public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: casteyde.christian@free.fr To: gcc-gnats@gcc.gnu.org Subject: bootstrap/8151: GCC 3.2 fails to bootstrap with glib 2.3 Date: Sat, 05 Oct 2002 02:46:00 -0000 [thread overview] Message-ID: <20021005094519.7705.qmail@sources.redhat.com> (raw) >Number: 8151 >Category: bootstrap >Synopsis: GCC 3.2 fails to bootstrap with glib 2.3 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sat Oct 05 02:46:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: casteyde.christian@free.fr >Release: 3.2 >Organization: >Environment: >Description: Linux 2.4.19/glibc 2.3/make 3.80/binutils 2.13 (test of integration) Actually, gcc did compile itself, but failed to build the libstdc++. Failure was "unknown __newlocale" in libstdc++ build, certainly due to glibc 2.3 header change. Quite difficult to find stable couple of glibc/gcc that compiles each other: glibc 2.2.5 fails with gcc 3.2 (since 3.1.1 actually), glibc 2.2.6 would but is not out, glibc 2.3 succeeded but broke gcc now. Hence it would be nice (if this is a gcc bug) to be fixed for gcc 3.2.1 (last couple that worked was 2.2.5 / 3.1). >How-To-Repeat: I guess building libstdc++ would suffice. >Fix: Don't known if it is a regression from glibc 2.3. Maybe this bug report is not in the right place. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-10-05 9:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-05 2:46 casteyde.christian [this message] 2003-05-08 5:06 Dara Hazeghi 2003-05-08 5:16 Dara Hazeghi 2003-05-08 9:06 Dara Hazeghi 2003-05-08 10:51 giovannibajo
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=20021005094519.7705.qmail@sources.redhat.com \ --to=casteyde.christian@free.fr \ --cc=gcc-gnats@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: linkBe 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).