Oh, well, if I'd found that before it would have saved me a certain amount of time and mucking about. Oh well! Never mind. It was educational.
yeah my lasting memory from that ordeal was the amount of faffing about just to get a Darwin build environment up and running, it turns out for example you (or at least I could not) cannot compile this using an intel tiger install, has to be a PPC one (at first I used an intel tiger VM for ease of use and speed)
interestingly when I put together a 10.5.8 kernel with the same patch applied, I had to use an intel mac for that! go figure...
perhaps it might be worth documenting your own findings/how you got things building

since I utterly failed to do that!
one thing I have always wanted to do, or more specifically see someone more knowledgeable then me do
is back/forward port CPU definitions to OS X kernels
what i mean by CPU definitions is
if you look at how OS X kernel identifies CPU's, it looks at the CPU PVR (Processor version register) and then it sorts it into 5 main PPC architecture sub-groups
you can see that they are divided into major groups of PowerPC, PowerPC 750, PowerPC 7400, PowerPC 7450 and PowerPC 970
and then each of those major groups has sub groups, so that for example if it encounters a PVR of a 7447A the 7447A sub-group will tell OS X that yeah this CPU supports an L2 cache and has DFS for example
and this is important because for example when you patch tiger like this its running in PowerPC Generic mode, so for example TenFourFox G3 build wont actually run on a tiger 604 machine, because for some reason its compiled for the PPC750 arch specifically, so since OS X is Generic mode it returns bad-arch
so it would be interesting if things could be re-jigged so that when OS X tiger is run on a 604, it runs in 750 mode, but also it would be interesting to see if 604 mode could be added back to tiger?
and then likewise 10.2.8 for example has no halt on unknown CPU check, so you can freely boot it on newer CPU's like a 7447A, but if you go to about this mac or do a machine command you will see it obviously does not recognise the 7447A properly and is in running in PPC Generic mode, so it would be cool to see if the 7447A definition could be brought to 10.2.8 so it sees it properly as a G4 etc
and similarly with the 970FX so that 10.2.8 G5 can run on 970FX PowerMac G5 machines

(10.2.7 G5 was the first with the halt on unknown CPU check) 10.2.8 running on 2.7Ghz PowerMac G5 would be a right giggle
early versions of OS X did actually have definitions for the 60x CPU's

(theres even a 601 definition!)
Contribute to apple-oss-distributions/xnu development by creating an account on GitHub.
github.com
and would correctly display PowerPC 604e in about this mac and when you ran the machine command

(I have often wondered if tiger still had the "PowerPC" about this mac CPU type string for when its running in PowerPC Generic mode, does it still have the 604 ones or not?)
BTW its really awesome to see tiger running on an older 604e CPU, I myself have only ever managed to run it on real hardware with a 604ev CPU, which Geekbench wont recognise for some reason (Geekbench 2 will actually recognise the PVR of most PowerPC CPU's! but for some reason it has a bug? where 604ev, 7400 7410, and 970FX CPU's are not properly recognised)
so it would be very cool to see geekbench of your 180Mhz machine, see if you can set a new Geekbench low score record?
browser.geekbench.com
BTW you can search the Geekbench database by PVR, the above are the 2 sole 604 results

( a friends 8600/250 and my 9600/300) I would love to know what a 120Mhz 604 would get, I actually snagged a 120Mhz 604 just for this purpose to slot into my 9600, but I have not yet had a chance to do so etc
I’m a bit confused by the lack of multiple 604
(ev) CPU support on Mac OS X, since the first dual CPU G4’s appeared in summer 2000, well before Mac OS X 10.3 appeared.
Technical specifications for the Power Macintosh G4 450 DP (Gigabit). Dates sold, processor type, memory info, hard drive details, price and more.
everymac.com
Given that the PPC 604 series supported the MESI protocol, what is it that prevents multi-cpu execution? A dual-core 233MHz 604(ev) should be able to compete with a 233MHz G3 I would have thought? Or is that what
@herd is talking about when referring to “PVR”?
its because of how the Dual CPU setup in the 9500/9600 works, especially with the fact that the second CPU is not exposed in the OpenFirmware Device tree, means that OS X has no idea its even there in the first place so unless someone writes a driver/expands the platform expert, to explicitly enable that second CPU, it just sits there not getting used.