On Sat, Oct 11, 2003 at 06:06:11AM -0600, Marcelo E. Magallon wrote: > > Me too. The actual problem seems to have been causing by a behavior of > > ldconfig that we almost never see because we tend to ship library > > packages with lib$SONAME.so.$SOVERSION symbolic links already in the > > package payload. > > I don't want to nitpick, but the SONAME is what you are calling > lib$SONAME.so.$SOVERSION. What you call $SONAME doesn't actually have > a name, but is sometimes referenced as the library name (actually > lib$SONAME). Linux's dynamic linker doesn't really understand version > numbers (at least not in the way, say, IRIX does, which would be closer > to what you wrote, but not quite) > > What we ship in the packages is a symbolic link $SONAME -> $FILENAME. Thanks for the clarification. -- G. Branden Robinson | Those who fail to remember the laws Debian GNU/Linux | of science are condemned to branden@debian.org | rediscover some of the worst ones. http://people.debian.org/~branden/ | -- Harold Gordon
Attachment:
signature.asc
Description: Digital signature