🚀 go-pugleaf

In article <9511171758.AA14183@vital>,
Albert Golembiowski <albert@inrs-telecom.uquebec.ca> wrote:
>Hello Experts,
>
>Are there any legitimate circumstance under which `ld'
>flags symbols (function names) as `undefined' even though
>they exist in an archive symbol table, as assured by command `nm -s',
>and the archive is listed downstream from where the
>`undefined' originate.
>
>I'd think that `ld' simply looks up the symbol table to decide on
>undefined.

This is certainly legitimate.

The way all linkers work is given an object file, make a list of undefined
symbols.  Once all object files are done, then start looking at libraries.
For each library in order if any files in the library remove an undefined
symbol then include the file - this obviously change the undefined list.
However, once a file has been looked at once it is not looked at again -
so if libA.a defined something and libB.a needs it and libA.a is listed
before libB.a in the included libraries it will never link.

Probably I've now confused you.  Sorry :-(.  Library structure, and order
at linking is very important if you want to get your code to compile and
link.

Regards,
	Rohan
-- 
----------------------------------------------------------------------------
rjl@iassf.easams.com.au	| All quotes can be attributed to my automated quote
Rohan Lenard            | writing tool.  Yours for just $19.95; and if you
+61-2-367-4555          | call now you'll get a free set of steak knives ...