After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 51192 - compile fails if db2/db3 present?
compile fails if db2/db3 present?
Status: RESOLVED DUPLICATE of bug 50935
Product: gnome-libs
Classification: Deprecated
Component: libgnome
1.2.x
Other Linux
: Normal normal
: ---
Assigned To: Martin Baulig
Martin Baulig
Depends on:
Blocks:
 
 
Reported: 2001-02-20 22:50 UTC by Telsa Gwynne
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Telsa Gwynne 2001-02-20 22:50:16 UTC 
In a fit of gnome-1.4beta enthusiasm decided to build rpms. Ploughed
through compile order given on gnome-1.4-list.

Attempted rpm -ta gnome-libs-1.2.12.tar.gz on a RH 7.0 system with all
updates installed. Machine has a fairly full install, including
db1-1.85-4, db1-devel-1.85-4, db2-2.4.14-4, db2-devel-2.4.14-4,
db3-3.1.14-6 and db3-devel-3.1.14-6 -- which I think may be relevant.

rpm -ta failed with a host of these errors:
gnome-metadata.c: In function `metadata_set':
gnome-metadata.c:302: warning: passing arg 2 of pointer to function from
incompatible pointer type
gnome-metadata.c:302: too few arguments to function

Friend suggests --prefer-db1 as per RH specfiles, because "it breaks with
db3" -- but in that case, why is configure not complaining? Not sure what
I should do here.
Comment 1 Telsa Gwynne 2001-02-20 23:48:28 UTC 
Oh, christophe saw it before me. Marking as dup cos I think it is.

*** This bug has been marked as a duplicate of 50935 ***
Comment 2 Roy Stogner 2001-03-02 05:06:03 UTC 
Is there some reason for the restrictive read permissions on bug
50935?  I'm running into this problem as well.
Comment 3 Telsa Gwynne 2001-03-06 17:59:51 UTC 
What kind of restriction? As far as I can tell, anyone can
read it. Is Bugzilla telling you have to login to proceed
or something? It uses cookies, so if your browser is not
accepting them you have to keep logging in to read and comment
on bugs.

Mail me about this, and we'll see what's going on.