From: Len Brown <len.brown@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: cross-compiling ia64 kernels?
Date: Wed, 01 Nov 2006 04:02:43 +0000 [thread overview]
Message-ID: <200610312302.43369.len.brown@intel.com> (raw)
In-Reply-To: <617E1C2C70743745A92448908E030B2AB91DF8@scsmsx411.amr.corp.intel.com>
> > > http://www.kegel.com/crosstool/
I scribbled on demo-ia64.sh to build the latest:
--- demo-ia64.sh.orig 2006-10-31 22:50:46.000000000 -0500
+++ demo-ia64.sh 2006-10-31 22:50:29.000000000 -0500
@@ -18,6 +18,8 @@
#eval `cat ia64.dat gcc-3.3.4-glibc-2.2.5.dat` sh all.sh --notest # fails
#eval `cat ia64.dat gcc-3.4.0-glibc-2.3.2.dat` sh all.sh --notest
#eval `cat ia64.dat gcc-3.4.1-glibc-2.3.3.dat` sh all.sh --notest
-eval `cat ia64.dat gcc-3.4.2-glibc-2.3.3.dat` sh all.sh --notest
+#eval `cat ia64.dat gcc-3.4.2-glibc-2.3.3.dat` sh all.sh --notest
+
+eval `cat ia64.dat gcc-4.1.0-glibc-2.3.6.dat` sh all.sh --notest
echo Done.
And updated the .dat file to use linux 2.6.18
(dunno what the 2.6.12.0 stuff is about)
--- gcc-4.1.0-glibc-2.3.6.dat.orig 2006-10-31 22:49:40.000000000 -0500
+++ gcc-4.1.0-glibc-2.3.6.dat 2006-10-31 22:01:53.000000000 -0500
@@ -2,7 +2,7 @@
GCC_CORE_DIR=gcc-3.3.6
GCC_DIR=gcc-4.1.0
GLIBC_DIR=glibc-2.3.6
-LINUX_DIR=linux-2.6.15.4
+LINUX_DIR=linux-2.6.18
LINUX_SANITIZED_HEADER_DIR=linux-libc-headers-2.6.12.0
GLIBCTHREADS_FILENAME=glibc-linuxthreads-2.3.6
GDB_DIR=gdb-6.4
built it, but it bombed out in the glibc:
$ sh demo-ia64.sh
....
/home/lenb/crosstool-0.42/build/ia64-unknown-linux-gnu/gcc-4.1.0-glibc-2.3.6/build-glibc/nscd/cache.o: In function `cache_add':
cache.c:(.text+0xf22): undefined reference to `__sync_bool_compare_and_swap_si'
cache.c:(.text+0xfe2): undefined reference to `__sync_fetch_and_add_si'
collect2: ld returned 1 exit status
make[2]: *** [/home/lenb/crosstool-0.42/build/ia64-unknown-linux-gnu/gcc-4.1.0-glibc-2.3.6/build-glibc/nscd/nscd] Error 1
make[2]: Leaving directory `/home/lenb/crosstool-0.42/build/ia64-unknown-linux-gnu/gcc-4.1.0-glibc-2.3.6/glibc-2.3.6/nscd'
make[1]: *** [nscd/others] Error 2
make[1]: Leaving directory `/home/lenb/crosstool-0.42/build/ia64-unknown-linux-gnu/gcc-4.1.0-glibc-2.3.6/glibc-2.3.6'
make: *** [all] Error 2
But apparently it got far enough to build a gcc for building IA64 kernels, because that works.
export ARCH=ia64
export CROSS_COMPILE=ia64-unknown-linux-gnu-
export PATH=$PATH:/opt/crosstool/gcc-4.1.0-glibc-2.3.6/ia64-unknown-linux-gnu/bin
MAKE="time make ARCH=$ARCH CROSS_COMPILE=$CROSS_COMPILE"
$MAKE -j4
thanks,
-Len
next prev parent reply other threads:[~2006-11-01 4:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 21:20 cross-compiling ia64 kernels? Luck, Tony
2006-10-30 22:25 ` Bob Picco
2006-10-30 22:30 ` Ian Wienand
2006-10-31 7:12 ` Len Brown
2006-10-31 12:15 ` Bob Picco
2006-11-01 4:02 ` Len Brown [this message]
2006-11-01 13:33 ` Andreas Schwab
2006-11-01 15:26 ` Christoph Lameter
2006-11-01 15:38 ` Andreas Schwab
2006-11-01 17:06 ` Christoph Lameter
2006-11-01 17:43 ` Andreas Schwab
2006-11-01 17:45 ` Christoph Lameter
2006-11-01 19:15 ` Andreas Schwab
2006-11-01 19:35 ` Christoph Lameter
2006-11-01 19:46 ` Christoph Lameter
2006-11-01 22:24 ` Andreas Schwab
2006-11-01 23:30 ` Christoph Lameter
2006-11-02 0:36 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200610312302.43369.len.brown@intel.com \
--to=len.brown@intel.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox