opeter
macrumors 68030
I realize this is off-topic but is the Aquafox logo AI?
I think it was made before the AI craze. But, maybe I am mistaken.
I realize this is off-topic but is the Aquafox logo AI?
This seems like a neat project. I can't wait to try it out whenever I get a Power Mac G5. I would've tried it on my iMac G5 but... Things happened. I'm hoping to get some games and stuff ported over for fun. I dunno how XCode is set up in/for this, but we'll see.
I have a minor nitpick, though... Why is the image on the first post AI generated? It gives a "low effort" vibe to the project, even if that doesn't really seem to be the case here. It's probably put off a good amount of people by now.
There's no way to say for sure, but it really looks like it is.I realize this is off-topic but is the Aquafox logo AI?
Gotcha, I'll keep that in mind.You should not really need Xcode as such. (In fact even original Unix tools are required mostly as a start-off point.)
We have the proper modern toolchain for C/C++/Python etc. (No Go, and C# and Rust support is minimal, but for most of languages the current standard compilers work.)
I see, good to know. I could try designing a little banner, if any of you are interested.It was probably added when everyone wasn’t yet fed up with AI slope LOL
(Personally it is not the scenario where I would bother about visual design part. And for someone coming from DTP industry, the web is generally bad design-wise.)
The project itself was not / is not done via AI though. Both the work on the OS and my PPCPorts (of several thousands of ports, I think under a dozen have fixes largely relying on Claude, and three ports were written with Claude; in those instances they were tested, of course).
The Snow Leopard project is separate from the larger PowerPC Ports project. Barracuda develops and maintains ports for 10.6, and then I (and several others) build, test and patch for Leopard.There's no way to say for sure, but it really looks like it is.
Gotcha, I'll keep that in mind.
I see, good to know. I could try designing a little banner, if any of you are interested.
Is A5 image bootable on LSI SAS/SATA controller? I added new (invisible by motherboard sata chipset) SATA SSD (MSI S270 240GB) and succesfully formatted it as two partitions of equal size, downloaded A5 image from google drive, checked and restored it to first partition on new ssd, can see new OS in boot picker, but booting into it results in error 🙁
AppleMPTFusion.kext seems to exist there (and Get info in Leopard 10.5.8 Finder show it as Powerpc) , so not sure why it stops?
I dunno any related specifics, but a fact that an SSD is visible does not ensure it is bootable. I have an SSD on a PCIE card, which is not bootable by design, though visible and usable in 10.5 (in 10.6 it sends OS into KP due to broken AHCI kexts, sadly).
Ah, it already set to infinity 😉
Copied Powerfox (G5 version from my Leo partition), seems to be working.
Safari also works (I use wired internet connection).
Now may be I should find what kext exactly prevent normal boot for my new Snow Leo 😉
But it might be long chase.
I looked at bootx page at
and may be there is unix way to move all kext not required to boot and graphics/audio/net/usb/sas ones to some other place where Mach/BootX will not looking.
But, probably this is task not for now now, for tomorrow's now
View attachment 2645890
Developer Tools for 10.6.8 (developer version 😉)
Install these AFTER installing Xcode 3.2.6. They will overwrite unusable x86-only binaries.
Three [set of] components are here:
1. ld64 and its tools, ver. 97.17, which corresponds to Xcode 3.2.6. LTO is disabled.
2. Apple gnumake, ver. 3.81, same as in 10.6.8, just built for ppc.
3. cctools from darwin-xtools by Iain Sandoe (maintainer of GCC for Darwin), ver. 1.1.0. (ld64 components are dropped from here, since ld is much newer in xtools and may not be totally compatible with old Xcode gcc.)
Specifically, I installed the OS, installed standard Xcode 3.2.6, then installed these three pkgs.
Then I installed PPCPorts, synced sources, and I am able to build software (I have built several fundamental ports now). So ld, as, make and gcc work.
Notice, this does not mean that everything will work, since there are a lot of x86-only binaries which are not dealt with here (gm4, bison etc.). However, from what I can tell, this is a minimum that makes installation functional.
Archived pkgs:
Identical installers can be built from source using the following portfiles:
![]()
powerpc-ports/devel/sl-make at 46ca86130c9517fefd85f522897b98eddef30216 · macos-powerpc/powerpc-ports
Overlay repo with fixes to use with MacPorts on macOS PowerPC - macos-powerpc/powerpc-portsgithub.com
https://github.com/macos-powerpc/po...efd85f522897b98eddef30216/devel/darwin-xtools (use darwin-developer-tools subport)![]()
powerpc-ports/devel/sl-ld64 at 46ca86130c9517fefd85f522897b98eddef30216 · macos-powerpc/powerpc-ports
Overlay repo with fixes to use with MacPorts on macOS PowerPC - macos-powerpc/powerpc-portsgithub.com
Notice, these ports cannot be installed (as a safety measure to not overwrite binaries in /usr/bin accidentally). Use them like you use `MacPorts` port: build the installer via MacPorts, then run the installer to install the software (outside of MacPorts).
Installers are built with `sudo port pkg ${port_name}`.
DISCLAIMER: If you install these, please make sure you know what you are doing, or at least try on a clean system with no valuable data, so that you can wipe it out if something goes wrong. While I have tested this and confirmed working on a clean installation of 10.6.8, no guarantee is given whatsoever, as usual.
Is this still preferred method of getting ppcports working on 10.6.8_A5 ?
Apple download for Xcode 3.2.6 leads to sign-in, and apparently Macintosh Garden does not have it directly, their link lead to same apple page) so I used Archive.org link:
![]()
GFortran for Mac OS X 10.5 to 10.7 and Xcode 3.1.3, 3.2.2, and 3.2.6 for 10.5 and 10.6 : Free Download, Borrow, and Streaming : Internet Archive
Includes GCC for 10.5 to 10.7, GFortran for 10.5 to 10.7, and Xcode 3.1.3, 3.2.2, and 3.2.6 for 10.5 to 10.6Xcode 3.1.3 for Mac OS X 10.5Xcode 3.2.2 and 3.2.6...archive.org
currently downloading ...
I could but it would only be good for the specific host I used. Doesn't seem to be an easy way to properly partition the target disk for the restore in macOS Sequoia 15.2.
I created a raw image with qemu-img create -f raw 'diskname.img' 'size in' GB.
Then I added it to my Tiger VM and initialized it there. Shut down the VM and mounted the new disk and the 10.6.8_PPC_A5.dmg.
Then I just opened Disk Utility, selected the mounted new disk and hit 'restore', then selected the mounted '10.6.8_PPC_A5' disk as the source and hit the restore button.
That was it.
Then I start Qemu with these minimal commands...
Code:qemu-system-ppc -M mac99,via=pmu -device usb-mouse -m 2048m -hda 'path/to/the/new/img' -prom-env 'boot-args=-v ' -cpu 7457 -boot c
target/ppc: Disable software TLB for the 7450 family
(Applies to 7441, 7445, 7450, 7451, 7455, 7457, 7447 and 7447a)*We have since 2011 [1] been unable to run OpenBIOS in the 7450s and have not heard of any other software that is used with those CPUs in QEMU. A current discussion [2] shows that the 7450 software TLB is unsupported in Linux 5.15, FreeBSD 13, MacOS9, MacOSX and MorphOS3.15. With no known support in firmware or OS, this means that no code for any of the 7450 CPUs is ever ran in QEMU.Since the implementation in QEMU of the 7400 MMU is the same as the7450, except for the software TLB vs. hardware TLB search, this patch changes all 7450 cpus to the 7400 MMU model. This has the practical effect of disabling the software TLB feature while keeping other aspects of address translation working as expected.This allow us to run software on the 7450 family again.*- note that the 7448 is currently aliased in QEMU for a 7400, so it is unaffected by this change.
I tried this on 10.6.8_A5 itself, using PPCPorts and qemu 5.1.0 (higher versions like 6.1.1 compiled on Leo with some manual patching but failed to even reach OF prompt).
Sadly -cpu 7457 apparently bugged in this version, and default (G4?) for mac99 machine does not boot restored to virtualhdd image ...
I guess 9.0+ may work better, but depending on host and compiler? I getdifferent results on OSX Leopard + gcc14/16 and Linux with gcc15 on same ppc (G5) Hardware ...
May be @barracuda156 can publish .shadow file relative to master A5 image so people will have something smaller to dl and merge ? Bsdtar seems to be primary candidate for inclusion...
If you find a correctly-working version of Qemu that is newer and better than what we have in PPCPorts
sudo nvram boot-command=multi-boot
ls /Volumes/10.6.8_PPC_A5/usr/standalone/
bootcaches.plist i386/
hdiutil attach -owners on https://download.macintoshgarden.org/apps/10.6.8_PPC_A5.dmg
hdiutil: attach failed - Authentication error
power-mac-g5-user-usr:~ andrewrandrianasulu$ hdiutil attach -owners on http://old.mac.gdn/apps/10.6.8_PPC_A5.dmg
/dev/disk2 /Volumes/10.6.8_PPC_A5 1
power-mac-g5-user-usr:~ andrewrandrianasulu$ mc /Volumes/10.6.8_PPC_A5\ 1/
Is that different than what Apple has at https://github.com/apple-oss-distributions ?Currently downloading tarballs from
with wget -A "*.tar.gz" -i URL
It seems that whole set of tarballs was once mirrored on macosforge, but now it on some js heave Apple website, so not easy to dl in same form usable for darwinbuild!
Previous set of tarballs for 10.5.8 was weighting 1.2 gb, nearly 800 files. No way I will build them by hand!
cd /Volumes/Work/Darwin/DarwinNew/opensource.apple.com/tarballs/IOPCIFamily
grep "IOPCIFamily" $(find /Volumes/Work/Darwin/DarwinNew/opensource.apple.com -maxdepth 2 -type f -name 'tarballs.txt') | \
perl -pE 's|.*opensource.apple.com/(.*)/tarballs.*/(\w+\-.*).tar.gz|\1 \2|' | sort -V
10.1 IOPCIFamily-3
10.1.1 IOPCIFamily-3
10.1.2 IOPCIFamily-3
10.1.3 IOPCIFamily-3
10.1.4 IOPCIFamily-3
10.1.5 IOPCIFamily-3
10.2 IOPCIFamily-9
10.2.1 IOPCIFamily-9
10.2.2 IOPCIFamily-9
10.2.3 IOPCIFamily-9
10.2.4 IOPCIFamily-9
10.2.5 IOPCIFamily-9
10.2.6 IOPCIFamily-9
10.2.7 IOPCIFamily-12.4
10.2.8 IOPCIFamily-12.2
10.2.8.G5 IOPCIFamily-12.4
10.3 IOPCIFamily-21
10.3.1 IOPCIFamily-21
10.3.2 IOPCIFamily-21
10.3.3 IOPCIFamily-21
10.3.4 IOPCIFamily-21
10.3.5 IOPCIFamily-21
10.3.6 IOPCIFamily-21
10.3.7 IOPCIFamily-21
10.3.8 IOPCIFamily-21
10.3.9 IOPCIFamily-21
10.4 IOPCIFamily-32
10.4.1 IOPCIFamily-32
10.4.2 IOPCIFamily-32
10.4.3 IOPCIFamily-34
10.4.4.ppc IOPCIFamily-34
10.4.5.ppc IOPCIFamily-34
10.4.6.ppc IOPCIFamily-34
10.4.7.ppc IOPCIFamily-34
10.4.8.ppc IOPCIFamily-34
10.4.8.x86 IOPCIFamily-79.1
10.4.9.ppc IOPCIFamily-34
10.4.9.x86 IOPCIFamily-79.5
10.4.10.ppc IOPCIFamily-34
10.4.10.x86 IOPCIFamily-79.5
10.4.11.ppc IOPCIFamily-34
10.4.11.x86 IOPCIFamily-79.5
10.5 IOPCIFamily-103
10.5.1 IOPCIFamily-103
10.5.2 IOPCIFamily-103.1
10.5.3 IOPCIFamily-103.1
10.5.4 IOPCIFamily-103.1
10.5.5 IOPCIFamily-103.1
10.5.6 IOPCIFamily-106
10.5.7 IOPCIFamily-110
10.5.8 IOPCIFamily-110
10.6 IOPCIFamily-113
10.6.1 IOPCIFamily-113
10.6.2 IOPCIFamily-113
10.6.3 IOPCIFamily-113
10.6.4 IOPCIFamily-113
10.6.5 IOPCIFamily-115
10.6.6 IOPCIFamily-115
10.6.7 IOPCIFamily-115
10.6.8 IOPCIFamily-144
10.7 IOPCIFamily-144
...
15.2 IOPCIFamily-664.60.9
15.3 IOPCIFamily-664.81.2
15.4 IOPCIFamily-681.101.1
15.5 IOPCIFamily-681.120.3
15.6 IOPCIFamily-681.140.3
26.0 IOPCIFamily-726.0.5
26.1 IOPCIFamily-726.40.2
26.2 IOPCIFamily-726.40.2
26.3 IOPCIFamily-726.40.2
26.4 IOPCIFamily-726.100.6
26.5 IOPCIFamily-726.100.6
Is that different than what Apple has at https://github.com/apple-oss-distributions ?
There's a list of Mac OS X releases with links to the project versions:
https://opensource.apple.com/releases/
I use a script to get the map of project versions to Mac OS X releases, download the tar files to project folders (e.g. tarballs/IOPCIFamily/IOPCIFamily-144), and create symbolic links in Mac OS X folders (e.g. 10.6.8/tarballs/IOPCIFamily)
Using that arrangement, here's a command that shows what versions of Mac OS X used what versions of IOPCIFamily:
Code:cd /Volumes/Work/Darwin/DarwinNew/opensource.apple.com/tarballs/IOPCIFamily grep "IOPCIFamily" $(find /Volumes/Work/Darwin/DarwinNew/opensource.apple.com -maxdepth 2 -type f -name 'tarballs.txt') | \ perl -pE 's|.*opensource.apple.com/(.*)/tarballs.*/(\w+\-.*).tar.gz|\1 \2|' | sort -V
Code:10.1 IOPCIFamily-3 10.1.1 IOPCIFamily-3 10.1.2 IOPCIFamily-3 10.1.3 IOPCIFamily-3 10.1.4 IOPCIFamily-3 10.1.5 IOPCIFamily-3 10.2 IOPCIFamily-9 10.2.1 IOPCIFamily-9 10.2.2 IOPCIFamily-9 10.2.3 IOPCIFamily-9 10.2.4 IOPCIFamily-9 10.2.5 IOPCIFamily-9 10.2.6 IOPCIFamily-9 10.2.7 IOPCIFamily-12.4 10.2.8 IOPCIFamily-12.2 10.2.8.G5 IOPCIFamily-12.4 10.3 IOPCIFamily-21 10.3.1 IOPCIFamily-21 10.3.2 IOPCIFamily-21 10.3.3 IOPCIFamily-21 10.3.4 IOPCIFamily-21 10.3.5 IOPCIFamily-21 10.3.6 IOPCIFamily-21 10.3.7 IOPCIFamily-21 10.3.8 IOPCIFamily-21 10.3.9 IOPCIFamily-21 10.4 IOPCIFamily-32 10.4.1 IOPCIFamily-32 10.4.2 IOPCIFamily-32 10.4.3 IOPCIFamily-34 10.4.4.ppc IOPCIFamily-34 10.4.5.ppc IOPCIFamily-34 10.4.6.ppc IOPCIFamily-34 10.4.7.ppc IOPCIFamily-34 10.4.8.ppc IOPCIFamily-34 10.4.8.x86 IOPCIFamily-79.1 10.4.9.ppc IOPCIFamily-34 10.4.9.x86 IOPCIFamily-79.5 10.4.10.ppc IOPCIFamily-34 10.4.10.x86 IOPCIFamily-79.5 10.4.11.ppc IOPCIFamily-34 10.4.11.x86 IOPCIFamily-79.5 10.5 IOPCIFamily-103 10.5.1 IOPCIFamily-103 10.5.2 IOPCIFamily-103.1 10.5.3 IOPCIFamily-103.1 10.5.4 IOPCIFamily-103.1 10.5.5 IOPCIFamily-103.1 10.5.6 IOPCIFamily-106 10.5.7 IOPCIFamily-110 10.5.8 IOPCIFamily-110 10.6 IOPCIFamily-113 10.6.1 IOPCIFamily-113 10.6.2 IOPCIFamily-113 10.6.3 IOPCIFamily-113 10.6.4 IOPCIFamily-113 10.6.5 IOPCIFamily-115 10.6.6 IOPCIFamily-115 10.6.7 IOPCIFamily-115 10.6.8 IOPCIFamily-144 10.7 IOPCIFamily-144 ... 15.2 IOPCIFamily-664.60.9 15.3 IOPCIFamily-664.81.2 15.4 IOPCIFamily-681.101.1 15.5 IOPCIFamily-681.120.3 15.6 IOPCIFamily-681.140.3 26.0 IOPCIFamily-726.0.5 26.1 IOPCIFamily-726.40.2 26.2 IOPCIFamily-726.40.2 26.3 IOPCIFamily-726.40.2 26.4 IOPCIFamily-726.100.6 26.5 IOPCIFamily-726.100.6
Right. Stuff from before Mac OS X 10.0 has to be obtained from elsewhere.I think the only stuff that might have gotten lost on official Apple sites are a few pre-release versions (not of the OS, just select tools). Of those, tbh, I don’t remember anything of particular value.