This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Naming targets. ppc-405-linux?


One good source of target tuples that are in use for gnu tools
seems to be the Debian 'archtable' file:
http://cvs.debian.org/dpkg/archtable?rev=1.21.2.4&cvsroot=dpkg

This handles a lot of chip variations, e.g.
i386-linux-gnu


i486-linux-gnu

i586-linux-gnu

i686-linux-gnu
ppc
powerpc
powerpcle
powerpc64
sh3-linux-gnu


sh4-linux-gnu
sh3eb-linux-gnu
sh4eb-linux-gnu


Yet there are more variations out in the field, for instance,
the ppc405, which can't run programs compiled for normal powerpc
(it has quirks that need workarounds).  And you can't configure
for ppc405-linux; binutils barfs on that.

For those chips which don't have standard targets, and which need
their own toolchains, it looks like
the way to go is to jam the specific chip type into the middle
(vendor) field of the target name, e.g.

ppc-405-linux

for an embedded Linux system with an IBM PPC405 chip.

Does that sound about right?
- Dan


------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]