Lewis Perin (firstname.lastname@example.org)
Tue, 16 Mar 1999 10:51:08 -0500 (EST)
>From: F Labrosse <email@example.com>
>Tim Waugh writes:
> > On Tue, 16 Mar 1999, David Campbell wrote:
> > > > ./parport.o: unresolved symbol memset
> > >
> > > I have seen this also with kernel modules, I believe that you will
> > > find that memset is not used in any of the code!?!
> > It is though, and in clean 2.2.3. What does 'nm parport.o | grep memset'
> > say, and which compiler are you using? It sounds like the kind of thing
> > that would break if you forgot to use optimisation.
>I have exactly the same problem (see my todays post). It appears only with
>twm3 and 4, not with twm1 and 2. BTW, using gcc. I didn't checked nm
>parport.o but memset() IS used in several places in the parport files.
Maybe memset resolves to a macro under the right compile options?
--- Lew Perin | firstname.lastname@example.org | www.panix.com/~perin/
-- To unsubscribe, send mail to: email@example.com -- -- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2.0b3 on Sun 28 Mar 1999 - 17:01:08 EST