Duplicated this exact problem on 2 machines (one x86 and one ~x86). USE="-*" will give this: legolas root # emerge -v courier-imap Calculating dependencies ...done! >>> emerge (1 of 1) net-mail/courier-imap-3.0.2 to / >>> md5 src_uri ;-) courier-imap-3.0.2.tar.bz2 >>> Unpacking source... >>> Unpacking courier-imap-3.0.2.tar.bz2 to /var/tmp/portage/courier-imap-3.0.2/work * Applying courier-imap-3.0.2-db40vs41.patch... [ ok ] * Applying courier-imap-3.0.2-removerpm.patch... [ ok ] configure.in:21: error: possibly undefined macro: AC_PROG_SYSCONFTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. >>> Source unpacked. * vpopmail not found nls configure: creating cache /var/tmp/portage/courier-imap-3.0.2/work/config.cache checking for i686-pc-linux-gnu-gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for gawk... gawk checking for a BSD-compatible install... /bin/install -c checking whether ln -s works... yes checking whether make sets $(MAKE)... yes checking for perl5... no checking for perl... /usr/bin/perl checking for sysconftool...... ././sysconftool checking for env... /bin/env checking whether build environment is sane... yes checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for gdbm_open in -lgdbm... no checking for gdbm_open... no configure: error: Cannot find either the gdbm or the db library. !!! ERROR: net-mail/courier-imap-3.0.2 failed. !!! Function econf, Line 365, Exitcode 1 !!! econf failed I have db-4 installed, but not db-3. If I turn on the berkdb flag on either system it will install a db-3 package (As the ebuild explicitly chooses that) and installs courier-imap just fine. The package does not otherwise depend on db, but it seems it does require a db of some description. So it seems the package should always depend on db-3 unless the -berkdb and +gdbm flag combination is set in which case the dependancy can be for gdbm.
Ah. I see that is pretty much what is happening in the 3.05 courier-imap.
i've backported my fix I put in 3.0.5 to the other 3.x versions now.
