On 9/28/06, Arnie Stender <[EMAIL PROTECTED]> wrote:
It so happens that when I got rid of /usr/lib64 I copied its contents
to /usr/lib first which I think included the libpopt.la file. The reason
I did that was because (I think) the version in /usr/lib64 was newer. It
makes sense that it would have a reference to /usr/lib64 since that is
where to was installed but when I looked at the file in
/usr/lib/libpopt.la I found three lines relevant to this conversation.
# Please DO NOT delete this file!
# It is necessary for linking the library.
This must be a shot at self preservation.
:-) Definitely not necessary for linking the library once it's
installed. Linkers were working long before libtool came along.
# Directory that this library needs to be installed in:
libdir='/usr/lib'
Does the comment mean that "it was in /usr/lib64 and SHOULD BE in
/usr/lib" or does it mean "you can link to this lib in /usr/lib"? I'm
going to try renaming the file and try the compile again. Stay tuned to
the ongoing saga. ;-)
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
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
