From: Andrew Morton <akpm@osdl.org>
To: linux-ia64@vger.kernel.org
Subject: Re: gcc problems
Date: Sat, 07 Feb 2004 05:49:47 +0000 [thread overview]
Message-ID: <20040206214947.686e6bbf.akpm@osdl.org> (raw)
In-Reply-To: <20040206000058.7e928d80.akpm@osdl.org>
Jim Wilson <wilson@specifixinc.com> wrote:
>
> On Fri, 2004-02-06 at 09:34, Wichmann, Mats D wrote:
> > If it's a question of glibc 2.2.x vs. 2.3.x, there are
> > ia64 Linux distributions based on glibc 2.2 that work
> > pretty well - SUSE's SLES8, for example.
>
> gcc-3.x will have some problems when used on a glibc-2.2.x system, but
> most of them are obscure, and probably none of them apply to building
> kernels, because the kernel doesn't link in glibc.
>
> It is reasonable that gcc should be buildable though. I believe the
> following patch solves this problem. I just ifdefed out the code for
> old glibc versions. I see no point in trying to make this work, because
> unwinding will fail (for user apps) for other reasons if you are using
> glibc-2.2.4.
>
> I don't have access to a glibc-2.2.4 system for testing. I can't use
> such old systems for gcc 3.x development. It works OK for glibc 2.3,
> where it has no effect. If someone tells me that this does work, then I
> can check it into the FSF gcc sources.
>
> 2004-02-06 James E Wilson <wilson@specifixinc.com>
>
> * config/ia64/linux.h (MD_FALLBACK_FRAME_STATE_FOR): Only define for
> glibc 2.3 or better.
This gave me a successful build of
gcc (GCC) 3.5.0 20040206 (experimental)
on
linux-tiger:/usr/src/gcc-cvs-obj> cat /etc/issue
Red Hat Linux Advanced Server release 2.1AS (Derry)
linux-tiger:/usr/src/gcc-cvs-obj> rpm -q glibc
glibc-2.2.4-32.3
Thanks. Ship it.
next prev parent reply other threads:[~2004-02-07 5:49 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
2004-02-06 17:34 ` Wichmann, Mats D
2004-02-07 2:05 ` Jim Wilson
2004-02-07 5:49 ` Andrew Morton [this message]
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=20040206214947.686e6bbf.akpm@osdl.org \
--to=akpm@osdl.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