This is the mail archive of the crossgcc@sourceware.org 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] |
Quoting "Robert P. J. Day" <rpjday@mindspring.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. > > so you're still working on building a functional SH4 toolchain, is > that it? > > rday > Yes, please. I've poked around and seen your bugzilla/crosstool comments on 4.0.2. Given my goal of getting to a 2.6.14 kernel, what are your suggestions? I'm OK w/ using a 3.x gcc or even switching from SUSE to some other platform if you think it would help. Regards, Mike ------ 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] |