Re: build error for sh4 using latest snapshot of gcc

[Dan Kegel <dank at kegel dot com>]

Robert P. J. Day wrote:
> > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24445
> >
> > Thanks!  But to really count, the bug report needs a preprocessed
> > source file
>
> i understand that, but that's asking a lot of someone (i.e., me) who's
> still figuring his way around here to dig into the glibc source and
> try to construct from that a single source file that generates the
> same error that crosstool produced.

Yeah.  But really, it's not that hard!  In fact, it's kind of mechanical!
Here's what you do:
1. Run the build and save a log file.
2. Look at the log to figure out what directory the failed command was run in
3. Look at the log to find what PATH was set to
4. Create a three-(long-)line shell script that sets the PATH,
   cd's to the directory, and runs the failed command
   (in this case, the monster long gcc command that starts with
     sh4-unknown-linux-gnu-gcc  ../sysdeps/generic/strtok.c
    and ends with
     -MT
    /home/rpjday/ct/crosstool-0.38.new/build/sh4-unknown-linux-gnu/gcc-4.1-20051015-glibc-2.3.5/build-glibc/string/strtok.os )
5. Verify that this shell script reproduces the problem
   It should take about one or two seconds to run
6. Modify the command by adding the -save-temps option
7. Run it again
8. Voila, you should have a strtok.i file ready to compress and upload as an
   attachment to your bug!


> i figured a partial bug report was better than none at all.

Indeed, it is.

Thanks,
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