Path: utzoo!utgpu!watmath!uunet!lll-winken!pacbell!rtech!binky!roger
From: roger@binky.uucp (Roger Taranto)
Newsgroups: unix-pc.general
Subject: Re: _assert and shlib.ifile
Message-ID: <1989Jul6.223141.18008@binky.uucp>
Date: 6 Jul 89 22:31:41 GMT
References: <641@binky.UUCP> <8871@chinet.chi.il.us>
Reply-To: roger@binky.UUCP (Roger Taranto)
Organization: Binky, Inc., Alameda, CA
Lines: 16

In article <8871@chinet.chi.il.us> kdb@chinet.chi.il.us (Karl Botts) writes:
>In article <641@binky.UUCP> roger@binky.UUCP (Roger Taranto) writes:
>>Is _assert in the shlib?
>assert() is a macro.

I said _assert, not assert.  If you look at the definition of assert() in
<assert.h>, you'll see that it calls _assert.  _assert is in /lib/libc.a;
however, it is not in shlib.ifile.  So, if you want to link a program that
uses assert with the shared library, you have to extract assert.o from 
libc.a and link that in with your program.

I was wondering if assert was in the shared library, and someone forgot to
put it into the shlib.ifile, just like what happened with the daylight symbol.

-Roger
roger@binky.UUCP	...!{pacbell,ucbcad,rtech}!binky!roger