Fwiw, libgcc15 (not libgcc-powerpc) built fine here on 10.5. gcc15 is still building currently.
Edit: gcc15 built fine as well
Great, thanks for updating. Expected, but good to have this confirmed.
Fwiw, libgcc15 (not libgcc-powerpc) built fine here on 10.5. gcc15 is still building currently.
Edit: gcc15 built fine as well
Just got linked this thread by a friend after remarking about rebuilding VLC as a G5 optimized binary.
I've got a G5 Quad (of...questionable stability, as they all are) as well as an Xserve G4 and G5. I've Potentially also access to some old Intel Mac Pros (of unknown vintage) through an an e-waste recycler. A friend also has some Intel Xserves that I may be able to borrow.
My workshop does not charge me for electricity use and I've 200 Amps at 208 volts (woo, North America) and will (eventually) have access to fiber internet.
Does the project still require some build boxes?
I would love to put something like this together for Tiger. What would I have to do?I have uploaded my custom PPCPorts install which includes approx. 1500 prebuilt ports for PPC OS X 10.5.8 Leopard (32bit only).
![]()
10.75 GB file on MEGA
mega.nz
Instructions:
Mount the custom install dmg and double click the provided install.command script - enter your user password when prompted and wait till the process is completed. (at least 20 Gigs of harddisk space are required)
If you already have MacPorts installed you might want to consider backing up the /opt directory on your boot drive before proceeding with the install.
If anyone runs into any problems you can post them here and I'll try to help.
Just got linked this thread by a friend after remarking about rebuilding VLC as a G5 optimized binary.
I actually do have my pem key and instructions attached to the third post in this thread. Adding it to the Github would be great so I don't have to keep copying and pasting it. Thank you.@thedoctor45x @Forest Expertise I suggest you guys add instructions how to use your archives and where to get pem keys. The latter can be committed to the fork of the base, if desired; if you do, please pick a distinct name (your GH handle will perhaps be convenient, but anything will do).
Then anyone can add a couple of lines into conf files, and everything gonna work normally via port install.
(And we can add this to the head post too, otherwise it gets lost in comments.)
I actually do have my pem key and instructions attached to the third post in this thread. Adding it to the Github would be great so I don't have to keep copying and pasting it. Thank you.
Well, at least X11 is working again now
I would greatly appreciate help with getting python314 working on Tiger, now that it has released. I have attached a failed build log. @barracuda156, @glebm - what should I try to get this working?
Thanks for the help. I eventually got python314 to compile with the two attached patches. Is there anything obviously problematic with the patches? If not, I will make a pull request. I am bothered by the tiger-posixmodule-patch - that code exists in python313 and to my knowledge didn't need to be patched.There is no libproc on 10.4. Whatever uses it should be conditionally excluded (see libuv port or another example, there are many of those).
Thanks for the help. I eventually got python314 to compile with the two attached patches. Is there anything obviously problematic with the patches?
If not, I will make a pull request. I am bothered by the tiger-posixmodule-patch - that code exists in python313 and to my knowledge didn't need to be patched.
In other news, I submitted my pem key in a pull request.
I also built powerpc-port-base in opt/bootstrap, and built curl there. I ran into problems trying to package curl or even rebuild my main opt/local installation
I think one file had to be copied manually because it was complaining about permissions.
Curl (and many dependencies) also built on powerpc-ports 2.11.5 (or 2.11.99 according to some of the logs).
I have uploaded my custom PPCPorts install which includes approx. 1500 prebuilt ports for PPC OS X 10.5.8 Leopard (32bit only).
I have uploaded my custom PPCPorts install which includes approx. 1500 prebuilt ports for PPC OS X 10.5.8 Leopard (32bit only).
![]()
10.75 GB file on MEGA
mega.nz
Some additional news on this. This archive is for PowerPC Leopard, and yet it will not download using Aquafox 3.0 running on PowerPC Sorbet Leopard. The source site complains that my browser is out of date
due to old libadwaita. It might be possible to get newer versions to work by reverting this commit (?).
I assume something like this should work to wrap each patch in? #if defined(MAC_OS_X_VERSION_10_4)1. Instead of throwing out libproc code, wrap it in macros, please. Otherwise it is unsafe, someone accidentally moves the patch from inside Tiger-specific block and breaks the code for later OS (and that may go unnoticed, since it still compiles).
2. Dropping static assert is not great, but I am not sure we got a better fix ready. Again, I rather see it done conditionally – it is just 2–3 extra lines.
Take a look at these, and I think there was a Trac ticket too.
![]()
Remove Tiger workarounds from my ports · macports/macports-ports@d8b38cc
The MacPorts ports tree. Contribute to macports/macports-ports development by creating an account on GitHub.github.com
May be worth checking if earlier fixes are still present, where relevant, they may not be.![]()
python313: fix build on Tiger and Leopard by glebm · Pull Request #28265 · macports/macports-ports
Description This adds the 2 patches from @kencu, originally posted in https://trac.macports.org/ticket/71206#comment:13, to fix the build on Tiger. To fix the build on Leopard, we simply add -D_DAR...github.com
Thank you, I will deal with PRs within a day.
There were some changes to port.pkg and port.mpkg after 2.11.0 release, if those do not work, then likely something is broken (it was broken deliberately in upstream, and may still be broken in PPCPorts, since 10.4 was not tested).
If the point is to get it working locally for you, then anything will do. Say, for x86 ports, which I do not distribute to anyone and use mostly for local testing, I occasionally fix dylib paths manually, which does the trick, but is non-reproducible. If you plan to distribute the base for 10.4, it should build reproducibly with no manual intervention, as long as the latter is avoidable, and in this case it is (after all, relevant code can be reverted to its earlier version).
This is good to know that not everything is totally broken LOL
(Thank you for testing, this is actually helpful.)