Re: Crosstool for MPC823

[Dan Kegel <dank at kegel dot com>]

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().

Interesting!
Can you file a bug at http://sources.redhat.com/bugzilla
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 (http://www.denx.de)
> 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
LINUX_SANITIZED_HEADER_DIR=linux-libc-headers-2.6.11.2
to your .dat file as I described in
http://sources.redhat.com/ml/crossgcc/2005-10/msg00004.html
Maybe I should do that by default in the next crosstool,
since it seems to work so well.

See http://sources.redhat.com/ml/crossgcc/2005-01/msg00078.html
and http://www.linuxforums.org/forum/ptopic41994.html
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 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