public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jeff Sturm <jsturm@one-point.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: bootstrap/3373 Date: Tue, 26 Jun 2001 05:36:00 -0000 [thread overview] Message-ID: <20010626123601.20860.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR bootstrap/3373; it has been noted by GNATS. From: Jeff Sturm <jsturm@one-point.com> To: Hans Werner Strube <strube@physik3.gwdg.de> Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: bootstrap/3373 Date: Tue, 26 Jun 2001 09:07:04 -0400 (EDT) On Tue, 26 Jun 2001, Hans Werner Strube wrote: > This is not the same as the case I reported. When building gcc (3.0), g++ > g77, libstdc++ etc., gcc has no difficulties to find GNU as and ld, which were > installed previously in the gcc 2.95.3 tree and the pertinent directory is > automatically placed in the -B options by configure. Merely the definition of > GCJ in the libjava Makefile does not include the -B option pointing to GNU > as and ld. Although this behavior is at odds with the FAQ, I think there is a good point here... why is FLAGS_FOR_TARGET used for c/c++/chill but not gcj in the toplevel configure.in? Is this an oversight, or is -B$(build_tooldir)/bin not really needed? For reference, here's the original thread on -B$(build_tooldir)/bin: http://gcc.gnu.org/ml/gcc-patches/1998-10/msg00435.html Jeff
next reply other threads:[~2001-06-26 5:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-26 5:36 Jeff Sturm [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-26 1:26 bootstrap/3373 Hans Werner Strube
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=20010626123601.20860.qmail@sourceware.cygnus.com \ --to=jsturm@one-point.com \ --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).