Libraries and sym.links

Frank Langtind frank at langtind.no
Fri Dec 15 03:36:01 PST 2000



During compilation of KDE, I got an error message stating that libshadow.so 
was not present. libshadow.so.0 was present and creating a symbolic link 
called libshadow.so to that file, fixed the problem. It seems that such 
linking of libraries are very common. I'm wondering why do we need 
libXXX.so, libXXX.so.0, libXXX.so.0.0 etc. Is it a compability issue?

Frank


-- 
Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message




More information about the lfs-dev mailing list