On 9/28/06, Arnie Stender <[EMAIL PROTECTED]> wrote:
I got the following errors. It almost looks like libtool is finding a hard wired path to the /usr/lib64/libpopt that I removed. The question of the day is where would it be getting it from. Does it keep a cache file around?
Sort of. Libtool places .la files in the filesystem that have info about the associated library (.a and .so). So, libtool is pulling in /usr/lib/libpopt.la, which probably references /usr/lib64/libpopt.so. Libtool then fills this in on the linking command line, thinking this is where it should try to link to. I'd bet a dollar to donuts that you'll find the hangups in the .la file for libpopt. Now, some people just completely delete these .la files as they seem to cause nothing but trouble. RedHat does. I'm not exactly sure what the benefit of keeping them is. I don't really know the internals of libtool. During the build of libraries within the source tree, they're quite useful. Once they're on the / system, though, there's no reason why the linker won't just find them on it's own and do the right thing. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
