From: Akim Demaille <[EMAIL PROTECTED]>
Date: 25 Apr 2000 18:56:57 +0200
Tom> However, "make" doesn't use --target. Still, it gets passed in
Tom> by the top-level configure.
I understand this, although I'd understand better with --host. So
actually what you are teaching me is that you do ship
cross-compiling suites, i.e., a set of cross-compilation tool such as
sun4-gcc, sun4-ld etc., but also a sun4-make which is actually just a
standard make, right?
No, it's a plain old `make', not a `sun4-make'. After all, make
ignores --target, so it doesn't affect the name of the program.
It's still convenient to supply GNU make in the bin directory. Cygnus
customers find it useful. Why should Cygnus restrict itself to only
supplying cross-tools in the bin directory?
Is it right to:
- not document --target etc. when the AC_CANONICAL_TARGET etc. is not
used?
Yes.
- change the defaults to
1. build ?= config.guess
2. host ?= build
3. target ?= host
I think this is reasonable, because config.guess has been around for
so long that people have grown accustomed to it.
- remove the support of HOST on the command line, because it is
incorrect to map this HOST to a virtual --host=HOST
I think is required given that we change the default for build, host,
and target.
Ian
