I cannot emerge gnome-network. It exits with the following error: db.o(.text+0x2b): In function `database_open': : undefined reference to `__db185_open' collect2: ld returned 1 exit status distcc[1664] ERROR: compile on localhost failed with exit code 1 make[2]: *** [gnome-sync] Error 1 make[2]: Leaving directory `/var/tmp/portage/gnome-network-1.0.2-r1/work/gnome-network-1.0.2/sync' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gnome-network-1.0.2-r1/work/gnome-network-1.0.2' make: *** [all-recursive-am] Error 2 !!! ERROR: gnome-extra/gnome-network-1.0.2-r1 failed. !!! Function src_compile, Line 38, Exitcode 2 !!! compile error My emerge info reads: Portage 2.0.48-r5 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1) ================================================================= System uname: 2.4.22 i686 AMD Athlon(tm) Processor GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/var/cache/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 oss 3dnow apm avi crypt cups encode foomaticdb gif jpeg libg++ mad mikmod mmx mpeg ncurses pdflib png spell truetype xml2 xmms xv alsa gdbm berkdb slang readline arts tetex bonobo svga ggi tcltk guile X sdl gpm tcpd pam libwww ssl esd imlib oggvorbis gnome gtk qt kde opengl ldap cdr aalib cjk cscope dga dnd doc ethereal evo gtk2 jikes libgda maildir mbox md5sum mng moznocompose moznoirc moznomail mpi music nowin nptl offensive pic S3TC sasl sis src sse stroke threads type1 usb xml -java -motif -nls -quicktime -zlib -perl -python" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-O2 -march=athlon -fomit-frame-pointer -frename-registers -funroll-loops -pipe" CXXFLAGS="-O2 -march=athlon -fomit-frame-pointer -frename-registers -funroll-loops -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="ccache sandbox usersandbox userpriv distcc"
confirmed, the problem is the '-ldb1' which should be '-ldb' .. need to hack up a fix for this.
Created attachment 16886 [details, diff] patch to configure to fix ldb1 to ldb the owner takes no responsibility for damage to eyes caused by ugly hacks. do not continue if you have a known allergy to said hacks.
ok, not that I want to sound like a total idiot, but how are we suppose to apply this patch, and to what are we to apply the patch to? The ebuild? the configure file?
if you look at the first line of the patch you'll see 'configure' but if you're not used to patching that sort of thing is easy to miss. the best way for you to test this is to save the patch into gnome-extra/gnome-network/files and then add the following function under DEPEND and before src_compile( ) in the gnome-network ebuild. src_unpack() { unpack ${A} cd ${S} epatch ${FILESDIR}/gnome-network-1.0.2-r1.ldb1.patch }
is it just me or there actually is a /usr/lib/libdb1.so provided by sys-libs/db-1.85-r1 ? mcvaio lib # etcat belongs /usr/lib/libdb1.so.2 sys-libs Searching for /usr/lib/libdb1.so.2 in sys-libs ... sys-libs/db-1.85-r1 if anything, that should be patched to replace -ldb1 to -ldb-1, right?
i think it's a header type of problem, it now probably builds against the db4 headers with 185 compatability and picks the db1 .so which points to db1 (if around?) . What to do depends on which dep brings in db and if that one is compatible with newer db versions, if not we should fix the ebuild to only use db1 headers (there is some old hack to do this already in the ebuild, apperantly it doesn't work as expected anymore) otherwise we can just go for the generic db headers/shared objects. lqx: the -ldb1 is correct btw, it's part of the name not of the versioning. db1 uses both btw (the part which gives us problems here).
On my system it builds against db1, but gets headers from db3. I fixed it by changing the "old hack" in ebuild to: sed -i "N ; N ; N ; N ; N ; N ; s/#ifdef HAVE_DB_185_H\n# include <db_185.h>\n#else\n# include <db.h>\n#endif/#include <db1\/db.h>/g" sync/sync.h This gets rid of db_185.h and makes sure gnome-network uses db1 headers and not db2/db3/db4/whatever.
*** Bug 29772 has been marked as a duplicate of this bug. ***
*** Bug 30484 has been marked as a duplicate of this bug. ***
*** Bug 29131 has been marked as a duplicate of this bug. ***
Gnome-network 1.99.2 has just been released. Maybe that will compile more successfully...
I have duplicated this problem with my fresh install on a P4 system.
Mask maybe? Untill gnome-2.6 when its officially released?
*** Bug 37072 has been marked as a duplicate of this bug. ***
I am assuming it will be added when gnome 2.6 comes out.
That still leaves the intial bug, which is a problem, but we're sort of pressed on time and don't get around to the bugs of less immediate importance atm.
Ok, finally got around to this. I made the suggested fix in #7 into a patch and applied it. That should fix these problems as far as i can see. Please do test. I also added 1.99.5 to the tree, p.mask-ed . It probably misses some runtime deps & configure time switches, but it should work mostly. If anyone can clean that ebuild a bit more up, that would be cool. Please post patches here on bugzilla. Closing FIXED, i assume the problems got solved with this patch.
