yeah... I already find it... the problem is that libtool is being generated after the configure script, and my automatic build system runs before configure, so I would have to patch configure in order to get it to output libtool already patched... (kinda confusing)...
That's why I was wondering if there was a way to get configure to get the right parameters from outside instead of patching it... I'll try removing the objects manually and see if that fixes the link... hopefully it will fix it all! :) thanks for the great help !!! really appreciate! :) -H On Mon, May 31, 2010 at 6:57 PM, JonY <[email protected]> wrote: > On 6/1/2010 09:57, Hradec wrote: > >> cool... I'll try that! >> >> a question... the ilmbase configure script if figuring all that out by >> itself... I'm wondering if there's a default mechanism that a configure >> script can use to query gcc in order to obtain those options... if so, is >> there a way to change the default options using an environment variable to >> remove booth .o and -nostdlib options? this way I can avoid patching the >> standard configure script... >> >> -H >> >> >> > Hi, > > this is libtool being stubborn, if you are good with shell scripts, you can > look into the libtool file for clues, if not, you could just grep for the > strings in libtool to remove them. > -- Hradec
------------------------------------------------------------------------------
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
