Re: problem with compiling for sh3eb

["Arno Schuring" <aelschuring at hotmail dot com>]

> > The linux-libc-headers package gives you a subdirectory tree
> > containing (among others):
> >
> > include/linux
> > include/asm-$ARCH
> > include/scsi
> >
> > You should copy at least the linux/ subdir into where gcc expects to
> > find its headers (preferably $SYS-ROOT/usr/include) and copy
> > asm-$ARCH to include/asm. So far, I have never needed the other
> > subdirectories.
>
> oh, i didn't realize that.  so, from the perspective of a config file,
> i can just install those sanitized headers relative to where they'd
> normally be found relative to ${GCC_DIR} and things should work?
> cool.  i'll give that a shot this morning.

Uhm... just to make sure: I did write "where gcc expects to find the 
target's system headers", didn't I? They're not meant to replace gcc's 
internal headers. They should be placed in the same location where glibc 
places its include/ directory (and, for that matter, where crosstool copies 
the kernel headers).

> *then* i'll go back and figure out what means "sanitized". :-)

Sanitized, in this case: compatible with glibc. I tried without, and ran 
into a couple of error messages when building packages with the toolchain. 
You will know when you see messages like:

gcc: <linux/someheader.h>: incorrect redefinition of <symbol>, included 
from:
gcc: <libc-header.h>: previous definition was here

I don't have a live example ready for you, but you get the idea.


Arno


 np: Vangelis - Hispanola 

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com