On Mon, 17 May 2021, Martin Liška wrote:
> -@enumerate
> -@item
> -If you have chosen a configuration for GCC which requires other GNU
> -tools (such as GAS or the GNU linker) instead of the standard system
> -tools, install the required tools in the build directory under the names
> -@file{as}, @file{ld} or whatever is appropriate.
This bit is obsoleted by --with-build-time-tools (putting tools in the
build directory was needed in some cases before that option was added).
> -@item
> -Specify the host, build and target machine configurations. You do this
> -when you run the @file{configure} script.
But install.texi doesn't appear to have such documentation of what host,
build and target are and how to specify them.
> -Here are the possible CPU types:
> -
> -@quotation
> -@c gmicro, fx80, spur and tahoe omitted since they don't work.
> -1750a, a29k, alpha, arm, avr, c@var{n}, clipper, dsp16xx, elxsi, fr30, h8300,
> -hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, ip2k, m32r,
> -m68000, m68k, m88k, mcore, mips, mipsel, mips64, mips64el,
> -mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, romp, rs6000, sh, sparc,
> -sparclite, sparc64, v850, vax, we32k.
> -@end quotation
The very outdated list of specific names may not be very useful now,
although arguably there *should* be a current list of supported targets
(closer to that in config-list.mk, or at least a list of supported CPU
names and another list of supported OS names) in the installation
documentation.
> -Often a particular model of machine has a name. Many machine names are
> -recognized as aliases for CPU/company combinations. Thus, the machine
All such machine names can probably be considered obsolete; the main case
to document is CPU-SYSTEM (no company mentioned), not machine name aliases
(and mention somewhere that config.sub produces the canonical version of a
name).
--
Joseph S. Myers
jos...@codesourcery.com
