On Thu, Jun 23, 2005 at 06:18:30PM +0000, Alexey Toptygin wrote: >> static is your friend. >> >> Hint: it means something different for functions than it does for >> variables. > static makes the symbols local, but what does that mean? Does that mean > they will only be visible until the 'final link', and not thereafter? A > quick experiment reveals that local symbols aren't visible with nm -D, > which is what I was after, I guess; but why does the resulting shared > object still have static symbols (including local ones), unless stripped? > It seems that libc.so et al aren't stripped... is this to permit static > linking against libc without providing a separate .a version of the > library? There's still one there, so I guess not...
Testing is the best way to find out. > I guess a better question would be: what can I read to learn all about the > wet, messy guts of linking and object file formats? :-) Under Solaris? http://docs.sun.com/app/docs/doc/817-3677 David Eisner is a font of wisdom. I think that the particular email that contained that link should be reposted to the list every month. <hhos> Ben -- Ben Stern UNIX & Networks Monkey [EMAIL PROTECTED] This post does not represent FTI, even if I claim it does. Neener neener. UM Linux Users' Group Electromagnetic Networks Microbrew Software
