From: Dan Kegel <dank@kegel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: gcc problems
Date: Fri, 06 Feb 2004 16:50:18 +0000 [thread overview]
Message-ID: <4023C5CA.3010405@kegel.com> (raw)
In-Reply-To: <20040206000058.7e928d80.akpm@osdl.org>
Andrew Morton wrote:
> Andreas Schwab <schwab@suse.de> wrote:
>
>>The fields were named differently in old versions of glibc, but the whole
>> layout didn't change in any way.
>>
>> - unsigned long int sc_rsvd[16];/* reserved for future use */
>> + unsigned long int sc_rbs_base;/* NULL or new base of sighandler's rbs */
>> + unsigned long int sc_loadrs; /* see description above */
>> + unsigned long int sc_ar25; /* cmp8xchg16 uses this */
>> + unsigned long int sc_ar26; /* rsvd for scratch use */
>> + unsigned long int sc_rsvd[12];/* reserved for future use */
>>
>> > The easiest workaround is probably to install libunwind on your system
>>
>> The right fix is not to use a 2 years old glibc.
>
>
> That's not very old. One shouldn't have to upgrade libc just to build gcc?
Did the two-year-old libc really support ia64 well? I guess Itanium 1 was
out then, but those were early days...
- Dan
next prev parent reply other threads:[~2004-02-06 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 8:00 gcc problems Andrew Morton
2004-02-06 8:37 ` Ian Wienand
2004-02-06 8:43 ` Andrew Morton
2004-02-06 9:49 ` Jim Wilson
2004-02-06 11:46 ` Andreas Schwab
2004-02-06 16:30 ` Andrew Morton
2004-02-06 16:50 ` Dan Kegel [this message]
2004-02-06 17:34 ` Wichmann, Mats D
2004-02-07 2:05 ` Jim Wilson
2004-02-07 5:49 ` Andrew Morton
2004-02-10 7:37 ` David Mosberger
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=4023C5CA.3010405@kegel.com \
--to=dank@kegel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox