public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/4068: [linux-x86] bootstrapping on libc5 systems
Date: Wed, 27 Nov 2002 08:04:00 -0000 [thread overview]
Message-ID: <20021119235604.12743.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/4068; it has been noted by GNATS.
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <bangerth@dealii.org>, <gcc-bugs@gcc.gnu.org>, <mengel@fnal.gov>,
<nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Cc:
Subject: Re: bootstrap/4068: [linux-x86] bootstrapping on libc5 systems
Date: Tue, 19 Nov 2002 23:49:07 +0000 (GMT)
On 19 Nov 2002 bangerth@dealii.org wrote:
> Old Synopsis: bootstrap fails on older Linux (Red Hat 5.2)
> New Synopsis: [linux-x86] bootstrapping on libc5 systems
The problem systems are specifically glibc 2.0, not libc5. For it
possibly to work the patch implied by the discussion I referenced is
needed - i.e.
--- gcc/config/i386/linux.h.orig Fri Nov 15 14:57:12 2002
+++ gcc/config/i386/linux.h Tue Nov 19 23:47:16 2002
@@ -228,7 +228,7 @@
signal-turned-exceptions for them. There's also no configure-run for
the target, so we can't check on (e.g.) HAVE_SYS_UCONTEXT_H. Using the
target libc1 macro should be enough. */
-#ifndef USE_GNULIBC_1
+#if !(defined (USE_GNULIBC_1) || (__GLIBC__ == 2 && __GLIBC_MINOR__ == 0))
#include <signal.h>
#include <sys/ucontext.h>
--
Joseph S. Myers
jsm28@cam.ac.uk
next reply other threads:[~2002-11-19 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 8:04 Joseph S. Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-27 7:50 bangerth
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=20021119235604.12743.qmail@sources.redhat.com \
--to=jsm28@cam.ac.uk \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).