Bugzilla Bug 67427

Both 3.8 and 3.9.2 fails to install any shared objects, breaks evolution-2 when
building with USE="-mozilla ssl"

Adding || die "faile" to dolibs */lib/*.so in nss-3.9.2 ebuild results in:

>>> Install nss-3.9.2 into /var/tmp/portage/nss-3.9.2/image/ category dev-libs
ln: creating symbolic link
`/var/tmp/portage/nss-3.9.2/image//usr/lib/Linux2.6_x86_glibc_PTH_OPT.OBJ/lib/libfort.so'
to `../../../nss/lib/fortcrypt/Linux2.6_x86_glibc_PTH_OPT.OBJ/libfort.so': No
such file or directory
ln: creating symbolic link
`/var/tmp/portage/nss-3.9.2/image//usr/lib/Linux2.6_x86_glibc_PTH_OPT.OBJ/lib/libnss3.so'
to `../../../nss/lib/nss/Linux2.6_x86_glibc_PTH_OPT.OBJ/libnss3.so': No such
file or directory
ln: creating symbolic link
`/var/tmp/portage/nss-3.9.2/image//usr/lib/Linux2.6_x86_glibc_PTH_OPT.OBJ/lib/libnssckbi.so'
to
`../../../nss/lib/ckfw/builtins/Linux2.6_x86_glibc_PTH_OPT.OBJ/libnssckbi.so':
No such file or directory
ln: creating symbolic link
`/var/tmp/portage/nss-3.9.2/image//usr/lib/Linux2.6_x86_glibc_PTH_OPT.OBJ/lib/libsmime3.so'
to `../../../nss/lib/smime/Linux2.6_x86_glibc_PTH_OPT.OBJ/libsmime3.so': No
such file or directory
ln: creating symbolic link
`/var/tmp/portage/nss-3.9.2/image//usr/lib/Linux2.6_x86_glibc_PTH_OPT.OBJ/lib/libsoftokn3.so'
to `../../../nss/lib/softoken/Linux2.6_x86_glibc_PTH_OPT.OBJ/libsoftokn3.so':
No such file or directory
ln: creating symbolic link
`/var/tmp/portage/nss-3.9.2/image//usr/lib/Linux2.6_x86_glibc_PTH_OPT.OBJ/lib/libssl3.so'
to `../../../nss/lib/ssl/Linux2.6_x86_glibc_PTH_OPT.OBJ/libssl3.so': No such
file or directory
ln: creating symbolic link
`/var/tmp/portage/nss-3.9.2/image//usr/lib/Linux2.6_x86_glibc_PTH_OPT.OBJ/lib/libswft.so'
to
`../../../nss/lib/fortcrypt/swfort/pkcs11/Linux2.6_x86_glibc_PTH_OPT.OBJ/libswft.so':
No such file or directory

Created an attachment (id=41743) [details]
emerge info

Fixed in portage CVS.  Sorry it took me so long to sit down and check it out. 
Still recovering from Florida vacation.

I replied to the wrong bug.  But this looks like a dupe of 67124.

Definitely seems dupe, same user and same log.

*** This bug has been marked as a duplicate of 67124 ***