From: Keith M. <kei...@us...> - 2006-08-28 12:01:57
|
Hi Michael, On Monday 28 August 2006 6:49 am, Michael Gerdau wrote: > However as far as I understand the problem I'm facing with generating > the runtime libs during build the xcompiler it is that I need a way > to omit the two checks I currently do patch out of runtime's configure. > Both require a fully working xgcc and that one needs a few libs/objs > that aren't there until after runtime has been build (a typical > bootstrap issue :) Yes. The the two checks which are failing are, as you note:-- 'checking for C compiler default output file name' (lines 1696-1742) 'checking for suffix of executables' (lines 1790-1815) Both of these tests are embedded within autoconf's `AC_PROG_CC' macro, so there is no easy way to disable them, at the autoconf level. As you have discovered, you can patch them out of `configure' itself, but that's not really a satisfactory solution--your patch could too easily be rendered invalid, just by the simple action of running autoconf, regenerating `configure' to incorporate some minor (and maybe unrelated) change, or even simply if a different autoconf version is deployed. Furthermore, both of these tests require that the C compiler, xgcc in our case, be able to successfully link a minimal test program--it doesn't need to be able to run it, if cross-compiling, but the link must succeed. In our case, that link step is failing, because xgcc implicitly tries to link in runtime objects which haven't yet been built. Perhaps passing `LDFLAGS=-nostdlib' as a `configure' parameter could help, or maybe we need to prebuild a minimal subset of the runtime objects, before configuring for the complete build. I'll have a play with it, when I can find some spare time. Regards, Keith. |