All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@tuliptree.org>
To: linux-ia64@vger.kernel.org
Subject: Re: cross compiling ia64!
Date: Sun, 24 Aug 2003 01:23:02 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106168819600532@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106154319501965@msgid-missing>

On Fri, 2003-08-22 at 02:05, Ameya Mitragotri wrote:
> I have been trying ,rather unsuccessfully, to cross compile the linux
> kernel 2.6-test3 using the compiler inside the NUE 1.2.

NUE was useful when IPF hardware was hard to get, but that hasn't been a
problem for a long time.  As a result, NUE hasn't been updated in a
while, and has obsolete versions of tools.

> I get the following errors using gcc version 2.96-ia64-000717 snap
> 001117)

The 2.96-ia64-000717 release is ancient history now.  It shouldn't be
used anymore.

> Replaced the gcc with 3.0.1 & binutils with 2.11. The binutils still
> gave problems, replaced them with 2.14. This took care of the assembler

gcc-3.0.1 and binutils-2.11 are also both old tool versions. 
binutils-2.14 is the latest release and should be OK.  Gcc is at 3.3.1
now, but 3.2 is probably also usable.

> My guess that 3.0.1 may not be the correct version for compiling 2.6. I
> have also tried to compile 2.95.3 (as suggested in the README) for ia64,
> but it seem that 2.95.3 does not support ia64 configuration. Any
> pointers/references to solve this?

The IA-64 port was written after gcc-2.95 was released.  Anyone
recommending gcc-2.95 for IA-64 is confused.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com


  reply	other threads:[~2003-08-24  1:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-22  9:17 cross compiling ia64! Ameya Mitragotri
2003-08-24  1:23 ` Jim Wilson [this message]
2003-08-24  2:19 ` mbp

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=marc-linux-ia64-106168819600532@msgid-missing \
    --to=wilson@tuliptree.org \
    --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.