Ok I will try to get an invite for Stones.
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
Ok I will try to get an invite for Stones.
Is it possible to use the Finder from older builds with PPC support to help the boot process finish?
I think someone mentioned in this thread that they tried something of the sort and that did not work, but I am unsure of particulars.
Unfortunately, no. There is a pretty strong relationship between mach kernel and Finder version. Much earlier during this project, sometime in 2020, we tried using Finder from 10.5.8 with Builds 10A96 and (I think) 10A190, and this combination crashed. We’ve also tried bringing in Finder from 10A96 and 10A190 into 10A222, and this also did not work. There could be some other combination of Finder from one build which might work with an adjacent build, but it’s not a combination we’ve found yet — definitely not with the UB/PPC side of things.
On an unrelated note, I may have found Build 10A286 somewhere. It may be some time before I can verify it’s a solid lead. It won’t necessarily aid with UB/PPC suitability, but if I can acquire it, it can be added to the Macgarden and/or Archive-dot-org collections for other people to have access for their own curiosity. The one thing from 10A286 which could be interesting, even for us, is it is where the most evolved kexts for Apple’s version of ZFS lived before Apple yanked the plug on its development (over such a petty, petty reason… and it wouldn’t be for another eight years before a completely different, but completely proprietary stand-in called APFS was conjured up).
Have you got a list of what you personally replaced and, importantly, from which version of 10.5.x?
I reinstalled 10a190 and installed Xcode from 10a222. Same story, it installed successfully, but cannot compile.
gcc shows ver. 5626 (as expected, in between).
I will copy components somewhere to be able to pull something usable later on from it.
But for now it is confirmed that as is none of post-10a190 Xcodes work.
Correction: Xcode from 10A222 itself actually seems working. Compiler is not.
Have you saved the copy of those pages? I saved repository of amended ports, but didn’t expect textual instructions to vanish
In Table 4, roughly 95 to 98 pr cent of what you see in the 10.5.8 column, next to the 10A96 column, are kexts, frameworks, bundles, applications,and other components which I have tested personally in the 10A96 environment.
In that table, you’ll note how there are some which have also been tested in 10A190, but that testing was completed by other folks; much on that side still needs to be tested, one at a time, much as I’ve done over on the 10A96 side. If you see an item labelled purple (a conditional “pass”) or green (a likely universal “pass”), I can attest that the component loads in 10A96 and it is what I’m using presently with my own testing setup. Along the way, it’s good to keep in mind how I’ve had to go back to change red items to purple/green and purple/green to red as new testing information emerged.
Once I get to a stopping place with other things I’m trying elsewhere with the build, I need to learn how to correctly prepare installer packages and try my hand at making a home-grown OS X 10A96 installer with changes segued into place, so that folks will have a couple options when trying out 10A96.
I’ll update Table 1 with a link to it and make a mention right here once I have it locally and uploaded to an archive locale.
Have you saved the copy of those pages? I saved repository of amended ports, but didn’t expect textual instructions to vanish
That’s because kencu chose to do that of his own volition, as was his wont. His reporting me for citing his disruptive, self-centred conduct on this project was why I was suspended for a week in October. He could have provided us with either permanent repositories where we could have grabbed the stuff he posted/provided briefly, or else he could have contacted any of us, including you, with a courtesy direct message providing info on where and how to find that stuff. He did neither. Instead, he gave us virtually no warning that he was going to yank the stuff, deleted his work, and he did so well within 24 hours of making that announcement (as I think ChrisCharman discovered quite quickly when he went to the disappearing link and found nothing). The entire matter was vexing, to say the least.
Last edited:
Update on software:
Fidelia 1.0.8 works with no issues. Cannot try high def files right now, but lossless work.
Interarchy 10.0.2 works (FTP at least).
Data Rescue 3.2.3 apparently works.
Split & Concat 3 apparently works.
Wireshare crashes on start.
Shiira 2.3 starts and opens some sites but is unusable with most of sites due to certificate issues and ErrorUnsupportedURL errors.
Fidelia 1.0.8 works with no issues. Cannot try high def files right now, but lossless work.
Interarchy 10.0.2 works (FTP at least).
Data Rescue 3.2.3 apparently works.
Split & Concat 3 apparently works.
Wireshare crashes on start.
Shiira 2.3 starts and opens some sites but is unusable with most of sites due to certificate issues and ErrorUnsupportedURL errors.
Anyone has ideas how to force Cmake to build? I have amended OS versions in port file, and went from a failure at 22% to failure at 76% with the same fatal error: ImageIO/ImageIO.h: No such file or directory:
Code:
:info:build [ 76%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmScanDepFormat.cxx.o
:info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.21.4/Source && /opt/local/bin/g++-mp-7 -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.21.4/Source -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.21.4/Source/LexerParser -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.21.4/Source/CTest -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.21.4/Source/CPack -isystem /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.21.4/Utilities/std -isystem /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.21.4/Utilities -isystem /opt/local/include -pipe -Os -D_DARWIN_C_SOURCE -D_GLIBCXX_USE_CXX11_ABI=0 -arch ppc -O3 -DNDEBUG -mmacosx-version-min=10.6 -std=c++1z -MD -MT Source/CMakeFiles/CMakeLib.dir/cmScanDepFormat.cxx.o -MF CMakeFiles/CMakeLib.dir/cmScanDepFormat.cxx.o.d -o CMakeFiles/CMakeLib.dir/cmScanDepFormat.cxx.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.21.4/Source/cmScanDepFormat.cxx
:info:build In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.21.4/Source/cmGlobalXCodeGenerator.cxx:54:0:
:info:build /System/Library/Frameworks/ApplicationServices.framework/Headers/ApplicationServices.h:55:10: fatal error: ImageIO/ImageIO.h: No such file or directory
:info:build #include <ImageIO/ImageIO.h>
:info:build ^~~~~~~~~~~~~~~~~~~
:info:build compilation terminated.
:info:build make[2]: *** [Source/CMakeFiles/CMakeLib.dir/cmGlobalXCodeGenerator.cxx.o] Error 1
:info:build make[2]: *** Waiting for unfinished jobs....
:info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-v3.21.4-f65cebf51a2cf3af2017fd9b03c685c77da00c74'
:info:build make[1]: *** [Source/CMakeFiles/CMakeLib.dir/all] Error 2
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-v3.21.4-f65cebf51a2cf3af2017fd9b03c685c77da00c74'
:info:build make: *** [all] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-v3.21.4-f65cebf51a2cf3af2017fd9b03c685c77da00c74'
:info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/work/cmake-3.21.4" && /usr/bin/make -j4 -w all VERBOSE=ON
:info:build Exit code: 2
:error:build Failed to build cmake: command execution failed
:debug:build Error code: CHILDSTATUS 14907 2
:debug:build Backtrace: command execution failed
:debug:build while executing
:debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
:debug:build invoked from within
:debug:build "command_exec -callback portprogress::target_progress_callback build"
:debug:build (procedure "portbuild::build_main" line 8)
:debug:build invoked from within
:debug:build "$procedure $targetname"
:error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_cmake/cmake/main.log for details.
I would check that the imageIO header is present in the include folder or potentially it could be needed in the apple internal development folder that is only created when ‘make install headers’ is run on certain apple open source projects, particularly the internal development tools which are not installed during a normal Xcode install. If it’s not anywhere on the system, you could check if it’s present on Retail SL or Leopard and then, after reviewing the header for any architecture specific changes you may need to make, copy it to the appropriate location. This is similar to the missing XCRun that needs to be replaced, also TargetConfig etc
Edit: This header should reside in the Application Services Framework first and foremost
Yes i was disappointed to find this as well.Have you saved the copy of those pages? I saved repository of amended ports, but didn’t expect textual instructions to vanish
I can confirm that MSN Messenger for Mac version 3.0 works fine in Clouded Leopard, by redirecting it to Escargot.
Here you go @barracuda156
This is the updated installer for the Snow Leopard 10.6.0 version if LibXML2 that i built. This revision fixes the issue with flatnamespace from the previous version. Please let me know if there are any issues at all.
There is a (probably dead) magnet out there for Build 10A421a which clocks in at 5.62GB — slightly smaller in size from some of the earlier DPs, but certainly within the realm of being a whole, standalone installation of that iteration of the DPs.
Also, I now have Build 10A286 (client) and am now downloading some other DP builds. There will be some new-to-us kernel debug kits, as well. I’ll get those up as archives and link to them in Table 1 on the wikipost as they’re ready. So far, there aren’t surprises as to build versions (all of these were released via ADC and/or at WWDC), but they will fill in some gaps — even if they aren’t UB-bootable for PowerPC Macs. At this point, as things go, a completeness in chronicling the entirety of Snow Leopard’s development ought to be a secondary arm of this project.
Fantastic work @B S Magnet! This is great news!
I’ve spent some time over the last couple of days investigating an issue with DirectoryServices on my modified build of 10A190, namely excessively high CPU consumption. It was bugging me as it’s difficult to compile things on a system that has the processor already at full load.
Directory Services changed a lot between 10.5 and 10.6 and, unfortunately, although many of the components are still universal in 10.6.0 - the DirectoryServices Binary in usr/sbin is intel only. I’m testing out some different combinations to see what may or may not work, and thankfully with more builds now made available thanks to @B S Magnet, hopefully there will be more spare parts to play with. My only real concern is a possible dependency on IOKit but we’ll see in time.
For the moment, if anyone is experiencing high CPU usage or DirectoryServices related issues in 10A190 then a working solution is to replace the Framework, PrivateFramework, Binary and supporting files on the system with the earlier Leopard version. Obviously this is a step back in terms of moving the build forward, but in terms of improving stability, i would highly recommend doing this as at least it is a working temporary fix providing a more useable experience on build 10A190.
I would like to add that the completionism that often takes hold of me is in total agreement with this secondary aim, of the gathering and archiving of as much of the development journey of Snow Leopard as possible.
Last edited:
I’m just the courier; there are some really kind folks out there looking after us.
I’m putting on my pedantic hat for just a sec to add how, in theory, dropping in 10.5.8 stuff into 10A96 or 10A190 to fix issues is more like a moving a half-step forward since 10.5.8 came out just over a year after 10A96 and just a hair over nine months after 10A190.
OK. I’ve put the pedantic hat back in the drawer.
I think the idea here is to help reduce the overall frequency of people having to look far and wide for known builds. And also, by having everything we’re aware of being aggregated, it becomes easier for everyone to identify any novel builds which may later emerge from who-even-knows-where [I’m looking squarely at y’all, internal-only-builds-which-purportedly-ran-as-UBs].
I used a Leopard 10.5.0 Retail (actually Student Developer Kit) version as it was within arms reach.
Last edited:
I was thinking earlier today about the need for a dedicated ‘PowerPC Architecture Development Reference’ thread and how we could leverage the combined knowledge of the community with a wiki and reference manuals/documentation. Does anybody know if this already exists on MR? If it doesn’t i feel it would be useful to start one for many reasons, and could of course benefit this project and future projects.
There are many talented, knowledgeable and resourceful people in this community but we often rely on character reference and historical reference to old threads or posts. It would be good to pool this information, much in the way that has already been done for the popular stickies.
The aim of the thread would simply be to improve the communities understanding of and capacity for development on our machines.
The success of this would depend massively on community contribution and support so thoughts very much welcomed.
There are many talented, knowledgeable and resourceful people in this community but we often rely on character reference and historical reference to old threads or posts. It would be good to pool this information, much in the way that has already been done for the popular stickies.
The aim of the thread would simply be to improve the communities understanding of and capacity for development on our machines.
The success of this would depend massively on community contribution and support so thoughts very much welcomed.
When putting together the PPC SuperWikiPost, I didn’t see anything like this. (I think I covered every known PowerPC-related wikipost on MR, but it’s possible I could have missed it.)
Would you be interested to kick off a new WikiPost for this scope? If you do, I can add it to that SuperWikiPost.
Although software development is beyond my wheelhouse, this sounds like an excellent idea to bring to life for everyone who knows a lot more about how to build/fix/modify software.
Yeah exactly, the PPC SuperWikiPost is one of the more successful examples of what we need but this would be geared more toward collating and advancing our development knowledge. For many years before i joined to contribute to this project, i often used these forums as reference for fixing, tweaking and using my machines as i’m sure many others still do - but it is much better to have collated information that is maintained than hunt through posts on threads that are often buried.
I’m learning as i go as well, and that is the second inspiration for the idea. We already have a few separate threads that are being used to educate and aid ppc users with building things like TenFourFox for example. We would all benefit from this endeavour i feel.
I’m happy to get it started when i have a day-off next, hopefully others will contribute over time. I’m glad the wiki-master will be on board!
Looking back over the thousands of posts we have amassed on this thread i see that @Larsvonhier was leeching 10A335 at one point, was this ever uploaded anywhere as we’re still missing that build?