public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/27063] Fail to build gcc-core-4.2 snapshots Date: Thu, 15 Jun 2006 06:33:00 -0000 [thread overview] Message-ID: <20060615063313.9896.qmail@sourceware.org> (raw) In-Reply-To: <bug-27063-9369@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from bonzini at gnu dot org 2006-06-15 06:33 ------- I agree it is a packaging issue, but we can work around it and it can be useful for other front ends as well. Taking the bug. -- bonzini at gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |bonzini at gnu dot org |dot org | Status|NEW |ASSIGNED Last reconfirmed|2006-04-13 01:44:51 |2006-06-15 06:33:13 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27063
next prev parent reply other threads:[~2006-06-15 6:33 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-04-06 16:42 [Bug bootstrap/27063] New: " sebastian dot pop at cri dot ensmp dot fr 2006-04-06 16:46 ` [Bug other/27063] " pinskia at gcc dot gnu dot org 2006-04-13 1:44 ` pinskia at gcc dot gnu dot org 2006-06-15 6:33 ` bonzini at gnu dot org [this message] 2006-06-15 6:39 ` bonzini at gnu dot org 2006-07-03 7:58 ` bonzini at gcc dot gnu dot org 2006-07-03 7:58 ` bonzini at 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=20060615063313.9896.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).