Date: Sun, 31 Jan 1999 21:12:28 +0100 (CET) From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: John Polstra <jdp@polstra.com> Cc: FreeBSD Hackers <hackers@FreeBSD.ORG> Subject: Re: ldconfig and libraries Message-ID: <XFMail.990131211228.asmodai@wxs.nl>
next in thread | raw e-mail | index | archive | help
On 31-Jan-99 John Polstra wrote: > In article <XFMail.990131121008.asmodai@wxs.nl>, > Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> wrote: >> >> are libraries in /usr/lib and /usr/local/lib tied to naming standards? > > To be recognized by ldconfig, an a.out shared library must have a > name that ends with ".so." followed by at least two version numbers, > like this: > > libfoo.so.12.0 > > To be recognized by ldconfig, an ELF shared library must have a name > that ends with ".so." followed by exactly one version number, like > this: > > libfoo.so.12 Why this change in library naming from a.out to elf? >> for example, is this an accepted name for ldconfig: >> >> libgmodule-1.1.so.12.0 > > For a.out: yes. For ELF: no. OK, this just broke a tonload of applications out there for people who like to compile stuff by themselves. E.g. Gtk+, Glib, libPropList. What would a workaround be then? Because an app depends on a certain name of a library or am I mistaken in that belief? >> Every library found by ldconfig in the specified paths should be >> reported back with ldconfig -r, right? > > Only the ones with names that fit the rules above. That explains why my previously list of a.out libs of about 185 is only 95 at the moment. *sigh* --- Jeroen Ruigrok van der Werven It's a Dance of Energy, asmodai(at)wxs.nl when the Mind goes Binary... Network/Security Specialist <http://home.wxs.nl/~asmodai>; *BSD: Powered by Knowledge & Know-how <http://www.freebsd.org>; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.990131211228.asmodai>