Created attachment 287101 [details] gdbm-1.9.1[compat] build log with MAKEOPTS="V=1" # USE=compat emerge gdbm [...] # ldd -d -r /usr/lib/libgdbm_compat.so.4 linux-vdso.so.1 => (0x00007fff115ff000) libc.so.6 => /lib64/libc.so.6 (0x00007f9030820000) /lib64/ld-linux-x86-64.so.2 (0x00007f9030e01000) undefined symbol: gdbm_errno (/usr/lib/libgdbm_compat.so.4) undefined symbol: gdbm_version_number (/usr/lib/libgdbm_compat.so.4) undefined symbol: gdbm_nextkey (/usr/lib/libgdbm_compat.so.4) undefined symbol: gdbm_delete (/usr/lib/libgdbm_compat.so.4) undefined symbol: gdbm_firstkey (/usr/lib/libgdbm_compat.so.4) undefined symbol: gdbm_version_cmp (/usr/lib/libgdbm_compat.so.4) undefined symbol: gdbm_fetch (/usr/lib/libgdbm_compat.so.4) undefined symbol: gdbm_store (/usr/lib/libgdbm_compat.so.4) undefined symbol: gdbm_close (/usr/lib/libgdbm_compat.so.4) undefined symbol: gdbm_open (/usr/lib/libgdbm_compat.so.4) Note: I am experiencing this failure both with and without "-Wl,--as-needed" in LDFLAGS. This underlinking in libgdbm_compat.so.4 leads to build failures all over the place in packages that use gdbm (e.g. in python with USE=gdbm).
Upstream patch: http://git.gnu.org.ua/cgit/gdbm.git/commit/?id=ae9ea0011da4ba01e5639611d61c442af8d42817
should be all set now in the tree; thanks for the report! Commit message: Add patch from upstream so gdbm_compat links against gdbm http://sources.gentoo.org/sys-libs/gdbm/files/gdbm-1.9.1-compat-link.patch?rev=1.1 http://sources.gentoo.org/sys-libs/gdbm/gdbm-1.9.1-r1.ebuild?rev=1.1
