Re: gcc 2.95 and Standard C

["p. buxton" <somercet@xxxxxxxxxxx>]

_from: Bruce Smith <bruce@armintl.com>
>
> > But how am I meant to find out which lib to link to for every piddlin'
> > function my widdle heart desires?
>
>I was afraid you'd ask that.  I've been doing this for a long time,
>and I honestly don't remember where it's documented.  Perhaps someone else 
>can help.
>
>If I get stuck, I whip up a little script that runs "ar t" on the .a
>libraries grep'ing for the function I'm looking for.  I admit that's
>a HACK, and it's probably in documentation somewhere.

But a hack is better than nothing, which is what I had before. :)

_from: Adam Tauno Williams

>It may be adding dll's/symbols on the fly for you.  Which is nice, till it 
>gets 'em wrong.

Well, it's static linked. I say this because 2K source files on Windows 
become 70K programs, whereas on Linux they are 5-6K (before debug symbol 
stripping). But the same problem.

>You're correct.  I was told once that the man pages for functions are not 
>meant as full documentation, but simply to help jog the memory about 
>paramater lists etc...  I'd get a copy of the gcc user's manual and the 
>glibc
>reference.  Be prepared, as it fills two three-inch three ring binders.
>...
>
>And it becomes intuative after several wrist slashings.

gcc for Dummies, Sylvia Plath (ed.).

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at 
http://profiles.msn.com.