public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/43301] top-level configure script ignores ---with-build-time-tools
Date: Thu, 04 Aug 2022 02:20:22 +0000 [thread overview]
Message-ID: <bug-43301-4-25H6UN7s9l@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43301-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43301
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aoliva at gcc dot gnu.org
--- Comment #7 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #6)
> JFTR, I had cause to use this today on powerpc-darwin9, and it seemed to
> DTRT - so it would be useful to establish what it was that did not work
> before, that was fixed by the patch.
>
> /src-local/gcc-git-11/configure
> --prefix=/opt/iains/powerpc-apple-darwin9/gcc-11-3Dr2d
> --build=powerpc-apple-darwin9 --enable-languages=all --with-tune-cpu=G5
> --enable-libphobos --with-libphobos-druntime-only
> CC=powerpc-apple-darwin-gcc CXX=powerpc-apple-darwin-g++
> --with-build-time-tools=/opt/iains/powerpc-apple-darwin9/gcc-11-3Dr2d/bin
>
> Without the
> "--with-build-time-tools=/opt/iains/powerpc-apple-darwin9/gcc-11-3Dr2d/bin"
> the system linker and assembler are found and used (which fails to work with
> D, causing a bootstrap fail) with the option, the relevant tools are found
> and bootstrap succeeded....
>
> (so I am not sure what the original problem was
> since $build is not specified in the summary, I guess we must assume it was
> i686-pc-cygwin so perhaps the problem is specific to that setup?)
Alexandre Oliva's assessment is that the issue was just one having an old build
left over, and that all the patch did was to force a rebuild:
https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599169.html
(so we might be going with his patch instead)
next prev parent reply other threads:[~2022-08-04 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43301-4@http.gcc.gnu.org/bugzilla/>
2022-05-24 15:04 ` egallager at gcc dot gnu.org
2022-07-31 20:58 ` egallager at gcc dot gnu.org
2022-08-02 23:05 ` iains at gcc dot gnu.org
2022-08-04 2:20 ` egallager at gcc dot gnu.org [this message]
2022-12-02 6:27 ` egallager at gcc dot gnu.org
2010-03-09 1:00 [Bug bootstrap/43301] New: " scovich at gmail dot com
2010-03-09 1:04 ` [Bug bootstrap/43301] " scovich at gmail dot com
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=bug-43301-4-25H6UN7s9l@http.gcc.gnu.org/bugzilla/ \
--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: link
Be 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).