On Thursday 26 October 2006 17:12, Rafael Barrera Oro wrote: > >>and i checked and yes, nss is installed in /usr/lib64/nss, should i make > >>a symlink (/usr/lib/nss -> /usr/lib64/nss) ? > >[SNIP] > > > > That will solve the immediate issue, yes. The bigger issue, however, is > > that on that profile /usr/lib should have been a symlink to /usr/lib64. > > > >$ ls -ld /usr/lib > >lrwxrwxrwx 1 root root 5 2006-02-22 23:12 /usr/lib -> lib64 > > even with symlink manually created it wont work! this is a tough one! > > gentoo64 lib # ls -al > lrwxrwxrwx 1 root root 14 Oct 26 14:10 nss -> /usr/lib64/nss
It still gives the same error?
> Any other idea?
Well, you could replace /usr/lib/nss with /usr/lib64/nss in the ebuild. The
symlink should work though.
$ grep "use amd64" -A 1 `portageq portdir`/dev-java/jss/jss-3.4-r1.ebuild
elif use amd64; then
sed -e 's:-L$(DIST)/lib:-L/usr/lib/nspr -L/usr/lib/nss
-L$(JAVA_HOME)/jre/lib/amd64 -L$(JAVA_HOME)/jre/lib/amd64/server
-L$(DIST)/lib:' \
> how about replacing lib with a symlink to lib64 ?
You mean replace /usr/lib with a symlink like it's supposed to be? I certainly
would do that if it was my system but I guess you'd need to move the contents
of /usr/lib to lib64 first. I certainly would take a good look at what /usr/lib
and /usr/lib64 contains first. Would like to make sure I didn't overwrite
something unintentionally...
--
Bo Andresen
pgpd06z1gJ66w.pgp
Description: PGP signature
