On Wed Sep 12 06:00:56 2007, ptc wrote: > On Mon Mar 19 15:59:44 2007, [EMAIL PROTECTED] wrote: > > On Monday 19 March 2007 12:22, Andy Dougherty wrote: > > > > > I found the ticket that introduced this failing behavior, so I'm > resending > > > my message below with a fixed-up subject line to enter into RT. In > brief, > > > this patch incorrectly assumes that all compilers accept a '-h', > '--help', > > > or '/?' switch. Any compiler that doesn't is deemed 'not found', and > > > there is no way to override it. Extending the list of options to try is > > > not a sensible forward-looking portable strategy. > > > > I realize this patch precludes cross-compilation at the moment, but > does it > > work better for you, Andy? > > Applied the patch with some modifications so that it runs correctly on > Windows in r21212. Tested on Linux x86, Windows and Cygwin.
I've managed to test this on Solaris and it works if one doesn't specify a bogus compiler. However, if one does specify a bogus compiler for instance by using the configure line: perl Configure.pl --cc=moo then for some reason the configuration with solaris continues, even though it should barf. The problem exists around line 39 in config/init/hints/solaris.pm. If one tries C<exit 1;> if the C<run_command> call doesn't work, then configure just happily continues configuring. How does one get configure to stop completely at this point??? Using plain C<exit 1;> on Linux, Windows and Cygwin worked fine. Paul
