building bleeding-edge sh3eb toolchain with sanitized headers
Robert P. J. Day
rpjday@mindspring.com
Sat Apr 9 21:30:00 GMT 2005
here's what i just finished doing that *seemed* to build an sh3eb
toolchain with fairly recent components. the bits and pieces:
gcc-4.1-20050327
glibc-20050402 (and corresponding linuxthreads via CVS)
binutils-2.15.96
linux-2.6.11.2 sanitized headers (in place of kernel source tree)
(using gcc-3.4.3 native compiler on FC3 host system)
sh3eb.dat:
TARGET=sh3eb-unknown-linux-gnu
TARGET_CFLAGS="-O -mb -m3"
GLIBC_CONFIGPARMS="no-z-defs=yes"
gcc-4.1-20050327-glibc-20050402.dat:
BINUTILS_DIR=binutils-2.15.96
GCC_DIR=gcc-4.1-20050327
GLIBC_DIR=glibc-20050402
LINUX_DIR=linux-2.6.11.2
GLIBCTHREADS_FILENAME=glibc-linuxthreads-20050402
EXTRA_TARGET_CFLAGS="-fno-unit-at-a-time"
patches/glibc-20050402/make-install-lib-all.patch (the only patch)
hacks to crosstool.sh:
- remove entire section for preparing kernel headers, leave:
cd $LINUX_DIR
...
mkdir -p $HEADERDIR
cp -r include/linux $HEADERDIR
cp -r include/asm-${ARCH} $HEADERDIR/asm
# cp -r include/asm-generic $HEADERDIR/asm-generic (not there)
- unpack and patch software, don't build yet
- install sanitized headers in build directory where kernel source
would normally go, and:
symlink "asm" -> "asm-sh"
copy in "asm-sh/ubc.h" from 2.6.11.2 regular source tree
symlink "cpu" -> "cpu-sh3"
- and build ...
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
More information about the crossgcc
mailing list