Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!classic.iinet.com.au!news.uoregon.edu!news.delphi.com!uunet!in1.uu.net!polstra!not-for-mail
From: jdp@polstra.com (John Polstra)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: ld.so failed
Date: 11 Sep 1995 09:02:15 -0700
Organization: Polstra & Co., Seattle, WA
Lines: 23
Message-ID: <431mi7$8v8@seattle.polstra.com>
References: <42dk7r$r6n@shore.shore.net> <42n7f7$s6g@helena.MT.net> <42pf84$11o@shore.shore.net> <42tsc2$m5a@helena.MT.net>
NNTP-Posting-Host: seattle.polstra.com
In article <42tsc2$m5a@helena.MT.net>,
Nate Williams <nate@sneezy.sri.com> wrote:
> In article <42pf84$11o@shore.shore.net>, <witr@spooky.rwwa.com> wrote:
>
> >And, I've found
> >you can leave off a library, like -lm, and you get no message until
> >``ld.so failed''. It is easy to do this sort of thing (since how
> >would you know that adding -lfoo requires you to also add -lm), and
> >the resulting message is silly.
>
> Huh? You should get link time errors, not run-time errors if you are
> missing routines. If the errors occur at run-time, then the linker
> has a bug not the run-time loader.
And that is precisely the case, as mentioned in ld(1):
BUGS
Shared objects are not properly checked for undefined symbols.
--
John Polstra jdp@polstra.com
Polstra & Co., Inc. Seattle, Washington USA
"Self-knowledge is always bad news." -- John Barth