I don't know how I missed this the first few times I checked the thread but this repo saved my poor A1139 from another 3 days gcc compile and that's pretty neat.
I apparently also clicked the heart on this???
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
PPCPorts: the only ports you ever need on a PowerPC
- Thread starter barracuda156
- Start date
- Sort by reaction score
I apparently also clicked the heart on this???
I mean if you have a Quad (and you do) (and I do) the compile time isn't nearly as painful. But my Quad is out of service until the winter months, so my HR 17 will have to do, and having the binaries helps a lot.
What’s up with yours btw? Or just saving it from heat? Mine was dying for a few days, but at the moment is usable again (no idea when the issue strikes again), which is rather helpful: after updating x264 I need to rebuild ffmpeg 7 times LOL (4 through 8, plus G5 variants for two of them). Update. Oh wait, in fact at least two of them also need to have +x11 variant built…
Power consumption and electricity costs. I can't justify running it in the same season and at the same time as my (already struggling) air conditioner.
There are some updates and fixes, consider running `port sync`.
Also a few new ports added.
P. S. As usual, commit history is available here: https://github.com/macos-powerpc/powerpc-ports/commits/main
Also a few new ports added.
P. S. As usual, commit history is available here: https://github.com/macos-powerpc/powerpc-ports/commits/main
Perhaps a dumb question, but I cannot seem to find the answer by searching.
Is there anything in the PPCPorts world that would allow a fully functioning connection to Dropbox or OneDrive (i.e. automatically uploads files to Dropbox/OneDrive as they change... Just like the current versions do)?
Thanks!
Is there anything in the PPCPorts world that would allow a fully functioning connection to Dropbox or OneDrive (i.e. automatically uploads files to Dropbox/OneDrive as they change... Just like the current versions do)?
Thanks!
Possibly fileferry. Otherwise you may need to look for some open-source software in supported languages (no rust, no go, no typescript or alike), verify it works on a modern macOS, and then we can try making it work on powerpc.
@mac57mac57 Generally speaking, I think the problem will be that file-level events are not supported prior to 10.7. So automatic detection of changes may be an issue. maestral, for example, relies on watchdog, which uses fsevents, I think.
That sucks. Hopefully it is fixable.
I have been playing with Komikku, a very nice manga reader for GNOME.
View attachment 2542346
After commenting out all the webkit/webview stuff and disabling the (many) sources that needed it, it works pretty well. WebP is broken though (in GTK?), I don't know why.
This is an older version because I could not get newer versions to work due to old libadwaita. It might be possible to get newer versions to work by reverting this commit (?). It depends on some Python modules that are not in MacPorts so I installed those locally with pip.
1.88 is also broken by this now.
P. S. We are literally living in a meme:
Well @Doq, I suspect you may be being a wee bit over cautious here.
A fully loaded G5 Quad could conceivable draw up to 500W continuously if it is doing something strenuous, like PPCPorts builds. That equates to around 4 Amps of electricity at the 120v household circuit it plugs into. Now that average household circuit can provide up to about 12 Amps, which other household appliances may already draw - for example, your coffee pot may draw that much when you first start it up and it is quickly heating the water.
Your Air Conditioner, on the other, draws between 2,000W and 3,000W continuously while it is running. That equates to around 8 to 12 Amps at the 240v circuit they are usually powered by.
So, 500W vs. 3,000W... That is nearly an order of magnitude difference. I would argue that the impact of that extra 500W on your power bill would be fairly low. Mathematically, it would be only a 17% increase. If your monthly power bill (with air conditioner running) was, say, $350, with the G5 Quad running full tilt for the same billing period, that bill would only increase by $60... and that is only if the G5 Quad ran at 100% capacity for 100% of that time. Neither of those conditions would apply to real world use of the G5 Quad, even for builds however, so I would guess that theoretical $60 is more like $30 - $40.
So... Perhaps you could bring your G5 Quad out of its summer hibernation and put it back to work? The cost is low (ish), and a Quad is THE way to get this stuff done!
p.s.> All of the above assumes a typical household central air set up. If you are working with window or room air conditioners, then "all bets are off"; I would see your point entirely!
Yes, it is for this reason that I have very strict times on when my aircon is allowed to run, regardless of actual room temperature or weather conditions.
My power bill as it is is about $75/mo during the summer months where the aircon runs. This hypothetical $60 increase would kill my financials instantly, and that's before having to also dissipate the extra heat it gives off, which my aircon cannot.
This is the case; I have a single window aircon that does the entirety of the cooling-- I live in a studio so while it's not quite adequate (it's a little bit underpowered), it's enough to manage.
Believe me, I might actually not be cautious enough. I saw triple digits one time and I was immediately over it.
@Doq, my apologies... I may have unintentionally offended you. I had no such intention.
I live in the American south, where the mercury pushes 100 F for months at a time in the summer months. My expectations of A/C requirements and the associated billing are clearly different than your reality.
Please accept my apologies. You have been nothing but incredibly helpful to me - I had, and have, absolutely no intention to offend you. Thank you for all the help you have provided to me and to countless others here on these forums.
Cheers,
Michael
I live in the American south, where the mercury pushes 100 F for months at a time in the summer months. My expectations of A/C requirements and the associated billing are clearly different than your reality.
Please accept my apologies. You have been nothing but incredibly helpful to me - I had, and have, absolutely no intention to offend you. Thank you for all the help you have provided to me and to countless others here on these forums.
Cheers,
Michael
Last edited:
The last release for Tiger still works. https://github.com/macports/macports-base/releases/download/v2.10.7/MacPorts-2.10.7-10.4-Tiger.dmg
Just make sure to do "sudo port sync" instead of "sudo port selfupdate" because the client can't update anymore and it'll print a cryptic error.
It is generally a good idea to avoid routines which do a lot of dissimilar operations at once without any control over that. IMO, selfupdate should never be used, and certainly so on legacy systems. It can also break things on modern macOS.
Updating ports and updating the base can and should be performed separately.
Some updates today: a few editors, musikcube, fastfetch, btop, a fix for tiff.
This is a huge disappointment, especially because we just got QMPlay2 working pretty well.
There are some chances it will be fixed, if yt-dlp adds support for QuickJS backend. See discussion: https://github.com/bellard/quickjs/issues/445
Unfortunately, libgcc15 fails to build (log attached). My understanding is gcc upstream supports PowerPC Darwin. Should I report the build failure to them, or is it something that there is a clear fix for?
The last version of gcc15 I built was 15-20250323 snapshot: https://github.com/macos-powerpc/po...2d908222c54218f/lang/gcc-powerpc/Portfile#L42
There were no failures (on 10.6 at least).
Quick googling led to related stuff introduced in Sep 2024: https://gcc.gnu.org/pipermail/gcc-cvs/2024-September/409550.html
So probably it should not be broken, unless something changed since March in this regard. However, I never built any recent gcc version on 10.4.
You can report gcc bugs here: https://gcc.gnu.org/bugzilla/
(If you do, add iains and me into CC field.)
But perhaps start from an issue here: https://github.com/iains/gcc-15-branch/issues
Likely Iain gonna know how to fix that.
I filed an issue on the Github. Thank you for your helpful directions, as always.
I will also email about trying to get a Bugzilla account if I don't hear from Iain.
Python ports-related announcement
Since MacPorts keeps multiple Python versions and Python ports get updated “every third day” (both in a sense of upstreams being very active and MacPorts folks having more interest to keep those ports updated), it takes a lot of time to compile those, while there is not much point in that. Up till now I tried to have at least stuff like `mypy` and `scipy` compiled for python 3.10 through 3.13, but with the Quad being kinda dead and another PowerMac located at a place where I have to pay for electricity, it becomes both strainful in terms of the only usable machine being busy for hours and simply expensive.
I will keep verifying that builds work for at least one of the later python versions (3.12 or 3.13, at the moment), so pre-built packages are likely to be available for those. There will be no regular (or at all) builds for anything older, unless there is some port in my PPCPorts strictly requiring an older python package.
From what I can tell, normally python 3.11+ use the same versions, so usually if you see a package built for 3.12/3.13, the same portfile should work for 3.11. Earlier versions may or may not build.
This is to say that if for some reason you need some python package for < 3.12 and it is either broken or takes forever to build on your hardware, raise the issue explicitly. Otherwise use the latest python version available for a given port (it is normally 3.12 or 3.13 now).
Since MacPorts keeps multiple Python versions and Python ports get updated “every third day” (both in a sense of upstreams being very active and MacPorts folks having more interest to keep those ports updated), it takes a lot of time to compile those, while there is not much point in that. Up till now I tried to have at least stuff like `mypy` and `scipy` compiled for python 3.10 through 3.13, but with the Quad being kinda dead and another PowerMac located at a place where I have to pay for electricity, it becomes both strainful in terms of the only usable machine being busy for hours and simply expensive.
I will keep verifying that builds work for at least one of the later python versions (3.12 or 3.13, at the moment), so pre-built packages are likely to be available for those. There will be no regular (or at all) builds for anything older, unless there is some port in my PPCPorts strictly requiring an older python package.
From what I can tell, normally python 3.11+ use the same versions, so usually if you see a package built for 3.12/3.13, the same portfile should work for 3.11. Earlier versions may or may not build.
This is to say that if for some reason you need some python package for < 3.12 and it is either broken or takes forever to build on your hardware, raise the issue explicitly. Otherwise use the latest python version available for a given port (it is normally 3.12 or 3.13 now).
Fwiw, libgcc15 (not libgcc-powerpc) built fine here on 10.5. gcc15 is still building currently.
Edit: gcc15 built fine as well
Edit: gcc15 built fine as well
Last edited: