This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: tweaking the sanitized headers for sh3eb build



[...]
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)

If you really want to be sure, I'd say you have to contact Mariusz Mazur (the maintainer of the linux-libc-headers) about it, but it seems like a sane way to do.


Just did a make prepare on a vanilla kernel tree, it seems it does the following:

aschuring@golem:~/work/linux-2.6.7 > make defconfig ARCH=sh
[...]
aschuring@golem:~/work/linux-2.6.7 > make prepare ARCH=sh
 Making asm-sh/cpu -> asm-sh/cpu-sh3 link
 Making asm-sh/mach -> asm-sh/unknown link
make[1]: `include/asm-sh/machtypes.h' is up to date.

Which with -n translates to:

ln -sf cpu-sh3 include/asm-sh/cpu
ln -sf unknown include/asm-sh/mach

So you were correct. You might run into a missing mach-dir later, also. I guess the sanitized headers need some postprocessing for some architectures, though this might be difficult to incorporate in crosstool.

Arno


np: Marillion - Beautiful


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]