All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Christiansen <smc@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Trouble building cross compilers
Date: Thu, 21 Mar 2002 20:02:32 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905313@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905309@msgid-missing>

On Wed, Mar 20, 2002 at 06:30:47PM -0800, Jesse Barnes wrote:
> I have a couple of questions about cross compiling with gcc 3.0:
> 
> 1) is it possible to build an x86 hosted gcc 3.0 ia64 cross compiler
>    without nue?  Or, which packages do I need to build a gcc cross
>    compiler?

I've not been able to build an x86 to ia64 cross compiler using 3.0
"out of the box".  I have a patch for 3.0.4 in the tarball at

http://www.ibm.com/developerworks/oss/linux/tools/

which seems to work.  It's a hack, so no guarantees.

The 3.1 pre-release branch works fine, so you might consider using CVS
or a pre-release snapshot.  See http://gcc.gnu.org

The gcc mailing list thread beginning with the following may also
be helpful.

http://gcc.gnu.org/ml/gcc/2002-02/msg00585.html

And here's another useful resource, if you haven't already discovered it:

http://www.objsw.com/CrossGCC/


-- 
Steve Christiansen <smc@us.ibm.com>
IBM Linux Technology Center
503-578-4177  IBM T/L: 775-4177
http://www.ibm.com/linux/ltc


  parent reply	other threads:[~2002-03-21 20:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-21  2:30 [Linux-ia64] Trouble building cross compilers Jesse Barnes
2002-03-21 10:28 ` Andreas Schwab
2002-03-21 20:02 ` Steve Christiansen [this message]
2002-03-21 20:48 ` Jim Wilson
2002-03-21 21:01 ` Jim Wilson
2002-03-22  0:28 ` Jesse Barnes
2002-03-22  0:57 ` Keith Owens
2002-03-22  1:02 ` Jesse Barnes

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-105590701905313@msgid-missing \
    --to=smc@us.ibm.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.