-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dan Nicholson wrote:
>
> Hmm, that's odd. I'd have expected it to say libdir='/usr/lib64'. Like
> I said, I don't know the details of how libtool works.
>
> You could certainly delete any .la files. RedHat does it for every
> package. That might be the quick and dirty solution to your problems.
>
> Here's one thought:
>
> grep 'lib64' /usr/lib/*.la
>
> Maybe the problem is coming from somewhere else.
>
> --
> Dan
Hey Dan,
GUESS WHAT! libbonobo and libbobnoboui at least and God only knows how
many more of these libs supply their own libtool in the source package.
In it all references to libs are /usr/lib64. I'm in the process of
re-compiling all the libs I can find that have such a local version
libtool. I'm copying down the libtool in /usr/bin/libtool that I
installed with CLFS. That has no such lib64 references. The only thing I
am left wondering is why everything built with the local libtool the
first time through. I feel like Tarzan swinging on a very long vine
through the jungle. It's a thrill but I have this feeling there is a
tree in my way and I don't see it yet. :-0 Stay tuned.
Arnie
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFHGjnI9lqJPlLBqQRAp2ZAJ9V/plA2EmirAsmLz4L8uHP0FI/oQCgkmVp
W8QnI84ZCfjIawHtNTJjCbQ=
=ak9C
-----END PGP SIGNATURE-----
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
