Contents|Index|Previous|Next

Target names

If you have a cross-development tape, the label also indicates the target for that configuration. The pattern for target names uses the following form.

architecture [- vendor] - object format

Target names differ slightly from host names in that the last variable indicates the object format rather than the operating system, and the second variable is often left out (this practice is becoming obsolete; in the future, all configuration names will be made up of three parts).

In cross-development configurations, each tool in the GNUPro Toolkit package is installed with the configured name of the target as a prefix. For example, if the C compiler is configured to generate COFF format code for the Motorola 680x0 family, the compiler is installed as ‘m68k-coff-gcc’.

The following lists some of the more common targets supported by Cygnus Solutions. (Not all targets are supported on every host!)

The list is not exhaustive; see Embedded Configurations Supported in Release Notes for GNUPro Toolkit for an up-to-date matrix with current host/target combinations supported by Cygnus Solutions. Also, see GNUPro Tools for Embedded Systems and config.guess .

Motorola 68000 family

m68k-aout

    a.out object code format

m68k-coff

    COFF object code format

m68k-vxworks5.2

    VxWorks environment

Intel 960 family

i960-vxworks5.1

    VxWorks environment (COFF format)

i960- coff

    MON960 monitor

SPARC family

sparc-vxworks

    VxWorks environment

sparc-aout

    a.out object code format

sparclite-aout

    a.out object code format

sparclite-coff

    COFF object code format

Intel 80x86 family

i386-aout

      a.out object code format

i386-elf

      ELF object code format

MIPS R3000/R4xx0

mips-ecoff

    MIPS R3000, ECOFF object code format

mips-elf

    MIPS R3000, ELF object code format

mips64-elf

    MIPS R4xx0, ELF object code format

Hitachi H8/300

h8300-hms

    COFF object code format

Hitachi SH

sh-hms

      COFF object code format