On Tue, Sep 07, 1999 at 04:00:25PM -0700, Dan Jakubiec wrote:
> 2) Would it be better to add a "-D/usr/include" instead the the above
> defines? I am building a gcc cross-compiler for an ARM Linux system on an
> Intel Linux box. Will the system header files be close enough, or should I
> not take this chance?
I think you should build a parallel include tree, something like /usr/arm-include
with includes from ARM libc (I don't know if there are any differences in include
files) and the proper subdirectories from the ARM version of kernel source
(asm, linux, net, scsi subdirs).
> 3) Finally, I think the reason I hit this problem is that the Linux source
> base does not contain all the header files I need (such as stdlib.h,
> unistd.h, etc.). Why are these files not in the Linux kernel source base?
> Where do they come from?
Kernel code can't rely on libc (ie, you can't call malloc or printf from
kernel-space). Since the header files you mention are part of libc, and
can therefore be used only by user-space programs, they can't be distributed
with kernel sources.
Hope it helps,
Marco
========================================================================
Marco Pantaleoni [EMAIL PROTECTED]
Padova, Italy Tel: ++39-49-686951
Software Engineering for the people - PLUTO Linux User Group
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
