From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Peter Dyballa <Peter_Dyballa@web.de>, 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 09:56:07 -0600 [thread overview]
Message-ID: <20221125155607.GI25951@gate.crashing.org> (raw)
In-Reply-To: <CAH6eHdSic5Z6cfhRyL5jmO2OJy8_HTGEch7h2whSFUHPkjZW8w@mail.gmail.com>
On Fri, Nov 25, 2022 at 11:22:15AM +0000, Jonathan Wakely via Gcc-help wrote:
> On Fri, 25 Nov 2022 at 10:20, Peter Dyballa via Gcc-help
> <gcc-help@gcc.gnu.org> wrote:
> > ..../gcc10-bootstrap/work/gcc-10.3.0/isl/configure: line 1: cd: /opt/local/libexec/gcc10-bootstrap: No such file or directory
> > checking for powerpc-apple-darwin8.11.0-gcc...
> >
> > checking whether we are using the GNU C compiler... (cached) yes
> > ..../gcc10-bootstrap/work/gcc-10.3.0/isl/configure: line 5363: test: =: unary operator expected
>
> isl is not part of GCC, and I don't see this error in the version of
> isl that gcc-10.3.0/contrib/download_prerequisites uses.
>
> Using isl is optional anyway, you can just leave it out if you want.
> Either way, this seems to be a problem with the version of isl that
> MacPorts uses, not a GCC problem.
Yup. Also, GCC 10.4 was released over a month ago, please use that?
Any problem in previous minor releases might already be fixed (I doubt
it in this case, but :-) )
Segher
next prev parent reply other threads:[~2022-11-25 15:57 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 [this message]
2022-11-25 16:50 ` Peter Dyballa
2022-11-25 19:43 ` Segher Boessenkool
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=20221125155607.GI25951@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).