I tried using MacPorts on a Leopard 10.5.8 Intel VM to install gcc15 but it failed atlibomp.
I am afraid no one tests 10.5 Intel builds at all. Why `libomp` is pulled in? In any case, I can only recommend switching the installation to `libstdc++` (which was Apple original set-up). Unfortunately, getting rid of clangs is non-trivial: some ports unconditionally try using unsupported by GNU `as` SIMD (libyuv, libsodium, aom), and upstreams think it is a user problem (implementing a proper test is an extra work for them). But with `libc++` you will have to deal with the whole zoo of untested clangs. Hard to estimate which is more painful eventually.
So now I'm trying PPCPorts on Leopard 10.5.8 Quad G5.
The instructions at https://macos-powerpc.org don't say what to do after step 3.
I tried this:
Code:JoeG5:~ joevt$ sudo port list Warning: Can't open index file for source: rsync://macos-powerpc.org/macos-powerpc/PPCPorts/powerpc-ports.tar Warning: Can't open index file for source: rsync://rsync.macports.org/macports/release/tarballs/ports.tar.gz Error: listing all ports failed: No index(es) found! Have you synced your port definitions? Try running 'port selfupdate'.
Run `sudo port -v sync`, as with MacPorts. Alternatively, `sudo portindex ${dir_with_ports}` also works, the first is easier.
So then I tried this:
Code:JoeG5:~ joevt$ sudo port selfupdate ---> Checking for newer releases of MacPorts MacPorts base version 2.12.1 installed, MacPorts base version 2.12.1 available. ---> MacPorts base is already the latest version ---> Updating the ports tree The ports tree has been updated. All installed ports are up to date.
So now I can do this:
Code:JoeG5:~ joevt$ sudo port install gcc15 Warning: archive_sites.conf: no urls set for macports_archives ---> Computing dependencies for gcc15 The following dependencies will be installed: autoconf ... zstd Continue? [Y/n]: Y ---> Fetching archive for gcc_select ---> Installing gcc_select @0.1_10 ---> Activating gcc_select @0.1_10 ---> Cleaning gcc_select ---> Fetching archive for gcc10-bootstrap ---> Archive not available for gcc10-bootstrap, building locally ---> Fetching distfiles for gcc10-bootstrap Attempting to fetch http://distfiles.macports.org/gcc/gcc-10.5.0.tar.gz ---> Verifying checksums for gcc10-bootstrap ---> Extracting gcc10-bootstrap
I will leave it running overnight.
Notice, at the moment the primary compiler is gcc14. Do you have any special reason to use gcc15 now?
So far I have not come across such a need with regard to ports we have. I am planning to skip gcc15 and update the main compiler to gcc16 once it is released.