Re: [Mingw-users] MinGW linker cmdline parser broken

[Chris W. <ch...@qw...>]

Hi Oliver,

On Fri, 19 Dec 2008, Oliver Lange wrote:

> > This is NOT a bug in MinGW. As Tor Lillqvist stated, it is a bug in 
> > Autotools and SCons (or in the build files of your project) if they 
> > produce non-portable output that relies on ELF-specific behaviour for 
> > undefined symbols to produce correct output. It would fail with Sun CC 
> > and many other compilers. ELF is the exception here, not the rule.
> 
> Well that's interesting news i never learned before. A linker starts 
> linking before it has read the entire command line... so i guess i'm 
> best off when i first pass all link options (!), then all objects and 
> then, at the very end, all libs?
> 
> Sorry guys for raising all the dust..

Please read the rest of my reply, where I talk about gnu getopt permuting 
the command line to move all the options to the front. So it should not 
matter in what order you specify the options.

Also, libraries can have dependencies on each other, and can even depend 
on object files, and object files can depend on other object files. There 
is no guarantee that the ordering you specified will work. The only one 
that is guaranteed to work is where each item (object file or library) is 
followed by the ones that it depends on. That may mean specifying the same 
object files and libraries more than once, in the case of circular 
dependencies.

Cheers, Chris.
-- 
_____ __     _
\  __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Ruby/Perl/SQL Developer |
\ _/_/_/_//_/___/ | Stop nuclear war http://www.nuclearrisk.org |