From: Jim Wilson <wilson@tuliptree.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Building IA-64 toolchain
Date: Thu, 08 May 2003 17:24:04 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705694@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705654@msgid-missing>
On Thu, 2003-05-08 at 04:21, navin wrote:
> ../../gcc-3.2/gcc/config/ia64/fde-glibc.c:42:3: #error You need GLIBC
> 2.2.4 or later on IA-64 Linux
The glibc copy you are using is too old. This glibc will work with gcc
2.96 (sic), but it won't work with gcc 3. There were related changes
made to glibc and gcc to enable unwind info to work correctly, which was
needed for C++ exception handling support. Thus you can't use a new gcc
with an old glibc or vice versa.
David Mosberger mentioned testdrive.hp.com or something like that.
Perhaps you could get an account there, and then get a newer copy of the
glibc header files from there.
Jim
prev parent reply other threads:[~2003-05-08 17:24 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
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 [this message]
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-105590723705694@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox