cross-compiling ia64 kernels?

cross-compiling ia64 kernels?

[Luck, Tony]

Does anyone have a recipe for tools & scripts to cross-compile
a current ia64 kernel?  I have lots of machines sitting in the
lab waiting for me to run native builds so I've never bothered
to look into cross environments.  But I've had some inquiries
on how to cross-build from some people with less h/w ready to
do their bidding.

-Tony

Re: cross-compiling ia64 kernels?

[Bob Picco]

luck wrote:	[Mon Oct 30 2006, 04:20:50PM EST]
> Does anyone have a recipe for tools & scripts to cross-compile
> a current ia64 kernel?  I have lots of machines sitting in the
> lab waiting for me to run native builds so I've never bothered
> to look into cross environments.  But I've had some inquiries
> on how to cross-build from some people with less h/w ready to
> do their bidding.
> 
> -Tony
Tony,

I build all my arches on x86_64 with crosstool. My current tool chain
for x86 and ia64 is derived from gcc-3.4.1-glibc-2.3.2.  For powerpc
I'm using  gcc-3.4.2-glibc-2.3.3. It doesn't require significant effort
after downloading Dan Kegel's crosstool source and build tools at:
http://www.kegel.com/crosstool/
. Select the tool chain gcc revision and
binutil revision in Dan's arch specific script file and build. Then one
only has to add the installed compiler path to your shell environment path.
For example ia64 for me is 
/usr/local/crosstool/gcc-3.4.1-glibc-2.3.2/ia64-unknown-linux-gnu/bin.
After that 
	make ARCH=ia64 CROSS_COMPILE=ia64-unknown-linux-gnu- whatever
should work just fine.

I'm not certain whether this is all the information you require:

bob

Re: cross-compiling ia64 kernels?

[Ian Wienand]

On Mon, Oct 30, 2006 at 01:20:50PM -0800, Luck, Tony wrote:
> Does anyone have a recipe for tools & scripts to cross-compile
> a current ia64 kernel?

Yes

Start at [1]; there are links to about 3 different ways to do it
there.  You can try crosstool from [2] as well

If you use Debian, I have some pre-built .debs which may work for you,
see [3], but it's pretty easy to build your own; see [4].

What I usually do is from an IA64 host use distcc to remote machines
with IA64 cross compilers.

-i

[1] http://www.gelato.unsw.edu.au/IA64wiki/CrossCompilation
[2] http://www.kegel.com/crosstool/
[3] http://www.gelato.unsw.edu.au/IA64wiki/GelatoDebianRepository
[4] http://www.gelato.unsw.edu.au/IA64wiki/DebianCrossCompiler

Re: cross-compiling ia64 kernels?

[Len Brown]

On Monday 30 October 2006 17:25, Bob Picco wrote:
> luck wrote:	[Mon Oct 30 2006, 04:20:50PM EST]
> > Does anyone have a recipe for tools & scripts to cross-compile
> > a current ia64 kernel?  I have lots of machines sitting in the
> > lab waiting for me to run native builds so I've never bothered
> > to look into cross environments.  But I've had some inquiries
> > on how to cross-build from some people with less h/w ready to
> > do their bidding.
> > 
> > -Tony
> Tony,
> 
> I build all my arches on x86_64 with crosstool. My current tool chain
> for x86 and ia64 is derived from gcc-3.4.1-glibc-2.3.2.  For powerpc
> I'm using  gcc-3.4.2-glibc-2.3.3. It doesn't require significant effort

What is the newest compiler version that works?
A moment ago I updated demo-ia64.sh to try to build
gcc-4.1.0-glibc-2.3.6 and it bailed out before completing.

thanks,
-Len

> after downloading Dan Kegel's crosstool source and build tools at:
> http://www.kegel.com/crosstool/
> . Select the tool chain gcc revision and
> binutil revision in Dan's arch specific script file and build. Then one
> only has to add the installed compiler path to your shell environment path.
> For example ia64 for me is 
> /usr/local/crosstool/gcc-3.4.1-glibc-2.3.2/ia64-unknown-linux-gnu/bin.
> After that 
> 	make ARCH=ia64 CROSS_COMPILE=ia64-unknown-linux-gnu- whatever
> should work just fine.
> 
> I'm not certain whether this is all the information you require:
> 
> bob

Re: cross-compiling ia64 kernels?

[Bob Picco]

Len Brown wrote:	[Tue Oct 31 2006, 02:12:12AM EST]
> On Monday 30 October 2006 17:25, Bob Picco wrote:
> > luck wrote:	[Mon Oct 30 2006, 04:20:50PM EST]
> > > Does anyone have a recipe for tools & scripts to cross-compile
> > > a current ia64 kernel?  I have lots of machines sitting in the
> > > lab waiting for me to run native builds so I've never bothered
> > > to look into cross environments.  But I've had some inquiries
> > > on how to cross-build from some people with less h/w ready to
> > > do their bidding.
> > > 
> > > -Tony
> > Tony,
> > 
> > I build all my arches on x86_64 with crosstool. My current tool chain
> > for x86 and ia64 is derived from gcc-3.4.1-glibc-2.3.2.  For powerpc
> > I'm using  gcc-3.4.2-glibc-2.3.3. It doesn't require significant effort
> 
> What is the newest compiler version that works?
> A moment ago I updated demo-ia64.sh to try to build
> gcc-4.1.0-glibc-2.3.6 and it bailed out before completing.
I don't know. It has been several months since building with crosstool.
I'm in the middle of apartment moving.  I'll attempt to investigate
later this week.

You might want to look at Dan's results section on his website.
> 
> thanks,
> -Len
your welcome,

bob
> 
> > after downloading Dan Kegel's crosstool source and build tools at:
> > http://www.kegel.com/crosstool/
> > . Select the tool chain gcc revision and
> > binutil revision in Dan's arch specific script file and build. Then one
> > only has to add the installed compiler path to your shell environment path.
> > For example ia64 for me is 
> > /usr/local/crosstool/gcc-3.4.1-glibc-2.3.2/ia64-unknown-linux-gnu/bin.
> > After that 
> > 	make ARCH=ia64 CROSS_COMPILE=ia64-unknown-linux-gnu- whatever
> > should work just fine.
> > 
> > I'm not certain whether this is all the information you require:
> > 
> > bob
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: cross-compiling ia64 kernels?

[Len Brown]

> > > 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

Re: cross-compiling ia64 kernels?

[Andreas Schwab]

Len Brown <len.brown@intel.com> writes:

> 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

glibc 2.3.6 is about a year old and predates gcc 4.1.0 by 3 months. You
should really use a more recent glibc.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: cross-compiling ia64 kernels?

[Christoph Lameter]

On Wed, 1 Nov 2006, Andreas Schwab wrote:

> glibc 2.3.6 is about a year old and predates gcc 4.1.0 by 3 months. You
> should really use a more recent glibc.

I tried debians toolchain-source before and it also fails.

Just tried to download crosstool-0.42. It seems to build glibc-2.3.3(?) 
and it fails to build glibc with

 GCC_SYSROOT_ARG_CORE=--without-headers
+ 
GCC_SYSROOT_ARG=--with-headers=/opt/crosstool/gcc-3.4.2-glibc-2.3.3/ia64-unknown-linux-gnu/ia64-unknown-linux-gnu/include
+ GLIBC_SYSROOT_ARG=prefix+ mkdir -p 
/opt/crosstool/gcc-3.4.2-glibc-2.3.3/ia64-unknown-linux-gnu/ia64-unknown-linux-gnu/lib
+ mkdir -p 
/opt/crosstool/gcc-3.4.2-glibc-2.3.3/ia64-unknown-linux-gnu/ia64-unknown-linux-gnu/usr/lib
+ echo

+ echo 'Building for --target=ia64-unknown-linux-gnu, 
--prefix=/opt/crosstool/gcc-3.4.2-glibc-2.3.3/ia64-unknown-linux-gnu'
Building for --target=ia64-unknown-linux-gnu, 
--prefix=/opt/crosstool/gcc-3.4.2-glibc-2.3.3/ia64-unknown-linux-gnu
+ test -z ''
+ echo Prepare kernel headers
Prepare kernel headers
+ cd 
/home/christoph/explore/crosstool-0.42/build/ia64-unknown-linux-gnu/gcc-3.4.2-glibc-2.3.3/linux-2.6.8
+ mkdir -p 
/opt/crosstool/gcc-3.4.2-glibc-2.3.3/ia64-unknown-linux-gnu/ia64-unknown-linux-gnu/include
+ test -z ''
+ test -f /home/christoph/explore/crosstool-0.42/ia64.config
+ cp /home/christoph/explore/crosstool-0.42/ia64.config .config
+ test -f .config
+ yes ''
+ make ARCH=ia64 oldconfig
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/split-include
  HOSTCC  scripts/basic/docproc
  SHIPPED scripts/kconfig/zconf.tab.h
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/mconf.o
scripts/kconfig/mconf.c:91: error: static declaration of 'current_menu' 
follows non-static declaration
scripts/kconfig/lkc.h:63: error: previous declaration of 'current_menu' 
was here
make[1]: *** [scripts/kconfig/mconf.o] Error 1
make: *** [oldconfig] Error 2

Re: cross-compiling ia64 kernels?

[Andreas Schwab]

Christoph Lameter <clameter@sgi.com> writes:

> + make ARCH=ia64 oldconfig
>   HOSTCC  scripts/basic/fixdep
>   HOSTCC  scripts/basic/split-include
>   HOSTCC  scripts/basic/docproc
>   SHIPPED scripts/kconfig/zconf.tab.h
>   HOSTCC  scripts/kconfig/conf.o
>   HOSTCC  scripts/kconfig/mconf.o
> scripts/kconfig/mconf.c:91: error: static declaration of 'current_menu' 
> follows non-static declaration
> scripts/kconfig/lkc.h:63: error: previous declaration of 'current_menu' 
> was here
> make[1]: *** [scripts/kconfig/mconf.o] Error 1
> make: *** [oldconfig] Error 2

Your kernel sources are way out of date, this has been fixed more than two
years ago.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: cross-compiling ia64 kernels?

[Christoph Lameter]

On Wed, 1 Nov 2006, Andreas Schwab wrote:

> Your kernel sources are way out of date, this has been fixed more than two
> years ago.

uname -a

Linux pentium940 2.6.19-rc3 #4 SMP Sat Oct 28 17:26:34 PDT 2006 i686 GNU/Linux

Re: cross-compiling ia64 kernels?

[Andreas Schwab]

Christoph Lameter <clameter@sgi.com> writes:

> On Wed, 1 Nov 2006, Andreas Schwab wrote:
>
>> Your kernel sources are way out of date, this has been fixed more than two
               ^^^^^^^
>> years ago.
>
> uname -a
>
> Linux pentium940 2.6.19-rc3 #4 SMP Sat Oct 28 17:26:34 PDT 2006 i686 GNU/Linux

What does this have to do with the kernel sources?

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: cross-compiling ia64 kernels?

[Christoph Lameter]

On Wed, 1 Nov 2006, Andreas Schwab wrote:

> > Linux pentium940 2.6.19-rc3 #4 SMP Sat Oct 28 17:26:34 PDT 2006 i686 GNU/Linux
> What does this have to do with the kernel sources?

Frankly, I have no idea where the cross script gets its kernel from. I 
guessed that it was somehow related to the current running kernel version? 
Or does the cross script have the version hardcoded somewhere? Could not 
find it.

Re: cross-compiling ia64 kernels?

[Andreas Schwab]

Christoph Lameter <clameter@sgi.com> writes:

> Frankly, I have no idea where the cross script gets its kernel from. I 
> guessed that it was somehow related to the current running kernel version? 
> Or does the cross script have the version hardcoded somewhere? Could not 
> find it.

Read the build log.

> /home/christoph/explore/crosstool-0.42/build/ia64-unknown-linux-gnu/gcc-3.4.2-glibc-2.3.3/linux-2.6.8

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: cross-compiling ia64 kernels?

[Christoph Lameter]

On Wed, 1 Nov 2006, Andreas Schwab wrote:

> Read the build log.

Ok. It builds now.  One has to edit gcc-3.4.2-glibc-2.3.3.dat to have

BINUTILS_DIR=binutils-2.15
GCC_DIR=gcc-3.4.2
GLIBC_DIR=glibc-2.3.3
LINUX_DIR=linux-2.6.18
^^^^^^^^^^^^^^^^^^^^^^^
GLIBCTHREADS_FILENAME=glibc-linuxthreads-2.3.3

This looks like its pretty old software. Wonder if that will be worth it.

Re: cross-compiling ia64 kernels?

[Christoph Lameter]

On Wed, 1 Nov 2006, Christoph Lameter wrote:

> Ok. It builds now.  One has to edit gcc-3.4.2-glibc-2.3.3.dat to have

And it failed again:

mv -f 
/home/christoph/explore/crosstool-0.42/build/ia64-unknown-linux-gnu/gcc-3.4.2-glibc-2.3.3/build-glibc-headers/sysd-syscallsT 
/home/christoph/explore/crosstool-0.42/build/ia64-unknown-linux-gnu/gcc-3.4.2-glibc-2.3.3/build-glibc-headers/sysd-syscalls
make[1]: Failed to remake makefile 
`/home/christoph/explore/crosstool-0.42/build/ia64-unknown-linux-gnu/gcc-3.4.2-glibc-2.3.3/build-glibc-headers/config.make'.
make[1]: Leaving directory 
`/home/christoph/explore/crosstool-0.42/build/ia64-unknown-linux-gnu/gcc-3.4.2-glibc-2.3.3/glibc-2.3.3'
make[1]: Entering directory 
`/home/christoph/explore/crosstool-0.42/build/ia64-unknown-linux-gnu/gcc-3.4.2-glibc-2.3.3/glibc-2.3.3'
autoconf  sysdeps/ia64/elf/configure.in > sysdeps/ia64/elf/configure.new
autoconf: Undefined macros:
***BUG in Autoconf--please report*** AC_FD_MSG
make[1]: Failed to remake makefile 
`/home/christoph/explore/crosstool-0.42/build/ia64-unknown-linux-gnu/gcc-3.4.2-glibc-2.3.3/build-glibc-headers/config.make'.
make[1]: `sysdeps/gnu/errlist.c' is up to date.
make[1]: Leaving directory 
`/home/christoph/explore/crosstool-0.42/build/ia64-unknown-linux-gnu/gcc-3.4.2-glibc-2.3.3/glibc-2.3.3'
make: *** [sysdeps/gnu/errlist.c] Error 2

Building a cross compiler seems to be a waste of time. It just plainly 
never works right without spending a week or so fixing broken stuff all 
over the place.

Re: cross-compiling ia64 kernels?

[Andreas Schwab]

Christoph Lameter <clameter@sgi.com> writes:

> Building a cross compiler seems to be a waste of time. It just plainly 
> never works right without spending a week or so fixing broken stuff all 
> over the place.

Why you are trying to compile all this old stuff in the first place?

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: cross-compiling ia64 kernels?

[Christoph Lameter]

On Wed, 1 Nov 2006, Andreas Schwab wrote:

> Christoph Lameter <clameter@sgi.com> writes:
> 
> > Building a cross compiler seems to be a waste of time. It just plainly 
> > never works right without spending a week or so fixing broken stuff all 
> > over the place.
> 
> Why you are trying to compile all this old stuff in the first place?

Wasnt it you who suggested to use cross-tools for crosscompiling? Any 
other idea? Maybe the best thing is to go directly with the gcc sources.

Re: cross-compiling ia64 kernels?

[Andreas Schwab]

Christoph Lameter <clameter@sgi.com> writes:

> Wasnt it you who suggested to use cross-tools for crosscompiling?

I have never said anything like this.

> Any other idea? Maybe the best thing is to go directly with the gcc
> sources.

Of course.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."