🚀 go-pugleaf

--
In article <1h8f0hINNota@ni.umd.edu>, louie@sayshell.umd.edu (Louis A.
Mamakos) writes:
|>
|>In article <1992Dec22.173036.7075@murdoch.acc.Virginia.EDU>
|>quarrie@cds001.cebaf.gov (David Quarrie) writes:
|>>--
|>>I'm experiencing problems with unresolved references when using
|>archives (.a).
|>>This isn't just my own .a files, but also libX11.a for X-Windows. As
|>far as
|>>I can ascertain, it's a problem with global symbols instead of global
|>routines
|>>and can be illustrated by the following (I haven't actually done the
|>following
|>>since I'm not in front of my NeXT but I think it should illustrate
|>the
|>>problem):
|>
|>[...example omitted...]
|>
|>>Am I doing something stupid? Is it a case of RTFM? So far I've
|>managed to force
|>>linking to succeed by extracting the appropriate .o files from the
|>library
|>>and explicitly linking them, but I wouldn't have thought I should
|>need to do 
|>>that. 
|>
|>Stupid?  Well, I don't think so.  Yes, RTFM, specifically 'man
|>ranlib'.  I think the -c option will do what you need.
|>
|>
|>louie
|>

Louie is, of course, absolutely correct. ranlib -c works just fine and does the
job. There are times when I just HATE U**x and the fact that they all appear
to be identical, but they're all just a little bit different. I think it's
worse than using VAX/VMS and U**x, at least you know they're going to be
different.

I'm also intrigued by the fact that the libX11.a supplied by Cub'X also needs
this to be done. Is this a well known fact or am I the first person to try
building an X application? -)

Thanks again to Louie...

-------------------------------------------------------------------------------
	David Quarrie					CEBAF MS 12H
							12000 Jefferson Ave
Internet: quarrie@cebaf.gov				Newport News VA 23606
DECnet  : cebaf::quarrie				Tel: (804) 249-7562
BITNET  : quarrie@cebaf					Fax: (804) 249-5800