public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou@gcc.gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/8686] [sparc-solaris]3.2.1 multilib bootstrap fails: 32-bit Solaris 9 + Sun patch 112963-01 Date: Mon, 09 Jun 2003 15:07:00 -0000 [thread overview] Message-ID: <20030609150752.9511.qmail@sources.redhat.com> (raw) In-Reply-To: <20021122223600.8686.eggert@gnu.org> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8686 ebotcazou@gcc.gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |SUSPENDED ------- Additional Comments From ebotcazou@gcc.gnu.org 2003-06-09 15:07 ------- Not a bug according to the documentation. Suspended since it would become a bug if we changed our position regarding the mandatory use of --disable-multilib on 32-bit kernels.
prev parent reply other threads:[~2003-06-09 15:07 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20021122223600.8686.eggert@gnu.org> 2003-06-02 4:48 ` dhazeghi@yahoo.com 2003-06-02 9:17 ` ebotcazou@gcc.gnu.org 2003-06-02 20:01 ` eggert@cs.ucla.edu 2003-06-02 21:47 ` ro@techfak.uni-bielefeld.de 2003-06-09 15:07 ` ebotcazou@gcc.gnu.org [this message]
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=20030609150752.9511.qmail@sources.redhat.com \ --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).