Crosstool for MPC823

Dan Kegel
Fri Oct 7 14:14:00 GMT 2005

el_gast wrote:
>>1) What was the symptom with the bad memset.S?
>>How did you know it was bad?
> In normal opperation, the CPU-Load would be 100% and nothing is going on.
> Debugget with GDB, there is a segmentationfault in memset().

Can you file a bug at
describing the problem and what you had to do to fix it?

>>2) Your comment says that memset.S is wrong for ppc403, too,
>>is that right?  Should we remove it there, too?
> The original tipp abaut this is from Wolfgan Denk (
> and the comment is from him. I think is's right.

Thanks.  I wonder if that applies to the ppc405, too.

> The crosstool failed in this step:
> hd@el-gast:~$ powerpc-823-linux-gnu-gcc test.c 
> test.c: In function `main':
> test.c:4: error: `PATH_MAX' undeclared (first use in this function)
> test.c:4: error: (Each undeclared identifier is reported only once
> test.c:4: error: for each function it appears in.)
> I dont now why PATH_MAX is undeclared, simply delete it was the easyest
> way ;)

Ah, but I do.

The 'right' way to fix this might be to use the
sanitized kernel headers by adding the line
to your .dat file as I described in
Maybe I should do that by default in the next crosstool,
since it seems to work so well.

for other people who ran into this, and fixed it manually a different way.

Let me know if that helps!
- Dan

Trying to get a job as a c++ developer?  See

Want more information?  See the CrossGCC FAQ,
Want to unsubscribe? Send a note to

More information about the crossgcc mailing list