From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Segher Boessenkool <segher@kernel.crashing.org>
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 17:50:56 +0100 [thread overview]
Message-ID: <7500F06B-1BD1-42E0-832B-7C5B1F14696B@Web.DE> (raw)
In-Reply-To: <20221125155607.GI25951@gate.crashing.org>
> 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:
gcc10 @10.4.0 lang/gcc10
libgcc10 @10.4.0 lang/gcc10
gcc10-libcxx @10.4.0 lang/gcc10
gcc10-bootstrap @10.3.0 lang/gcc10-bootstrap
They have dependencies:
Full Name: gcc10 @10.4.0_4+stdlib_flag
Extract Dependencies: xz
Build Dependencies: texinfo
Library Dependencies: cctools, gmp, isl, ld64, libiconv, libmpc, mpfr, zlib, zstd
Runtime Dependencies: gcc_select, libgcc10, gcc10-libcxx
--
Full Name: libgcc10 @10.4.0_4+stdlib_flag
Extract Dependencies: xz
Build Dependencies: texinfo, cctools, gmp, isl, ld64, libiconv, libmpc, mpfr, zlib, zstd
Library Dependencies:
Runtime Dependencies: libgcc11
--
Full Name: gcc10-libcxx @10.4.0_5+clang14
Extract Dependencies:
Build Dependencies: clang-14
Library Dependencies:
Runtime Dependencies:
The only port that I might be able to build is "libgcc10" which has a dependency of "libgcc11", and this a dependency to "libgcc":
Full Name: gcc11 @11.3.0_5+stdlib_flag
Extract Dependencies: xz
Build Dependencies: texinfo
Library Dependencies: cctools, gmp, isl, ld64, libiconv, libmpc, mpfr, zlib, zstd
Runtime Dependencies: gcc_select, libgcc11, gcc11-libcxx
--
Full Name: libgcc11 @11.3.0_5+stdlib_flag
Extract Dependencies: xz
Build Dependencies: texinfo, cctools, gmp, isl, ld64, libiconv, libmpc, mpfr, zlib, zstd
Library Dependencies:
Runtime Dependencies: libgcc
--
Full Name: gcc11-libcxx @11.3.0_6+clang14
Extract Dependencies:
Build Dependencies: clang-14
Library Dependencies:
Runtime Dependencies:
--
Full Name: libgcc @6.0_0
Library Dependencies: libgcc12
I do not understand this scheme, honestly! Very old software, that depends on software that will be created in some future? But – "libgcc12" is very easy to build:
Full Name: libgcc12 @12.2.0_2+stdlib_flag
Extract Dependencies: xz
Build Dependencies: texinfo, cctools, gmp, isl, ld64, libmpc, mpfr, zstd
Library Dependencies: zlib, libiconv
Runtime Dependencies:
Next month, if my internal disk will find enough empty space (remember: my PowerBook G4 is almost 20 years old, and then a 100 GB disk was no usual gadget, not even in a Mac). (It might be possible to create "private" versions on an external disk.) Before I have to find the cause why a particular port, boost, uses '-Wl,-rpath ...' which cannot work on Tiger. (It's OK with later OS versions.) It works, with other ports, when '-Wl,' is not there, because then it's a no-op or gets neglected.
Manual builds will take longer. Because they might needed patches *I* would have to provide – you've the seen the list I gave Jonathan?
--
Greetings
Pete
I wouldn't recommend sex, drugs or insanity for everyone, but they've always worked for me.
– Hunter S. Thompson
next prev parent reply other threads:[~2022-11-25 16:51 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 [this message]
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=7500F06B-1BD1-42E0-832B-7C5B1F14696B@Web.DE \
--to=peter_dyballa@web.de \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=segher@kernel.crashing.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).