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] |
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.
That's right. I'm hijacking the manufacturer's field. I should have said so explicitly.
ppc405-linux or ppc405-unknown-linux probably would be closer to what you are looking for.
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.
Indeed. And it's not clear to me how much work that would be, or whether it would be worth the effort.
I guess I'd do it if people thought it was really important. I could look at what the sh4 people had to do as a guide, maybe. - Dan
-- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
------ 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] |