Re: problem with ./configure

On 2013-09-12 12:13 PM, Eric Blake wrote:
>
> That could help if we had a 'break' statement to abort the loop once we
> think a version had been scraped; but right now, the full loop is
> executed to completion regardless of what option(s) the compiler
> understands (and in the case of gcc, executing both --version AND -v is
> useful, as they give different outputs, both of which are useful).

Oh.  OK.

> I'm okay if someone writes a patch to propose such an early exit (the
> fewer times we execute 'gcc', the faster a configure script will run -
> provided we aren't adding more forks in our decision for an early exit
> in the first place), but am not sure I will tackle it myself.

Coincidentally I have fairly sophisticated compiler-version-detection 
logic written for another project; I'm not promising to do this anytime 
soon, but I might see about porting it over.

zw