On 26 Jun 2000, Alexandre Oliva wrote:
> On Jun 26, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>
> > I thought there was already a switch for cygnus behavior.
>
> > --cygnus assume program is part of Cygnus-style tree
>
> I've never seen this option, and it doesn't seem to be accepted by any
> autoconf-generated `configure' script.
Oh, perhaps it only applies to automake. Here is the description
from automake.info-1.
`--cygnus'
Causes the generated `Makefile.in's to follow Cygnus rules, instead
of GNU or Gnits rules. For more information, see *Note Cygnus::.
> > Would it be possible to put this old style --host is really
> > --build stuff into the set of options activated when --cygnus
> > is passed in?
>
> Maybe we should not assume --build when --host is given, just warn
> instead. This would work under the assumption that people running
> configure interactively don't often specify --host=TRIPLET, but rather
> just TRIPLET, which would work in the new set-up too. I.e., your
> patch for $host_alias != $build_alias would be enough.
Do you mean warn that --host will do a cross compile or warn that
it will not do a cross compile? By the way, my patch was not
to test if $host_alias != $build_alias, it was a test
to see if they were exactly the same and only when
--host=TRIPLE was given.
if test "x$host_alias" = "x" || test "$host_alias" = "$build_alias" ; then
cross_compiling=no
ac_tool_prefix=
else
cross_compiling=yes
ac_tool_prefix=$host_alias-
fi
Mo DeJong
Red Hat Inc
