Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.ececs.uc.edu!news.kei.com!news.mathworks.com!EU.net!usenet2.news.uk.psi.net!uknet!usenet1.news.uk.psi.net!uknet!dispatch.news.demon.net!demon!awfulhak.demon.co.uk!awfulhak.demon.co.uk!awfulhak.demon.co.uk!not-for-mail
From: brian@anorak.utell.net (Brian Somers)
Newsgroups: comp.unix.solaris,comp.unix.bsd.misc
Subject: Re: Solaris 2.6
Date: 29 Nov 1996 16:29:32 -0000
Organization: Coverform Ltd.
Lines: 42
Sender: brian@awfulhak.demon.co.uk
Distribution: inet
Message-ID: <57n31c$3q2@anorak.utell.net>
References: <32986299.AC7@mail.esrin.esa.it>
<57djlg$bks@agate.berkeley.edu> <57dkbq$bsr@panix2.panix.com>
<casper.329abb76@mail.fwi.uva.nl> <57ej3a$7ij@panix2.panix.com>
<casper.329ae8f2@mail.fwi.uva.nl> <57hq0l$3rp@anorak.utell.net>
<57jrmi$pfd@innocence.interface-business.de>
Reply-To: brian%anorak.coverform.lan@awfulhak.demon.co.uk
NNTP-Posting-Host: anorak.coverform.lan
X-NNTP-Posting-Host: awfulhak.demon.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.8
Xref: euryale.cc.adfa.oz.au comp.unix.solaris:91212 comp.unix.bsd.misc:1659
In article <57jrmi$pfd@innocence.interface-business.de>,
j@ida.interface-business.de (J Wunsch) writes:
: brian@anorak.utell.net (Brian Somers) wrote:
:
>> : What about old .o files? Old dynamic libraries? Old archive libraries?
>> :
>> : How do you compile using those?
>> :
>>
>> You can't compile old objects/libraries with new objects/libraries and
>> expect to get a working binary at the end. Think about it - your header
>> files aren't the same !
:
: You can, as long as your library comes with header files that are
: self-contained. (I.e., they leave things like off_t to the system
: headers and don't use them.)
:
: Libraries that are not self-contained are poorly written anyway, in
: particular for the projected target market where the library is to be
: taken ``as is'' without any chance of a recompilation.
:
: There's always one hack more...
Writing a library that's *completely* self contained (I would think) has
got to be *really* rare. The only think I can think of off hand is
something memory resident - like a compression routine. Most things will
at least use a libc call, and if the libc args have changed you're back
to square one (unless you build your code using only the libraries and
headers, but if you can do that, then nothing's changed and it's a
non-issue).
I still think that the only way to link old and new objects/libraries
together is to put the symbol resolution info in the object - but that's
enormously impractical.
*shrug* - it's times like this that freeware becomes a nice idea :)
--
Brian <brian%anorak.coverform.lan@awfulhak.demon.co.uk>
<http://www.awfulhak.demon.co.uk/>
Don't _EVER_ lose your sense of humour....
.