public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: navin <navin@students.iiit.net>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Building IA-64 toolchain
Date: Wed, 07 May 2003 17:52:58 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705652@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705654@msgid-missing>

On Wed, 7 May 2003, David Mosberger wrote:

>>>>>> On Wed, 7 May 2003 21:33:11 +0530 (IST), navin <navin@students.iiit.net> said:
>
>  navin> Also from some of the previous posts i found that if i am
>  navin> building on a pentium or some other machine there is a trick
>  navin> involved.Andreas Jaegar told me that i had to install-headers
>  navin> before compiling the bootstrap gcc.He said to contact you
>  navin> guys as i don't have the headers for ia64.I have the sources
>  navin> for kernel which contain asm-ia64 and glibc-2.3.I don't know
>  navin> how to avoid the error.
>
>Have you tried NUE?  It's available here:
>
>  http://www.software.hp.com/products/LIA64/overview2a.htm
>

Yeah i have tried NUE.It is good and gcc is 2.95 something and glibc 
2.0. 
	I even tried copying the nue ia64-hp-something headers files and 
giving gcc the option with --header to that directory but it messed up as 
i previously mentioned

I don't know what the error is.Can you tell me where i can find the docs 
or how do i build the parallel glibc and gcc . It is nasty but it works.
I saw this on earlier lists other ports but hardly found the procedure.

The problem is that building an alpha target is easy .But when i apply 
the same rules to ia64 it breaks.GCC breaks.




  parent reply	other threads:[~2003-05-07 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 15:14 [Linux-ia64] Building IA-64 toolchain Jim Wilson
2003-05-07 15:20 ` Jim Wilson
2003-05-07 16:15 ` navin
2003-05-07 17:41 ` David Mosberger
2003-05-07 17:52 ` navin [this message]
2003-05-07 18:05 ` David Mosberger
2003-05-07 18:14 ` Randolph Chung
2003-05-08  8:33 ` navin
2003-05-08 17:24 ` Jim Wilson

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-105590723705652@msgid-missing \
    --to=navin@students.iiit.net \
    --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