glib2 @ 2.34.3 Build failure on powerpc ppc64

[calderon.christian760@…]

Glib2 failed to build on my PowerMac G5 running OS X 10.5.8. I have Macports set up to compile ports as ppc64 by default, idk if that is the issue. Also, I noticed that the compiler being used is gcc-4.0 which I've had problems with before (although I don't know if that is the cause of the problem) and not gcc-4.2.

Is this a problem caused by me trying to compile for ppc64, or is it a problem with using gcc-4.0, or something else? I have attached the log file.

[calderon.christian760@…]

log file

[ryandesign (Ryan Carsten Schmidt)]

Replying to calderon.christian760@…:

Glib2 failed to build on my PowerMac G5 running OS X 10.5.8. I have Macports set up to compile ports as ppc64 by default, idk if that is the issue.

Yes, that is the issue. Here is the upstream bug report: ​https://bugzilla.gnome.org/show_bug.cgi?id=647145

ppc64 is never the default in MacPorts, so it's not well-tested. It also doesn't really offer any advantage over ppc, unless you need to use more than 4GB of data in a single program. (In contrast, on Intel, using x86_64 offers many benefits over i386 other than just the larger address space.)

Also, I noticed that the compiler being used is gcc-4.0 which I've had problems with before (although I don't know if that is the cause of the problem) and not gcc-4.2.

gcc-4.0 is the default compiler on Tiger and Leopard so it should generally work fine, but you're right that gcc-4.2 is also available, and in some ports we do switch to that compiler on Leopard. The upstream bug report hints that a different gcc version might work better, so feel free to try compiling glib2 for ppc64 using gcc-4.2. Here's how you would do that:

sudo port clean glib2
sudo port install glib2 configure.compiler=gcc-4.2

If that works, I'll be happy to change the port to use that on Leopard. I cannot test it myself because my PowerPC Macs have G3 and G4 processors, not G5s.

[ryandesign (Ryan Carsten Schmidt)]

Duplicate of #29026 which was fixed.