Target names

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

architecture[-vendor]-objfmt

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 Developer's Kit 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'.

Warning: configure can represent a very large number of target name combinations of architecture, vendor, and object format. There is by no means support for all possible combinations!

This is a list of some of the more common targets supported by Cygnus Support. (Not all targets are supported on every host!) The list is not exhaustive; see section `Overview' in Release Notes, for an up-to-date matrix which shows the host/target combinations supported by Cygnus.

Motorola 68000 family

m68k-aout                a.out object code format
m68k-coff                COFF object code format
m68k-vxworks             VxWorks environment
m68k-lynx                LynxOS 2.2 environment

Motorola 88000 family

m88k-coff                COFF object code format

Intel 960 family

i960-vxworks5.0          VxWorks environment (b.out format)
i960-vxworks5.1          VxWorks environment (COFF format
i960-intel-nindy         Nindy monitor

AMD 29000 family

a29k-amd-udi             UDI monitor interface
 To use the MINIMON interface, use this configuration
 with the auxiliary program MONTIP, available from AMD.

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-netware             NetWare NLM
i386-lynx                LynxOS 2.2 environment

IDT/MIPS R3000

mips-idt-ecoff           IDT R3000, big endian ECOFF
mipsel-idt-ecoff         IDT R3000, little endian ECOFF
mips64-idt-ecoff         IDT R4000 ECOFF

Hitachi H8300

h8300-hms-coff           COFF object code format

Hitachi SH

sh-hms-coff              COFF object code format

Z8000

z8k-coff                 COFF object code format