MacOS X libtool problem with non-standard libobjc

[Bill Northcott]

It appears that libtool 1.4.3 implicitly assumes that any App containing 
Objective-C code must be linked against the system (Apple) libobjc.  This 
stuffs up projects like Swarm or GNUstep which use non-Apple runtimes 
which include a libobjc.

The problem is that regardless of where the object file containing the 
main() function appears on the libtool command line, libtool will create a 
link instruction placing it ahead of any -Lsomepaths.

When the linker(ld) encounters the object file containing main(), if that 
object file includes Objective-C code, it will be linked against the 
system libobjc.  Any '-Lpathtomylibobjc -lobjc' type flags further down 
the command line are just ignored even though there were undefined symbols 
in the first link.

In order to work  -Lpathtomylibobjc must precede any object files 
containing Objective-C on the ld command line.  Libtool 'as is' prevents 
this!  Even LD_LIBRARY_PATH variables don't seem to help.

Bill Northcott