From: Segher Boessenkool <segher@kernel.crashing.org>
To: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: Configuring GCC 10.3 on PPC Mac OS X 10.4.11/Tiger for build reveals flaws in configure scripts
Date: Fri, 25 Nov 2022 13:43:05 -0600 [thread overview]
Message-ID: <20221125194305.GJ25951@gate.crashing.org> (raw)
In-Reply-To: <7500F06B-1BD1-42E0-832B-7C5B1F14696B@Web.DE>
On Fri, Nov 25, 2022 at 05:50:56PM +0100, Peter Dyballa wrote:
> > Am 25.11.2022 um 16:56 schrieb Segher Boessenkool <segher@kernel.crashing.org>:
> > Also, GCC 10.4 was released over a month ago, please use that?
> > Any problem in previous minor releases might already be fixed
>
> I can try. I was asked to try to build the MacPorts package, or "port", gcc10-bootstrap to help solve another problem on PPC Tiger/Mac OS X 10.4.11 I've seen that GCC 10.4 was out and I now know that MacPorts supports this version too:
Ah. I don't know what modifications they make, but our compilers should
work without any of that. You could try with what we distribute, and
get help from us ;-)
The problems you encountered with the modified source code you tried
might happen with unmodified code just the same, but it is hard to know
for sure unless you try, and support is much harder than needed with
unknown modified code :-(
Segher
next prev parent reply other threads:[~2022-11-25 19:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 10:19 Peter Dyballa
2022-11-25 11:22 ` Jonathan Wakely
2022-11-25 11:29 ` Jonathan Wakely
2022-11-25 11:39 ` Jonathan Wakely
2022-11-25 11:30 ` Peter Dyballa
2022-11-25 15:56 ` Segher Boessenkool
2022-11-25 16:50 ` Peter Dyballa
2022-11-25 19:43 ` Segher Boessenkool [this message]
2022-11-28 22:05 ` Peter Dyballa
2022-11-30 23:09 ` Peter Dyballa
2022-12-01 8:22 ` Jonathan Wakely
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=20221125194305.GJ25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=Peter_Dyballa@Web.DE \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/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).