public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/6590: gcc emits code that gas doesn't understand Date: Fri, 10 May 2002 03:56:00 -0000 [thread overview] Message-ID: <20020510105604.14881.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/6590; it has been noted by GNATS. From: Bruno Haible <bruno@clisp.org> To: Richard Henderson <rth@redhat.com> Cc: gcc-gnats@gcc.gnu.org Subject: Re: bootstrap/6590: gcc emits code that gas doesn't understand Date: Fri, 10 May 2002 12:52:50 +0200 (CEST) Richard Henderson writes: > You _really_ need to have binutils installed at the same > prefix as gcc. This ought to be documented. I would have expected to find this information in INSTALL/configure.html. Bruno
next reply other threads:[~2002-05-10 10:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-10 3:56 Bruno Haible [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-13 10:26 Gerald Pfeifer 2002-05-08 15:06 Richard Henderson 2002-05-07 6:26 Bruno Haible
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=20020510105604.14881.qmail@sources.redhat.com \ --to=bruno@clisp.org \ --cc=gcc-prs@gcc.gnu.org \ --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).