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] |
i'm doing another build for sh3eb and i think i've sort of isolated a problem (at least for this).
what *works* is that i can build the toolchain with san. headers and then configure a kernel source tree and use that toolchain to compile the kernel as a whole separate operation. (for this to work, i have to set PATH appropriately, and set CROSS_COMPILE=sh3eb-unknown-linux-gnu). in short, it works if i do it in two steps.
if i try to do it all in one step, the compile of the kernel fails as if it's using the wrong compiler. i'm redoing the build and saving the output for inspection but does the above make any sense? (the errors i get from the kernel build are as if the compiler doesn't understand what are obviously SH3-specific compile options.)
By "in one step", what do you mean exactly? Telling crosstool to use the non-sanitized headers, perhaps? - Dan
-- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
------ 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] |