mozilla-1.7.5-r1 If custom LDFLAGS are configured in make.conf, they will get parsed incorrectly when building the ldap componets of mozilla resulting in a "-Wl,-soname" which halts the ebuild. ======= making ./libldap50.so i686-pc-linux-gnu-ld -shared -Wl,-soname -Wl,libldap50.so -o libldap50.so ./abandon.o ./add.o ./bind.o ./cache.o ./charray.o ./charset.o ./compare.o ./compat.o ./control.o ./countvalues.o ./delete.o ./disptmpl.o ./dsparse.o ./error.o ./extendop.o ./free.o ./freevalues.o ./friendly.o ./getattr.o ./getdn.o ./getdxbyname.o ./getentry.o ./getfilter.o ./getoption.o ./getvalues.o ./memcache.o ./message.o ./modify.o ./open.o ./os-ip.o ./proxyauthctrl.o ./psearch.o ./referral.o ./regex.o ./rename.o ./request.o ./reslist.o ./result.o ./saslbind.o ./sbind.o ./search.o ./setoption.o ./sort.o ./sortctrl.o ./srchpref.o ./tmplout.o ./ufn.o ./unbind.o ./unescape.o ./url.o ./utf8.o ./vlistctrl.o -L/var/tmp/portage/mozilla-1.7.5-r1/work/mozilla/dist/lib -llber50 i686-pc-linux-gnu-ld: unrecognized option '-Wl,-soname' i686-pc-linux-gnu-ld: use the --help option for usage information gmake[5]: *** [libldap50.so] Error 1 gmake[5]: *** Waiting for unfinished jobs.... gmake[5]: Leaving directory `/var/tmp/portage/mozilla-1.7.5-r1/work/mozilla/directory/c-sdk/ldap/libraries/libldap' gmake[4]: *** [export] Error 2 gmake[4]: Leaving directory `/var/tmp/portage/mozilla-1.7.5-r1/work/mozilla/directory/c-sdk/ldap/libraries' gmake[3]: *** [export] Error 2 gmake[3]: Leaving directory `/var/tmp/portage/mozilla-1.7.5-r1/work/mozilla/directory/c-sdk/ldap' gmake[2]: *** [export] Error 2 gmake[2]: Leaving directory `/var/tmp/portage/mozilla-1.7.5-r1/work/mozilla/directory/c-sdk' gmake[1]: *** [ldap] Error 2 gmake[1]: Leaving directory `/var/tmp/portage/mozilla-1.7.5-r1/work/mozilla' make: *** [default] Error 2 Reproducible: Always Steps to Reproduce: 1. 2. 3. removing the -Wl, from the front of the -soname option and running the command manually fixes the problem. This must be done with libldap50.so and with libprldap50.so. After that, the ebuild can continue normally on it's own.
Please do `emerge --sync` before filing bug reports. *** This bug has been marked as a duplicate of 86361 ***
