public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp@gcc.gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/11193] New: Version 1.126 of libstdc++-v3/configure.in broke pre-installed newlib builds Date: Sun, 15 Jun 2003 05:31:00 -0000 [thread overview] Message-ID: <20030615053147.11193.hp@gcc.gnu.org> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11193 Summary: Version 1.126 of libstdc++-v3/configure.in broke pre- installed newlib builds Product: gcc Version: 3.4 Status: UNCONFIRMED Keywords: build Severity: normal Priority: P2 Component: libstdc++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: hp@gcc.gnu.org CC: bkoz@redhat.com,gcc-bugs@gcc.gnu.org GCC build triplet: Canadians are supposedly safe from harm by this bug. GCC host triplet: (any cross host) GCC target triplet: (any newlib target, e.g. most *-*-elf) Building libstdc++-v3 against already installed newlib doesn't work anymore since rev 1.126 of libstdc++-v3/configure.in. See discussion at <URL:http://gcc.gnu.org/ml/gcc-patches/2003-06/msg00321.html>.
next reply other threads:[~2003-06-15 5:31 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-06-15 5:31 hp@gcc.gnu.org [this message] 2003-12-21 3:23 ` [Bug libstdc++/11193] " steven at gcc dot gnu dot org 2003-12-21 9:04 ` hp at gcc dot gnu dot org 2003-12-21 9:05 ` hp at gcc dot gnu dot org 2003-12-21 9:52 ` hp at gcc dot gnu dot org 2004-01-14 4:51 ` [Bug libstdc++/11193] [3.4 Regression] The conversion to autoconf 2.5 " pinskia at gcc dot gnu dot org 2004-01-14 21:54 ` hp at bitrange dot com 2004-01-14 22:03 ` [Bug libstdc++/11193] [3.4 Regression] revision 1.126 of configure.in " pinskia at gcc dot gnu dot org 2004-02-06 3:56 ` [Bug libstdc++/11193] [3.4/3.5 " ljrittle at gcc dot gnu dot org
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=20030615053147.11193.hp@gcc.gnu.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).