RE: Why won't my program compile? (continued)

["Robert P. J. Day" <rpjday at mindspring dot com>]

On Fri, 4 Nov 2005, mdmiller@visi.com wrote:

> And you fine gentlepeople are correct, my problem was the one caused
> by the gcc check that Mike Joyce provided a patch for.  The result
> is I go further but still crash and burn due to an internal compiler
> spill error.  Which suggests that Robert's suggestion of staying on
> the path because of the monsters in the woods has some merit.  My
> goal is to get the 2.6.14 kernel and its USB fixes running on an SH4
> board, but I don't have to get there in a single step.  Can anyone
> suggest a gcc/glibc combination that is in the direction of
> goodness? I'll use the compiler error as my .sigline today.

over on the linuxsh-dev list, we have reports of folks who have
working SH4 toolchains built using crosstool that have in fact
compiled the 2.6.14+sh kernel.  you might want to check the archives
of the mailing list:

http://lists.sourceforge.net/lists/listinfo/linuxsh-dev

  there is a wiki page (that i've been hacking on) explaining the
process here:

http://linux-sh.org/shwiki/Crosstool038

but it's just a touch out-of-date and i'm going to leave it alone
until the next release of crosstool since it's just not worth
explaining the workarounds when a newer version of crosstool will
(theoretically) work out of the box.

so you can wait a few days or read the most recent posts in the
archives if you're in a rush.

rday

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