He seems to be inactive there for quite a while, but I dropped him a message now.
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.
Snow Leopard on Unsupported PowerPC Macs
- Thread starter Larsvonhier
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
He seems to be inactive there for quite a while, but I dropped him a message now.
I have found what was the issue: you need to temporarily change the default linker. Compilation runs now, so I cannot yet guarantee it works through completion, but at least it went far beyond its failure points.
Details of the linker problem here: https://github.com/classilla/tenfourfox/issues/498
There is also another problem when using gcc4.8 and gcc6, but gcc7 is reported to be free from it, so I try using it at the moment.
P. S. Maybe worth adding this to Wiki post? This issue is completely unobvious and is not mentioned in the tutorial.
For anyone interested, I have uploaded Fidelia: https://macintoshgarden.org/apps/fidelia
It’s a music player, very nice one.
I dunno if the developer can still offer licenses for this ancient version, but it should run in free mode.
It’s a music player, very nice one.
I dunno if the developer can still offer licenses for this ancient version, but it should run in free mode.
It might be better to post this find over on the TFF development wiki.
Btw, regarding existed builds on 10.6, take a look at this: https://opensource.apple.com/source/dyld/dyld-239.3/doc/ReleaseNotes.txt.auto.html
Notice this:
dyld-200
<rdar://problem/8942979> update_dyld_shared_cache should accept an 'overlay' along with a 'root' directory option
Remove PowerPC support
ReleaseNotes.txt
opensource.apple.com
Lion 10.7 corresponds to dyld-195.3.
So support for PowerPC at least for some components remained through 10.7 (!).
I’m still working on building dyld but it needs further dependencies and headers than i haven’t compiled thus far.
There are some interesting looking internal build numbers there that i would be very keen to have access to.
I’ll have to add those builds as “internal-only” to the wikipost at some point. I am still impressed to see that.
By the way, has anyone installed available 10.6 builds on an Intel Mac? Could be useful to pull universal components out of those and maybe for cross-compiling something.
I have re-installed 10A190 on a second volume, installed 10A190 Xcode (only Essentials) and then installed 10A222 Xcode with System and Unix Dev Tools.
GCC works, however I had to replace ld in two places, since ld from 10A222 is Intel-only, and gnumake in usr/bin, for the same reason, with versions from 10A190. Without replacing ld configure fails, without replacing gnumake make fails.
At this point I was able to build and install Macports from source, so assume all is good.
P. S. Could you specify what did you do in particular, if you remember?
Update on Apple GCC:
1. You do not need initial installation of Xcode 10A190, as long as you have ld and gnumake from it. Installing Xcode from 10A222 directly and replacing these two files in usr/bin works. (Other instance of ld is a symlink pointing to usr/bin, so it does not need replacement.)
(So far I can say that compiler works – I have not yet tested Xcode itself. If you care about Xcode, perhaps install Xcode 10A190 without Development Tools first and then install Xcode 10A222 into another directory, but with all Development Tools.)
2. I briefly tried doing the same with Xcode 10A286, and it did not work. GCC is still recognized, but compiling with it fails. This may not mean it is impossible, but probably requires more tweaks. I don′t see much point pursuing that too far though, since anyway building newer GCC is more or less required.
3. As of now, any attempts to build for ppc64 on 10.6 PPC fail. I have found a way to force Macports pass -arch ppc64 to compiler, but compilation fails. The same compiler builds the same port successfully for ppc. At the same time on 10.5.8 PPC building for ppc64 works easily (in a sense it is easy to set up; not all ports build as universal however).
1. You do not need initial installation of Xcode 10A190, as long as you have ld and gnumake from it. Installing Xcode from 10A222 directly and replacing these two files in usr/bin works. (Other instance of ld is a symlink pointing to usr/bin, so it does not need replacement.)
(So far I can say that compiler works – I have not yet tested Xcode itself. If you care about Xcode, perhaps install Xcode 10A190 without Development Tools first and then install Xcode 10A222 into another directory, but with all Development Tools.)
2. I briefly tried doing the same with Xcode 10A286, and it did not work. GCC is still recognized, but compiling with it fails. This may not mean it is impossible, but probably requires more tweaks. I don′t see much point pursuing that too far though, since anyway building newer GCC is more or less required.
3. As of now, any attempts to build for ppc64 on 10.6 PPC fail. I have found a way to force Macports pass -arch ppc64 to compiler, but compilation fails. The same compiler builds the same port successfully for ppc. At the same time on 10.5.8 PPC building for ppc64 works easily (in a sense it is easy to set up; not all ports build as universal however).
Quick update on Xcode 3.2 Pre-release v. 1544 (from 10A222):
Apparently it works normally after replacing ld in /Developer/usr/bin (provided it is installed in default location).
At least I pulled an R GUI project into this volume together with R.framework, and the build by Xcode reports as successful.
In any case you will require ld and gnumake from Xcode 10A190 to make Xcode 10A222 and its compilers usable.
These files must be replaced with respective ones from 10A190:
P. S. If anyone has any success with later versions of Xcode, please update me.
Apparently it works normally after replacing ld in /Developer/usr/bin (provided it is installed in default location).
At least I pulled an R GUI project into this volume together with R.framework, and the build by Xcode reports as successful.
In any case you will require ld and gnumake from Xcode 10A190 to make Xcode 10A222 and its compilers usable.
These files must be replaced with respective ones from 10A190:
Code:
/usr/bin/gnumake
/usr/bin/ld
/Developer/usr/bin/gnumake
/Developer/usr/bin/ldP. S. If anyone has any success with later versions of Xcode, please update me.
I was planning on doing this but ironically some of the builds don’t support the 2008 MacBook - I haven’t tried them yet just going off memory of the seed notes. Will certainly look at this again at some point.
From what i recall i just manually installed the compiler packages using pacifist.
Do we have a list of supported Intel Macs? (I guess no, but who knows.) I am thinking of getting an old Intel MacMini or even Mac Pro for that purpose. Unfortunately installing 10.6.8 on my MacMini 2012 is nowhere trivial if at all possible (anyone knowing a sure working method, please let me know!).
Pacifist doesn’t seem to work properly on 10A190 for me. But in fact you don’t need it, all packages are directly accessible in the folder inside Optional Installs.
At least some of the seed notes state machine compatibility. The reason i bought the MacBook was for this project but i like the machine either way.
Pacifist doesn’t work correctly for me yet either, i have to boot into a Leopard partition and use pacifist and target the Snow Leopard drive.
I recon this has been sorted out, right? Macports work on 10A190 without major issues, though modification of some portfiles is required for them to build. Kencu has been super-helpful in this regard, but his fixes do not cover all ports that one may need, so it makes sense to use his set-up and add your own local portfiles.
Known problems:
– Few ports will still fail, since they fail for any PowerPC OS. Doesn’t mean it is impossible to build them, but it may be a non-trivial problem to deal with.
– So far I am unable to build anything for ppc64 on 10.6 PPC, and it is likely out of possibility, unless we somehow add ppc64 support back (perhaps close to impossible).
– Clang is non-functional, gcc builds up to gcc7 (though requires special patches); while several people confirmed gcc8 and even gcc10 build on 10.5.8, I am still in the process of trying to replicate that. So far I kept getting Bus errors for any gcc8+.
P. S. Outside of Macports, look here: https://github.com/iains
I cannot yet verify this works on 10A190, but I will try to make it.
Could you check which Apple gcc4.2 version you got running? I’m curious which is the last to work (i.e. from which 10.6 build).
P. S. Btw do we have all available seed notes collected somewhere?
Sidebar:
I’m starting to think ongoing discussion of Macports on SL-PPC ought to be be spun over into a new thread, as it’s not a core component of Snow Leopard.
If one gets created by one of y’all, I’ll be sure to link it from this thread’s wikipost.
I am not sure that’s needed. The only reason Macports is ever discussed here is because that’s a working way to build soft which is relatively easier than doing everything on its own. The issue is not “how to fix Macports for SL” but how to build soft for SL in an optimal way.