On 28 Jun 2000, Alexandre Oliva wrote:
> On Jun 28, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>
> > But, there is nothing to update! We have already addressed the
> > issue of toplevel configure passing both --build and --host
> > down to sub-configures.
>
> Indeed. But there's a lot of documentation to be updated, so that
> people will use --build where appropriate.
The "we would need to change documentation" argument is a red herring.
Most of the documentation (like the GNU coding standards) either
have incorrect info or no info on how to cross compile a package.
If you are talking about our internal cygnus documentaiton,
then that is another story, but that has nothing to do with
everyday users of autoconf.
> And we also have to update
> the top-level configure to reflect the new semantics of --build and
> --host.
Is that the main argument for reverting back to the old
--host semantics? Just so that the cygnus toplevel
configure script does not need to get updated to
match the changed semantics of CVS autoconf?
It just seems like we are holding back real
progress in autoconf just so that we can
avoid doing some work to update our custom
toplevel configure.
Mo DeJong
Red Hat Inc
