From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Lance Taylor To: joel@OARcorp.com Cc: gas2@cygnus.com Subject: Re: more on powerpc-rtems ar failure Date: Thu, 16 Apr 1998 14:43:00 -0000 Message-id: <199804162143.RAA02012@subrogation.cygnus.com> References: X-SW-Source: 1998/msg00143.html Date: Thu, 16 Apr 1998 16:30:24 -0500 (CDT) From: Joel Sherrill Will taking the default result in getting all the formats for a particular CPU? I have tried to encourage the use of CPU-rtems for all users of CPU and then have them use objcopy to produce the exact format required by a board. For example, does m68k-coff (aka m68k-rtems) also include at least m68k-aout, srecords, binary -- with m68k-elf a plus. In general, no. You can see which formats will be supported for a particular configuration target by looking in config.bfd. The s-records and binary formats are always supported, as are the tekhex and Intel hex formats. For your particular example of m68k-coff, you will get support for m68k-coff, versados, and m68k IEEE, but not m68k-aout or m68k-elf. On CPUs with both big and little endian, does it get all the "same endian" formats? It normally gets both big and little endian variants, if that is what you are asking. Ian