Bruce Dubbs wrote these words on 02/21/05 23:31 CST: > Randy McMurchy wrote: >>It is my understanding that the .so files, like the .a files are only >>used for linking during compilation of other programs. > > Incorrect. They are loaded when the program is loaded. If they are > already in memory, they do not need to be loaded again -- they are > reused. Thats the advantage of dynamically loaded libraries (dll) or > shared objects (so).
Perhaps I'm not making myself clear here. First of all, I realize what the purpose of the dynamic libs are for, and the difference between them and static libs. However, for the sake of clarity, I'll outline what I meant. PAM installs these libs in /lib: libpam.so.0.78 libpamc.so.0.78 libpam_misc.so.0.78 Then there are symlinks to these libraries: libpam.so.0 libpam.so others not displayed Now, my understanding is that the binary library and the symlink with the major number are required in /lib. The symlink without a major or minor number (the .so) symlink can be in /usr/lib. Like LFS does the Shadow libraries. You didn't address that part of my last post, and to me, what you say above contradicts the LFS installation of Shadow where the binary and the symlink with a major number is in /lib and the .so symlink is in /usr/lib. -- Randy rmlinux: [GNU ld version 2.15.91.0.2 20040727] [gcc (GCC) 3.4.1] [GNU C Library 2004-07-01 release version 2.3.4] [Linux 2.6.8.1 i686] 23:36:00 up 16 days, 7:25, 8 users, load average: 0.04, 0.04, 0.05 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
