public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc-bug at bullseye dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/12098] error: invalid switch '-x' Date: Tue, 02 Sep 2003 15:23:00 -0000 [thread overview] Message-ID: <20030902152314.16719.qmail@sources.redhat.com> (raw) In-Reply-To: <20030828233055.12098.gcc-bug@bullseye.com> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12098 gcc-bug at bullseye dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW Ever Confirmed| |1 ------- Additional Comments From gcc-bug at bullseye dot com 2003-09-02 15:23 ------- The configure script ought not allow building GCC if the assembler is no good. It should stop with an error stating the requirement for GNU as.
next prev parent reply other threads:[~2003-09-02 15:23 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-08-28 23:30 [Bug bootstrap/12098] New: " gcc-bug at bullseye dot com 2003-08-29 17:19 ` [Bug bootstrap/12098] " pinskia at gcc dot gnu dot org 2003-08-30 15:01 ` pinskia at gcc dot gnu dot org 2003-09-02 15:23 ` gcc-bug at bullseye dot com [this message] 2003-11-08 21:26 ` [Bug bootstrap/12098] gcc build fails without gas on ia64-hpux: " dhazeghi at yahoo dot com 2004-02-08 3:30 ` pinskia at gcc dot gnu dot org 2004-02-08 4:32 ` zack 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=20030902152314.16719.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).