Return to BSD News archive
Xref: sserve comp.os.386bsd.development:1502 comp.os.386bsd.misc:1656 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!pipex!sunic!news.funet.fi!nntp.hut.fi!nntp!sja From: sja@snakemail.hut.fi (Sakari Jalovaara) Newsgroups: comp.os.386bsd.development,comp.os.386bsd.misc Subject: Re: Something positive for a change: FreeBSD 1.0 shared libs are working Date: 21 Nov 93 11:00:32 GMT Organization: Helsinki University of Technology, Finland Lines: 15 Distribution: inet Message-ID: <SJA.93Nov21130032@gamma.hut.fi> References: <2cgdem$7gq@pdq.coe.montana.edu> <NEWSSERV!STARK!GENE.93Nov18221904@stark.uucp> NNTP-Posting-Host: gamma.hut.fi In-reply-to: newsserv!stark!gene@cs.sunysb.edu's message of 18 Nov 93 22:19:04 > However shared libraries are the scourge of the > earth when it comes to software that is not released as a single unit. Yes! One way of dealing with this would be to have 1) version number checking and multiple co-existing versions of libraries (the SunOS system seems good enough.) 2) a tool (linker) that takes an executable (not object files) and a list of dynamic libraries and build a new a.out that has some or all of its libraries linked in statically. (Hint, hint, *BSD developers!) Undefined symbol: ++sja