Hello, On Thu, Sep 01, 2005 at 12:58:40PM -0700, Noah Misch wrote: > > So, I think that autoconf should cope with this problem. > > It would be nice to handle this automatically, but I doubt we could do so > without breaking something elsewhere. I think that the following scenario might work: We would write a shell wrapper, which would run the compiler, investigate its output and then exit with the right exit code. At the beginning of the configure script, some tests would decide whether the copiler is broken or not. The wrapper would be used only for the broken compilers. The autodetection could be performed by the same script, the wrapper. Since the wrapper would be an external script, it could be upgraded independently on the main configure script, similarly as the config.guess script. This solution would not affect the normal platforms. But who would be interested to invest his time into this work? Perhaps the firms selling the broken compilers could sponsor this work, if they would think this moght be cheaper than fixing the compiler. Have a nice day, Stepan Kasal _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
