tweaking the sanitized headers for sh3eb build

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

  here's some followup to the problem i got earlier and how i (appear
to have) fixed it.  the build is progressing as we speak -- it may
fail later, but at least not for that reason.

  to set up the (sanitized) headers for my SH3 build, i just untarred
them into the right place, verified that "include/linux/version.h"
existed (it did), and created the appropriate symlink that would
normally be created by the config process:

  asm -> asm-sh		(in my case)

however, the build eventually failed claiming there was no "asm/ubc.h"
file and, sure enough, there wasn't.  i checked a stock 2.6.11.2
source tree and that file existed.  not only that, but it further
included <asm/cpu/ubc.h>.

 there was also no "asm-sh/cpu" directory, but there were a number of
more specific "cpu-sh2", "cpu-sh3" and so on directories so, guessing
wildly, i

  1) copied the <asm/ubc.h> file from the stock kernel tree, and
  2) created a symlink "cpu" -> "cpu-sh3" to satisfy that include
(since i'm guessing that's what the kernel config process would have
done anyway)

  thus far, it seems to have worked, although the build may certainly
fail later for other reasons.

  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