From owner-freebsd-questions Thu Apr 8 7:23:51 1999 Delivered-To: freebsd-questions@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 60389159E7 for ; Thu, 8 Apr 1999 07:23:46 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: from localhost (eagle@localhost) by eagle.phc.igs.net (8.9.3/8.9.3) with SMTP id KAA87851; Thu, 8 Apr 1999 10:19:45 GMT (envelope-from eagle@eagle.phc.igs.net) Date: Thu, 8 Apr 1999 10:19:45 +0000 (GMT) From: eagle To: John Polstra Cc: Bjoern Fischer , freebsd-questions@FreeBSD.ORG Subject: RE: ELF shared libs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 7 Apr 1999, John Polstra wrote: > Bjoern Fischer wrote: > > > how is version management of shared ELF libraries done? > > > > Is it true, that there must be exactly one digit behind > > the .so. (like libfoo.so.1)? Then how does the runtime > > linker distinct between compatible/uncompatible library > > API changes? > > It doesn't. If the version numbers differ, the libraries are > considered to be incompatible. There just one version number, and it > has to match exactly. (Well, actually, everything after the ".so" is > the "version number". It can have lots of digits but they still have > to match exactly.) That's just the way it works in the ELF standard. > Search the archives of the FreeBSD-current mailing list for way too > much discussion about it. > > > I couldn't find a man page for the runtime linker, too. > > man ld.so > > But it's out of date and doesn't describe the current ELF situation > accurately. > unless somthings changed radically only the first digit after so. is read by ldconfig at least that was the case a few months ago. rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message