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] |
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.
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 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] |