public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/15065] [4.3/4.4/4.5 Regression] bootstrap fails during bulding libstdc++-v3 on Tru64 V5.0 Date: Tue, 31 Mar 2009 16:17:00 -0000 [thread overview] Message-ID: <20090331161706.22028.qmail@sourceware.org> (raw) In-Reply-To: <bug-15065-641@http.gcc.gnu.org/bugzilla/> ------- Comment #18 from jsm28 at gcc dot gnu dot org 2009-03-31 16:17 ------- Closing 4.2 branch. -- jsm28 at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[4.2/4.3/4.4/4.5 Regression]|[4.3/4.4/4.5 Regression] |bootstrap fails during |bootstrap fails during |bulding libstdc++-v3 on |bulding libstdc++-v3 on |Tru64 V5.0 |Tru64 V5.0 Target Milestone|4.2.5 |4.3.4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15065
next prev parent reply other threads:[~2009-03-31 16:17 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-15065-641@http.gcc.gnu.org/bugzilla/> 2005-10-30 22:10 ` [Bug target/15065] [3.4/4.0/4.1 " pinskia at gcc dot gnu dot org 2005-10-31 0:09 ` pinskia at gcc dot gnu dot org 2006-02-28 20:49 ` [Bug target/15065] [3.4/4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org 2006-05-25 2:42 ` [Bug target/15065] [4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org 2007-02-14 9:29 ` [Bug target/15065] [4.0/4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org 2008-07-04 16:31 ` [Bug target/15065] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2008-08-25 8:09 ` htl10 at users dot sourceforge dot net 2009-03-31 16:17 ` jsm28 at gcc dot gnu dot org [this message] 2009-08-04 12:27 ` [Bug target/15065] [4.3/4.4/4.5 " rguenth at gcc dot gnu dot org 2010-05-22 18:11 ` [Bug target/15065] [4.3/4.4/4.5/4.6 " rguenth 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=20090331161706.22028.qmail@sourceware.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).