public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ebotcazou@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, niki.waibel@gmx.net, nobody@gcc.gnu.org Subject: Re: bootstrap/6969: [sparc-solaris2.8] can't build gcc-3.1 with binutils-2.12.1: configure-target-libiberty decides newly built compiler 'doesn't work' Date: Tue, 11 Mar 2003 16:51:00 -0000 [thread overview] Message-ID: <20030311165149.16078.qmail@sources.redhat.com> (raw) Synopsis: [sparc-solaris2.8] can't build gcc-3.1 with binutils-2.12.1: configure-target-libiberty decides newly built compiler 'doesn't work' State-Changed-From-To: open->feedback State-Changed-By: ebotcazou State-Changed-When: Tue Mar 11 16:51:49 2003 State-Changed-Why: Could you try to pass --disable-multilib to the configure script? http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6969
next reply other threads:[~2003-03-11 16:51 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-11 16:51 ebotcazou [this message] 2003-03-12 14:28 ebotcazou
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=20030311165149.16078.qmail@sources.redhat.com \ --to=ebotcazou@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=niki.waibel@gmx.net \ --cc=nobody@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).