Re: Odd linking on aix 5.3



porter2 wrote:
My guess it's because of the position of foo.o.

Normally linkers pull bits out of libraries only if required, so as no
object files have been mentioned when the boost_filesystem library was
mentioned, the linker has decided that it can't be needed. The order is
significant in a link line, with left hand elements used first. With
statically linked libraries you can fail if you end up with circular
dependencies.


Not on AIX, it doesn't. All symbols are seen in the order they're
encountered on the command line, archives included. This is a behavior
that is distinctly different from other Unix systems.

--
-------------------------------------
http://www.photo.net/photos/garyrhook
Vocatus atque non vocatus deus aderit
.



Relevant Pages

  • Re: Odd linking on aix 5.3
    ... Normally linkers pull bits out of libraries only if required, ... object files have been mentioned when the boost_filesystem library was ... statically linked libraries you can fail if you end up with circular ...
    (comp.unix.aix)
  • Re: Odd linking on aix 5.3
    ... Normally linkers pull bits out of libraries only if required, ... object files have been mentioned when the boost_filesystem library was ... statically linked libraries you can fail if you end up with circular ...
    (comp.unix.aix)
  • Re: Modularisation
    ... Why linking a module into executable if out of this ... The semantics of linking against static libraries and object files ... all executables use the same instance. ...
    (comp.lang.c)
  • Re: Modularisation
    ... > I'm not sure what libraries you're talking about, but separating the code ... or the group of object files are made into a static archive ...
    (comp.lang.c)
  • Re: error LNK2019: unresolved external symbol
    ... the headers from its own installation ... resolves references from your object files and select object files ... from your libraries to satisfy these references. ... and then choose in which folder the compiler should look for. ...
    (microsoft.public.vc.language)