Snow Leopard on Unsupported PowerPC Macs

[ChrisCharman]

Given how InstantOff never came to pass, and given how TextEdit is in their list of “Instant Off killable”, I’m starting to think InstantOff is an early implementation of the save-state feature which restores applications and windows between restarts — without losing anything (and which became a thing from Lion onward, and from TextEdit onward in 10.6.8, if not also as far back as 10.6.0).

I assumed it was referring to the changes made in 10.6 that allowed developers to code their apps, and flag them to let OS X know, that it can kill all the processes instantly without fear of hangs etc. This improves shut down speed for the system. I could be mistaken but I believe this feature was released with 10.6.0 but I can’t remember the name of it right now, if it’s not instant off.

 

[barracuda156]

Nice. You ought to throw those onto the garden (especially if those versions were released before 2012). I could certainly use BarCode Pro.

Here you go.

MultiLex: https://macintoshgarden.org/apps/multilex-pro
BarCode Pro: https://macintoshgarden.org/apps/barcode-pro

 

[barracuda156]

Once i've built everything i plan to build and then rebuilt it all again with the binaries, libraries, headers etc in place, i will then share a full list and an installer so that others don't need to struggle unnecessarily. Some projects depend on other projects which depend on further projects, some require headers that don't exist on 10A190 and which must be externally sourced and so on. What is clear is that the more i build, the more useable 10A190 becomes and the more closely it matches 10A432 at least on a base system level. I will continue to work on this as i have done, but it is sporadic and only when i can find time between work and childcare of course.

Please do, that would be greatly appreciated. I can test them once installed.

P. S. Do you build these with Xcode or newer GCC?

 

[barracuda156]

@barracuda156 Yeah I haven’t run into any issues as of yet. If you go to AOSP you can download the relevant source for the build tools for each version of Xcode, including 3.2x. This in addition to the developer preview source bundles i found are on my todo list to test when i have time. I hoped cross-compiling from the MacBook would be faster, which of course it was, but i need to look more into how to ensure it doesn’t link against 10A432 intel to make the builds portable.

What do you use to cross-compile?

I am trying to build gcc11 cross-compiler on my Intel MacMini with Catalina and Xcode 12.4, but so far it fails.

 

[barracuda156]

Got this on my Quad now when booting into 10.6. Rebooted, and everything working normally. Is it of any concern or can be ignored?

 

[ChrisCharman]

Please do, that would be greatly appreciated. I can test them once installed.

P. S. Do you build these with Xcode or newer GCC?

I could create another beta updater with the above listed projects if you want to test that it’s portable? Will be a large file though and might break your system so it’s entirely up to you.

Command line tools for the most part although some projects do require the use of XcodeBuild.

What do you use to cross-compile?

I am trying to build gcc11 cross-compiler on my Intel MacMini with Catalina and Xcode 12.4, but so far it fails.

10.6 Xcode tools on intel can target PPC still but as i said i’m still working on getting those projects to work. It might be easier to cross-compile on an intel machine running 10A190 but at this point i’ve replaced too many binaries and libraries with powerpc only versions for my system to be useable on intel machines.

Got this on my Quad now when booting into 10.6. Rebooted, and everything working normally. Is it of any concern or can be ignored?

View attachment 1922798

What does the log say if you check using console once booted into the desktop environment? Have you replaced anything recently?

 

[barracuda156]

I could create another beta updater with the above listed projects if you want to test that it’s portable? Will be a large file though and might break your system so it’s entirely up to you.

Yeah, please. I understand that no guarantees attached whatsoever, but if you are running the same build, then identical operations are unlikely to break the system. I will probably make a back-up of macports tree, just in case (and makes sense to do regardless). There is no precious data on my Quad, only stuff that is time-consuming to make.

 

[barracuda156]

What does the log say if you check using console once booted into the desktop environment? Have you replaced anything recently?

I only get system log after that reboot, and it starts with the following (and there are constant silly dyld errors ongoing, as it was before):

Dec  5 00:30:05 36-148 newsyslog[2864]: logfile turned over
Dec  5 00:30:05 36-148 [2868]:
Dec  5 00:30:06 36-148 com.apple.launchd[1] (0x711a10.sandbox-compiler[2872]): Working around rdar://problem/5982485 and allowing job to set policy for PID 2866. We should discuss having 0x700000.mdworker run under a per-user launchd.
Dec  5 00:30:08 36-148 com.apple.dyld[2865]: update_dyld_shared_cache[2865] for arch=ppc failed: flat namespace not supported in /usr/lib/libxml2.2.dylib
Dec  5 00:30:08 36-148 com.apple.dyld[2865]: update_dyld_shared_cache[2865] for arch=ppc failed: read failure copying dylib errno=2 for /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE while copying /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE to shared cache
Dec  5 00:30:08 36-148 com.apple.dyld[2865]: update_dyld_shared_cache[2865] for arch=ppc failed: read failure copying dylib errno=2 for /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation while copying /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation to shared cache
Dec  5 00:30:08 36-148 com.apple.dyld[2865]: update_dyld_shared_cache[2865] for arch=ppc failed: read failure copying dylib errno=2 for /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit while copying /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit to shared cache
Dec  5 00:30:08 36-148 com.apple.dyld[2865]: update_dyld_shared_cache[2865] for arch=ppc failed: read failure copying dylib errno=2 for /System/Library/QuickTime/QuickTimeImporters.component/Contents/MacOS/QuickTimeImporters while copying /System/Library/QuickTime/QuickTimeImporters.component/Contents/MacOS/QuickTimeImporters to shared cache
Dec  5 00:30:08 36-148 com.apple.dyld[2865]: update_dyld_shared_cache[2865] for arch=ppc failed: read failure copying dylib errno=2 for /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib while copying /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib to shared cache
Dec  5 00:30:15 36-148 com.apple.launchd[1] (com.apple.usbmuxd[2873]): getpwnam("_usbmuxd") failed
Dec  5 00:30:15 36-148 com.apple.launchd[1] (com.apple.usbmuxd[2873]): Exited with exit code: 1
Dec  5 00:30:15 36-148 com.apple.launchd[1] (com.apple.usbmuxd): Throttling respawn: Will start in 10 seconds
Dec  5 00:30:19 36-148 com.apple.dyld[2875]: update_dyld_shared_cache[2875] for arch=ppc failed: flat namespace not supported in /usr/lib/libxml2.2.dylib
Dec  5 00:30:19 36-148 com.apple.dyld[2875]: update_dyld_shared_cache[2875] for arch=ppc failed: read failure copying dylib errno=2 for /System/Library/PrivateFrameworks/CorePDF.framework/Versions/A/CorePDF while copying /System/Library/PrivateFrameworks/CorePDF.framework/Versions/A/CorePDF to shared cache

 

[barracuda156]

I finally got Rstan to build with a help from Stan developer who made a patched version which does not depend on libv8. Took several hours to figure out how to solve several errors with which the build was consistently failing. It worked through completion now.

However test model compilation in Rstan still fails, referring to libtbb: https://discourse.mc-stan.org/t/ove...r-make-v8-build-on-powerpc-mac-r-4-1-2/25432/

 

[ChrisCharman]

I only get system log after that reboot, and it starts with the following (and there are constant silly dyld errors ongoing, as it was before):

Dec  5 00:30:05 36-148 newsyslog[2864]: logfile turned over
Dec  5 00:30:05 36-148 [2868]:
Dec  5 00:30:06 36-148 com.apple.launchd[1] (0x711a10.sandbox-compiler[2872]): Working around rdar://problem/5982485 and allowing job to set policy for PID 2866. We should discuss having 0x700000.mdworker run under a per-user launchd.
Dec  5 00:30:08 36-148 com.apple.dyld[2865]: update_dyld_shared_cache[2865] for arch=ppc failed: flat namespace not supported in /usr/lib/libxml2.2.dylib
Dec  5 00:30:08 36-148 com.apple.dyld[2865]: update_dyld_shared_cache[2865] for arch=ppc failed: read failure copying dylib errno=2 for /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE while copying /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE to shared cache
Dec  5 00:30:08 36-148 com.apple.dyld[2865]: update_dyld_shared_cache[2865] for arch=ppc failed: read failure copying dylib errno=2 for /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation while copying /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation to shared cache
Dec  5 00:30:08 36-148 com.apple.dyld[2865]: update_dyld_shared_cache[2865] for arch=ppc failed: read failure copying dylib errno=2 for /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit while copying /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit to shared cache
Dec  5 00:30:08 36-148 com.apple.dyld[2865]: update_dyld_shared_cache[2865] for arch=ppc failed: read failure copying dylib errno=2 for /System/Library/QuickTime/QuickTimeImporters.component/Contents/MacOS/QuickTimeImporters while copying /System/Library/QuickTime/QuickTimeImporters.component/Contents/MacOS/QuickTimeImporters to shared cache
Dec  5 00:30:08 36-148 com.apple.dyld[2865]: update_dyld_shared_cache[2865] for arch=ppc failed: read failure copying dylib errno=2 for /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib while copying /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib to shared cache
Dec  5 00:30:15 36-148 com.apple.launchd[1] (com.apple.usbmuxd[2873]): getpwnam("_usbmuxd") failed
Dec  5 00:30:15 36-148 com.apple.launchd[1] (com.apple.usbmuxd[2873]): Exited with exit code: 1
Dec  5 00:30:15 36-148 com.apple.launchd[1] (com.apple.usbmuxd): Throttling respawn: Will start in 10 seconds
Dec  5 00:30:19 36-148 com.apple.dyld[2875]: update_dyld_shared_cache[2875] for arch=ppc failed: flat namespace not supported in /usr/lib/libxml2.2.dylib
Dec  5 00:30:19 36-148 com.apple.dyld[2875]: update_dyld_shared_cache[2875] for arch=ppc failed: read failure copying dylib errno=2 for /System/Library/PrivateFrameworks/CorePDF.framework/Versions/A/CorePDF while copying /System/Library/PrivateFrameworks/CorePDF.framework/Versions/A/CorePDF to shared cache

I would suggest deleting the system caches and rebuilding the dyld cache. The LibXML2 error should have been fixed with the last update i shared so it’s possible a cache refresh may resolve the issue.

 

[aurora72]

the last version that runs without problem is version 6.10370 from around May 2011 ( the last I could find through Wayback Machine that runs. the 6.20.. does not run anymore)

I've just downloaded the TeamViewer version you mentioned (https://web.archive.org/web/20110802173741if_/http://www.teamviewer.com/download/TeamViewer.dmg) it does run but it doesn't run in a stable way.

 

[barracuda156]

I would suggest deleting the system caches and rebuilding the dyld cache. The LibXML2 error should have been fixed with the last update i shared so it’s possible a cache refresh may resolve the issue.

Thanks, I will try that and update you.

 

[barracuda156]

Does anyone have an idea why iWorks fail to start? Its support files are actually installed in the appropriate location in Application Support (same as in 10.5.8).

Ironically, AppleWorks 6.2.9 installs and starts without issues.

 

[barracuda156]

Sorry if a silly question, but where to get the version of Transmission mentioned in the Wiki that is supposed to work?

 

[B S Magnet]

Sorry if a silly question, but where to get the version of Transmission mentioned in the Wiki that is supposed to work?

It’s not a silly question at all.

It is available on the Garden as the seventh/final download in the list.

 

[barracuda156]

It’s not a silly question at all.

It is available on the Garden as the seventh/final download in the list.

I am trying to build Transmission-X11 v. 3 now by the way. But little hope. Currently stuck at building aom dependency. (But most of other dependencies are built already.)

Other option will be to build Deluge: https://ports.macports.org/port/deluge/
But it also will need aom to be built.

Dependency hell LOL

 

[B S Magnet]

I am trying to build Transmission-X11 v. 3 now by the way. But little hope. Currently stuck at building aom dependency. (But most of other dependencies are built already.)

Other option will be to build Deluge: https://ports.macports.org/port/deluge/
But it also will need aom to be built.

Dependency hell LOL

I applaud your effort and send you good luck!

I’m fine with 2.84, as it’s on par with the final version of Transmission (as opposed to Transmission-qt) which runs on OS X 10.6.8. I don’t really need anything newer than that, as the features between Transmission 2.84 and subsequent versions for 10.7+ are not very different.

 

[barracuda156]

I applaud your effort and send you good luck!

I’m fine with 2.84, as it’s on par with the final version of Transmission (as opposed to Transmission-qt) which runs on OS X 10.6.8. I don’t really need anything newer than that, as the features between Transmission 2.84 and subsequent versions for 10.7+ are not very different.

But 2.84 won't work on 10.6 PPC, only qt does?

 

[B S Magnet]

But 2.84 won't work on 10.6 PPC, only qt does?

Transmission 2.84 definitely doesn’t, but Transmission-qt 2.84 does.

Transmission 2.22, the final version made for Leopard, won’t run properly on SL-PPC, but Transmission-qt 2.84 will. In fact, Transmission-qt 2.84 runs on Tiger, and it’s what I use on my iBook G3.

 

[barracuda156]

Transmission 2.84 definitely doesn’t, but Transmission-qt 2.84 does.

Transmission 2.22, the final version made for Leopard, won’t run properly on SL-PPC, but Transmission-qt 2.84 will. In fact, Transmission-qt 2.84 runs on Tiger, and it’s what I use on my iBook G3.

Have you tried any eMule client?

 

[B S Magnet]

Have you tried any eMule client?

I haven’t touched any eMule/eDonkey-related stuff since probably around 2004.

 

[barracuda156]

Update on software:

RipIt 1.5 works
MDRP 2.2 and 3.4.2 work

XLD 20211018 work (latest version from the developer)

AppleWorks 6.2.9 work

DjView 4.4 work
ViewIt 1.0.2 works
GraphicConverter 6.6.1 apparently works (need to check which was the last one for PPC)

 

[barracuda156]

I applaud your effort and send you good luck!

I’m fine with 2.84, as it’s on par with the final version of Transmission (as opposed to Transmission-qt) which runs on OS X 10.6.8. I don’t really need anything newer than that, as the features between Transmission 2.84 and subsequent versions for 10.7+ are not very different.

Thanks to a suggestion of kencu on a macports ticket, I bypassed dependency on failing aom, and built all required dependencies for Transmission-X11. Transmission itself fails so far though.

Doing a parallel build on 10.5.8 now, if it also fails there, then Deluge is a second choice to try.

P. S. Transmission (not X11, but a regular version) won't build for sure until we find a way to adapt XIB files for Xcode 3.2 (if that is feasible at all). I tried removing Xcode and OS versions checks to initialize building Transmission, but it failed with multiple XIB errors. This is the same problem I faced with R GUI 1.70+. I dunno how to solve it.

Does anyone understands ibtool and XIBs?

 

[barracuda156]

A couple of questions to everyone involved in developing:

1. Has anyone succeeded with building TFF from source, as described here? https://github.com/classilla/tenfourfox/wiki/HowToBuildFPR
Fails for me on 10.6 PPC with gcc4.9, gcc6 and gcc7 and whichever MacOS targets and SDKs (errors vary, but all attempts fail).
TBH I am yet to try the recommended gcc4.8, but I would expect 4.9 to be similar and not worse, but it fails, at least for me.

I am very far from web development, so other thing to ask: why nothing similar to TFF exists Webkit-based? Webkit is better than Mozilla and also opensource. What prevents building such browser on PPC?

2. If anyone knows of an opensource replacement for Apple ibtool or some utility that can convert XIB files to something that Xcode 3.2 can digest, please update us.

@ChrisCharman @B S Magnet

 

[B S Magnet]

A couple of questions to everyone involved in developing:

1. Has anyone succeeded with building TFF from source, as described here? https://github.com/classilla/tenfourfox/wiki/HowToBuildFPR
Fails for me on 10.6 PPC with gcc4.9, gcc6 and gcc7 and whichever MacOS targets and SDKs (errors vary, but all attempts fail).
TBH I am yet to try the recommended gcc4.8, but I would expect 4.9 to be similar and not worse, but it fails, at least for me.

I haven’t, but there are some fellow MR members who’ve been doing that on a separate project. And there’s also the Interweb-PPC project, which continues onward courtesy of @wicknix .

I am very far from web development, so other thing to ask: why nothing similar to TFF exists Webkit-based? Webkit is better than Mozilla and also opensource. What prevents building such browser on PPC?

Maybe it has to do with the current libraries produced by Apple being closed-source and not easily portable to legacy WebKit builds, but to be honest, I don’t know. You ought to contact Tobias Netzel, the developer of the last WebKit — Leopard WebKit — and ask him about the logistics and obstacles of trying to build WebKit. Evidently he stopped working on it in 2018 for some reason.