RE: [ng-spice-devel] Spice3f4 on Win32 with MinGW


To "'ng-spice-devel@ieee.ing.uniroma1.it'" <ng-spice-devel@ieee.ing.uniroma1.it>
From "Gillespie, Alan" <Alan.Gillespie@analog.com>
Date Wed, 25 Apr 2001 16:55:55 +0100
Delivered-To mailing list ng-spice-devel@ieee.ing.uniroma1.it
Mailing-List contact ng-spice-devel-help@ieee.ing.uniroma1.it; run by ezmlm
Reply-To ng-spice-devel@ieee.ing.uniroma1.it


> The traditional unix linker (ld) is a single-pass linker. 
> This means that,
> if a symbol is referenced in library a, and defined in 
> library b, library b
> must be after library a on the link line, or the symbol won't 
> be found.
> This problem goes away with dynamic linking. It becomes 
> significantly more
> painful if there are circular dependencies in the two (or 
> more) libraries -
> this can require multiple instances of the library on the command line
> (e.g. -lsomelib -lsomeotherlib -lsomelib)

Oh my god. My brain hurts. That makes a lot of sense. It
explains why gcc was linking some libraries in twice
(I thought).

So I need to remember where every symbol in spice is defined
and in which files it's referenced, so that I can then figure
out what order I need to put the libraries in, and how many
times !! That'll be simple enough ;-) Sounds like trial and
error is the simplest way after all.

Hang on. If I know where all the symbols and references are,
why don't I just link it myself !! I'm not getting to like
C/Unix any more yet ;-) I'm sure I'll grow to love it in
another 50 years or so.

> All of the above is written while I'm trying to get my head 
> around some
> quantum mech late at night, and may be entirely wrong. It's 
> more or less
> accurate though, I think.

Thanks for your input.

Alan

Partial thread listing: