Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It seems all ffmpeg versions need to be rebuilt against the new x265 😕
Does adding -latomic to libraries x265 links to help in some way? I am not sure since that version of gcc it appeared and when it stopped being needed, but *I think* I run into some similar problem on Slackware i586
 
Does adding -latomic to libraries x265 links to help in some way?

That is unrelated to atomics need. (And in general libatomic does not automatically become a dependency for everything down the road.)

P. S. I don’t know why I replied about dependents LOL, but anyway, just adding `-latomic` will do nothing, since original code uses different built-ins, but it is fixed by now in PPCPorts.
 
Last edited:
How long does it take to compile gcc10-bootstrap? I've been waiting a few days on my iMac G5 running 10.5.8. Mainly looking to install bash, which requires gcc14, which requires gcc10-bootstrap.

Tried using one of my intel minis running leopard to cross-compile, but I ran into tons of errors and gave up on that front.
 
How long does it take to compile gcc10-bootstrap? I've been waiting a few days on my iMac G5 running 10.5.8. Mainly looking to install bash, which requires gcc14, which requires gcc10-bootstrap.

Tried using one of my intel minis running leopard to cross-compile, but I ran into tons of errors and gave up on that front.
for me on previous config (2.0 Ghz dual core G5, 2 GB ram, 160 Gb sata mechanical drive gcc10-bootstrap finished in like 10 hours, libgcc14 on the other hoof .. not finished in 30 hours (with some breaks for manual installation of other stuff).

So I guess "more than 30 hours" for whole modern gcc toolchain. Not sure how much, I just installed binary
 
How long does it take to compile gcc10-bootstrap?

On 10.6 it builds for a single arch, so about 3 hrs (I think) on the Quad. On 10.5 it builds as universal by default, so it will take twice as long, at least.
You can install pre-built package if you set universal_archs to ppc ppc64 (in MacPorts config or on command line).

I've been waiting a few days on my iMac G5 running 10.5.8. Mainly looking to install bash, which requires gcc14, which requires gcc10-bootstrap.

Have you considered building for ppc64? It does have some drawbacks (in a sense of some ports not building), but those are unlikely to matter in general case.

Tried using one of my intel minis running leopard to cross-compile, but I ran into tons of errors and gave up on that front.

Provisionally you could build it as i386+ppc on 10.5 with Rosetta, but it will require some tweaks to the portfile. Adding 64-bit into the mix is likely to break the build.
 
me: sudo port install pngquant
ppcports: fetching rust

I knew about this, no problem, just .. well, lets hope THIS TIME nothing suddenly breaks electricity flow here for all time it will take to compile THIS
 
me: sudo port install pngquant
ppcports: fetching rust

If this is on 10.5, it will not work. Most likely it won’t work on 10.6 either, but for a different reason (mrustc builds and works, but it does not support the whole of rust syntax, by design).

I should probably prohibit installing mrustc on < 10.6 so that people don’t waste time.
 
Does "gitk" work currently? For me attempt at running it result in wish error msg:

"Expected version number but got 8.6-"

also gtk4 demo does not seem to work - demand too new gl by default ? So, pulseaudio gui control also not working.
 
Have you tried setting GSK_RENDERER=cairo env variable?
yes! with this variable set gtk4 demo and pulseaudio volume control GUI works!

For now I surely will put this one in my .profile, but may be port itself can alter gtk4 on ppc macs so this will be working default?
 
Does "gitk" work currently? For me attempt at running it result in wish error msg:

"Expected version number but got 8.6-"

also gtk4 demo does not seem to work - demand too new gl by default ? So, pulseaudio gui control also not working.

GL in gtk4 is broken (not only on powerpc).

But AFAIK there are no ports using it. `celluloid` would, in latest versions, but I do not upgrade it for the reason that it does not work then.

Otherwise gtk4 works. Gnome stuff may need dbus session running. If something fails, it is either cairo not set or dbus not running.
 
PLEASE DO NOT UPGRADE ANYTHING GCC-RELATED RIGHT NOW (unless you feel very adventurous).

There is a bug in gcc16 which has to be addressed, otherwise some ports will be broken.


The issue in question has provisionally been fixed.

P. S. There is a minor different issue that breaks jemalloc. Impact should be minimal. jemalloc was never properly supported on 10.5 and in most cases is used inside variants. Not a stopper, IMO. I am using gcc16 now myself for everything.
 
Last edited:
Update on the gcc matter:

1. The issue is related to a specific case of TLS implementation and is not exclusive to powerpc but apparently affects macOS < 10.11.
2. There is no fix for it right now, but it is expected, so for the moment I am not gonna revert the changes. (There is no reason to go back to gcc14: in the worst case a build of gcc16 with `--disable-tls` will work fine, which is what gcc14 was doing anyway.)
3. If you build gcc16 now, you will need to rebuild it again soon. So unless on a fast hardware, perhaps refrain from updating until the issue is fixed.
4. Once gcc/libgcc are updated, some ports will be broken. Extent is unknown but looks like only C++ ports that use TLS are affected. I have pushed temporary fixes to a few which I discovered, so that the set-up is working.
 
Update on the gcc matter:

1. The issue is related to a specific case of TLS implementation and is not exclusive to powerpc but apparently affects macOS < 10.11.
2. There is no fix for it right now, but it is expected, so for the moment I am not gonna revert the changes. (There is no reason to go back to gcc14: in the worst case a build of gcc16 with `--disable-tls` will work fine, which is what gcc14 was doing anyway.)
3. If you build gcc16 now, you will need to rebuild it again soon. So unless on a fast hardware, perhaps refrain from updating until the issue is fixed.
4. Once gcc/libgcc are updated, some ports will be broken. Extent is unknown but looks like only C++ ports that use TLS are affected. I have pushed temporary fixes to a few which I discovered, so that the set-up is working.

Should be good now. That issue is fixed, ICU switched back to a normal build with the main compiler.
 
installed the newest version of PPCPorts, updated with sync and tried to build libgcc. But it failed. I'm on a PowerBook A1138.

What system, what failure specifically? Did you deactivate ports before building? (That’s needed when updating libgcc/gcc.)
 
What system, what failure specifically? Did you deactivate ports before building? (That’s needed when updating libgcc/gcc.)


I'm on 10.6.8, A5 image as always. i didn#t deactivate the ports befoe upgrading. i DID see your recommendation in the other thread, where you recommended deactivating ports before upgrading, but i thought it was concerning ONLY 10.5. Eror seems to be related to unwind. i hope i can upload the log file, cause InterWebPPC doesn't work anymore with uploading files.
 

Attachments

  • Like
Reactions: Forest Expertise
I'm on 10.6.8, A5 image as always. i didn#t deactivate the ports befoe upgrading. i DID see your recommendation in the other thread, where you recommended deactivating ports before upgrading, but i thought it was concerning ONLY 10.5. Eror seems to be related to unwind. i hope i can upload the log file, cause InterWebPPC doesn't work anymore with uploading files.

This looks like this https://github.com/iains/gcc-15-branch/issues/3 but I have no idea why it happens on some set-ups. Never got it myself so far.

@saxfun For the record, is this on a G4 or G5?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.