crosstool.sh and sanitized headers

["Robert P. J. Day" <rpjday at mindspring dot com>]

  i was going to take a shot at using the 2.6.11.2 sanitized headers
in another SH3EB build, and i was curious about what hacks i'd have to
apply to crosstool.sh to handle this.

  obviously, there's a whole section in crostool.sh for preparing the
kernel headers that can be bypassed if you've already installed your
sanitized headers, mostly skipping configuration since there's no
makefile.  what i did with the headers:

  - copied them precisely where the build process would look for
	them in the build directory
  - symlinked "asm" -> "asm-sh"
  - verified that include/linux/version.h already exists

however, at the end of that section, there is one "cp" command that's
not going to work:

  cp -r include/asm-generic $HEADERDIR/asm-generic

there is no "asm-generic" directory at that location in the headers.
i'm not sure whether i should bypass this step or whether there's a
normal configuration step that creates this.  i don't think the latter
is true, as that directory exists in normal kernel source.

  thoughts?

rday

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