All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: cross-compiling ia64 kernels?
Date: Tue, 31 Oct 2006 07:12:12 +0000	[thread overview]
Message-ID: <200610310212.12778.len.brown@intel.com> (raw)
In-Reply-To: <617E1C2C70743745A92448908E030B2AB91DF8@scsmsx411.amr.corp.intel.com>

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

  parent reply	other threads:[~2006-10-31  7:12 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 [this message]
2006-10-31 12:15 ` Bob Picco
2006-11-01  4:02 ` Len Brown
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=200610310212.12778.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.