Re: Unresolved references when linking

Article View: comp.sys.next.programmer

Article #1943

Back to comp.sys.next.programmer Previous Next

#1943

From: Louis A. Mamakos
Date: Wed, 23 Dec 1992 01:22

25 lines
1493 bytes

In article <1992Dec22.173036.7075@murdoch.acc.Virginia.EDU> quarrie@cds001.cebaf.gov (David Quarrie) writes:
>--
>The following is relevant to NeXTSTEP3.0.

And, actually NeXTSTEP 2.x and earlier, too.

>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

Technical Details

Message-ID: <1h8f0hINNota@ni.umd.edu>

Path: arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!darwin.sura.net!haven.umd.edu!ni.umd.edu!sayshell.umd.edu!louie

References: <1992Dec22.173036.7075@murdoch.acc.Virginia.EDU>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!darwin.sura.net!haven.umd.edu!ni.umd.edu!sayshell.umd.edu!louie
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Newsgroups: comp.sys.next.programmer
Subject: Re: Unresolved references when linking
Date: 23 Dec 1992 01:22:25 GMT
Organization: University of Maryland, College Park
Lines: 25
Message-ID: <1h8f0hINNota@ni.umd.edu>
References: <1992Dec22.173036.7075@murdoch.acc.Virginia.EDU>
NNTP-Posting-Host: sayshell.umd.edu

Reply to Parent Message