build error for sh4 using latest snapshot of gcc
Wed Oct 19 21:11:00 GMT 2005
Robert P. J. Day wrote:
>>Thanks! But to really count, the bug report needs
>>a preprocessed source
>>file and minimal commandline to reproduce the crash from
>>that one source file. That's not too hard, and
>>will really help the guys fixing the bug.
> just to clarify one point, the step that failed involved running, not
> gcc proper, but the sh4-unknown-linux-gnu-gcc command produced during
> the "build-gcc-core" step.
That's ok - both share the same bug, probably.
> how would one reduce that to a simple example to incorporate into a
> bug report, since the bug testers wouldn't have access to that command
> at their end? or am i missing something here?
Having the preprocessed source means they can
build any old sh4 compiler and reproduce the
problem without worrying about grabbing the
glibc you were trying to build.
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 firstname.lastname@example.org
More information about the crossgcc