Re: Is this a bug in autoconf? (patch included)

[Akim Demaille]

| Akim Demaille wrote:
| > 
| > To make my question about $nonopt clearer, I'd like to know if there
| > is any reason to distinguish HOST when it comes from --host=HOST, and
| > HOST went it comes from ./configure HOST.

s/went/when/

| Canadian Crosses:
| 
| Until now you had to use eg. this:
| configure --build=`/<package>/config.guess` --host=i386-pc-cygwin32
| --target=m68k-rtems
| 
| AFAIU, running config.guess to determine $host* was a long withstanding
| bug in autoconf. 
| The proposal to let $build* be determined from config.guess and to
| default $host* from $build* seems logical to me.
| 
| Actually, I don't see why config.guess should be run to determine
| $host*.

I feel I'm being peterized here :)  I can't see the relationship
between your answer and my question :).

But I understand and agree with what you say :)

My question is should specifying the HOST as a single argument as
opposed to --host=HOST be any different?  Shouldn't it be the same?
Actually, is there any point in keeping two different interfaces to
the same feature?

        Akim