configure: error: GDBM library not found !!! ERROR: net-mail/maildrop-1.5.3 failed. !!! Function econf, Line 324, Exitcode 1 !!! econf failed '---[root@arrakis]---# etcat -v gdbm [ Results for search key : gdbm ] [ Applications found : 1 ] * sys-libs/gdbm : [ I] sys-libs/gdbm-1.8.0-r5 (0) '---[root@arrakis]---# emerge info Portage 2.0.49-r3 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.6.0-test5-mm2) ================================================================= System uname: 2.6.0-test5-mm2 i686 AMD Athlon(tm) MP 2000+ ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-mp -O3 -pipe -fomit-frame-pointer -m3dnow -msse -mmmx -mfpmath=sse" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon-mp -O3 -pipe -fomit-frame-pointer -m3dnow -msse -mmmx -mfpmath=sse" DISTDIR="/usr/portage/distfiles" FEATURES="ccache autoaddcvs sandbox userpriv usersandbox fixpackages" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt cups encode foomaticdb gif jpeg libg++ mad mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib alsa gdbm berkdb slang readline tetex aalib bonobo svga tcltk java guile mysql X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk motif opengl cdr scanner 3dnow acl cscope directfb dga dvb dvd faad fbcon gb gd ggi gtk2 gtkhtml imap ipv6 leim mozilla mozsvg mozxmlterm mozaccess mozp3p moznocompose moznoirc moznomail mpi nas nptl samba sse tiff usb xface xfs xml -arts -qt -kde ldap"
BTW, if compiled with USE="-mysql -ldap -gdbm -berkdb", everything compiles fine.
*** Bug 31400 has been marked as a duplicate of this bug. ***
I encountered this as well, but uncovered 10x the headaches before I started looking :) If you have the berkdb USE flag, it uses that instead of gdbm (despite the configure error, it's actually testing for bdb). However, if you use berkdb, maildrop will only compile against db-3.2, not db-4. But if you have both 3.2 and 4 installed, /usr/lib/libdb.so will link to 4, not 3.2. Okay, simple enough, I just patch the config/makefiles to use -ldb-3.2 instead of -ldb. Configure works, make goes for awhile, then I see this: make[2]: Entering directory `/var/tmp/portage/maildrop-1.5.3/work/maildrop-1.5.3/bdbobj' g++ -O3 -march=i686 -pipe -o testbdb testbdb.o libbdbobj.a -ldb-3.2 libbdbobj.a(bdbobj.o)(.text+0x78): In function `bdbobj_open': : undefined reference to `db_create_4000' collect2: ld returned 1 exit status make[2]: *** [testbdb] Error 1 make[2]: Leaving directory `/var/tmp/portage/maildrop-1.5.3/work/maildrop-1.5.3/bdbobj' I'm not a linking expert, but it appears that even using -ldb-3.2 is trying to use something from db-4. Oy vey. Long-term issue: there seems to be some clobbering issues between db-4 and db-3.2. Short term solution: USE=-berkdb emerge maildrop
I notice that the problem has been resolved in so far as it has been simply avoided in the 1.5.3-r1 ebuild; check-in comment: "Remove optional dependency on berkdb as it will not work with berkdb4 and patching is nontrivial". I don't know how important berkdb support is for maildrop, but might I suggest to the relevant developers that (a) if it isn't overly useful (b) there is no immediate intention to resolve the bdb4 issues - then this bug should be closed as CANTFIX or LATER and the new ebuild bumped to stable (especially in view of the fact that db-4.0.14-r2 is marked as stable on the majority of arches, thus making it an obvious problem for most folks)?
As far as I can tell, berkdb is only in maildrop as a "legacy" alternative to gdbm. If you have gdbm (which you should anyways, as gentoo prefers it in other places), berkdb isn't even needed. I agree with the decision to just remove its support. Funny, if maildrop actually supported berkdb 4, I would instead insist that this be fixed and patched, but 3.2 screams "LEGACY"!
i had the similiar but, that i wanted to use berkdb (not gdbm) and db-4.x confused it. so i got it built finally with this order of commands: # emerge unmerge db-4.0.14-r2 # emerge '<sys-libs/db-4' -gk # epm -q db db-3.2.9-r9 db-1.85-r1 # USE=berkdb emerge maildrop
well not fixed by default for me either, just after a fresh gentoo install: checking for dbopen in -ldb... no checking for db_open in -ldb... no checking for db_env_create in -ldb... no checking for dbopen... no checking for db_open... no checking for db_env_create... no configure: error: GDBM library not found !!! ERROR: net-mail/maildrop-1.5.3 failed. !!! Function econf, Line 365, Exitcode 1 !!! econf failed installing sys-libs/gdbm-1.8.0-r5 DIDN'T solved it. but env USE="-berkdb" emerge maildrop did. (uhm)
Does this still happen with the latest maildrop?
Closing this, as latest maildrop (1.7.0-20040907) doesn't show this behavior. Feel free to reopen if it doesn't work.
*** Bug 35095 has been marked as a duplicate of this bug. ***
