Help trying to get gcc47 to run on ppc32/Tiger.
Jeremy Huddleston Sequoia
jeremyhu at macports.org
Sun Jun 24 11:41:38 PDT 2012
On Jun 23, 2012, at 3:03 PM, Daryle Walker <darylew at mac.com> wrote:
> I just wanted to update my ports, and I ended up losing both of my C++0x/11 compilers. I have the least-supported system, a 32-bit PowerPC Mac running Mac OS x 10.4.11.
> I lost gcc46, but I fixed it by following a comment. I haven't been so lucky with gcc47, and looking at ticket 34385, hope has been all but given up. On my last attempt at a fix, it seems that either I messed up copying the patch from the gcc45 attempts, or the affected file is different between gcc45 and gcc47. It doesn't help that I don't know what's wrong in the first place, nor whose end (MacPorts or GNU) does the problem lay.
> Any help on what's wrong with the patch? (Then I can try compiling.)
If I recall, the patch is actually applied already to gcc's libffi. You need to check yourself to figure out what's going wrong.
You'll probably get more support on this configuration from GCC developers directly. I suggest you file a bug report at http://gcc.gnu.org/bugzilla
> (At least we should require (Apple's?) CLang to compile GCC-4.6 when it's available, and Apple's GCC 4.2 otherwise. Never use the LLVM-GCC 4.2, and install Apple GCC 4.2 when the computer doesn't come with it. I also wrote in GCC 4.7 to use Apple's GCC 4.2 for compilation.)
That should have nothing to do with it.
> (In the worst case, since we did have earlier versions of GCC 4.7 working on my computer, is there any way I can get that old version back?)
I'd be interested to know how you got that old version to compile, given this bug. What changed to cause it to fail? My suspicion is that you have a newer cctools installed from MacPorts which is noticing this bug whereas older cctools let it slip through to become a runtime issue.
More information about the macports-dev