Re: Naming targets. ppc-405-linux?

[Ralf Corsepius <corsepiu at faw dot uni-ulm dot de>]

Am Don, 2003-05-22 um 20.26 schrieb Dan Kegel:
> 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

The ultimate source for target triples are config.sub and config.guess,
all other sources actually are more or less irrelevant.

> 
> 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.
If you want binutils to accept ppc405-linux, you'd have to extend
config.sub.

> 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
Well, this would be correct, if you have toolchain for a CPU of the
"ppc"-family, running on a system manufactured by "405", running the
"linux" OS.

> for an embedded Linux system with an IBM PPC405 chip.
> 
> Does that sound about right?
I don't think so.

ppc405-linux or ppc405-unknown-linux probably would be closer to what
you are looking for.

[Your case is very similar to the sh4eb case above.
The sh is a CPU-family, sh4 is a variant of this CPU-family, sh4eb is
the big endian only variant for the sh4e.

In your case you have a member of the ppc-CPU-family, and want to be
using variant 405.] 

However, you'd have to modifiy config.sub/config.guess to accept these
and to make sure binutils/gcc + your libc's configuration (glibc2/newlib
or else) accept them.

Ralf





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