Bryan Kadzban wrote: >>> So, actually, .so and .a files are really only needed at compile time for >>> other packages. :-) >> OK, I was throwing the .so and the .so.1 files together. Since they are >> generally only symlinks, it makes sense to keep them together. > > Except I'm not sure it does, because they're used for different things. > :-) > > The soname symlink (the one whose name is determined by the > -Wl,-soname,XXXXX string at the library's compile time) is required at > runtime, or the program won't start. The plain .so link is only needed > at compile time. > > Unless I misunderstood what you mean by "keep them together"? I don't > think it makes any sense to have both in /lib, since I tend to think of > /lib as containing the bare minimum required to get /usr mounted...
I think the issue is that the library can be updated without rebuilding the app. For instance, I have: lrwxrwxrwx 1 root root 18 Aug 16 14:31 libncursesw.so.5 -> libncursesw.so.5.7 -rwxr-xr-x 1 root root 396804 Aug 16 17:09 libncursesw.so.5.7 If I updated to libncursesw.so.5.8, the link also updates, but the packages that use libncursesw.so.5 can still find it via the symlink. As an experiment, you might want to try renaming some of those symlinks and see if ldd still finds the library. I don't want to do it though. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
