XCode for Sorbet Leopard?

[mac57mac57]

I am about to install XCode into my Air Quad Sorbet Leopard install. I know I have done this on other Sorbet installs but I can't find any written notes. Is there a specific version of XCode for Sorbet, or should I just install the vanilla Leopard tools?

 

[JackAHyde]

As somebody who had trouble getting Xcode installed on Sorbet with a Dual 2.0 GHZ G5, I can only hope you have a smoother experience than I did. I had to get vanilla Leopard tools, but I ran into so many issues getting an installer that wasn't corrupt, the installer to actually finish, and having to erase the incomplete installation directory whenever the install failed at the halfway point.

If I had to give any specific tip, I would say to use Pacifist to install just the CLI stuff individually from the install package. I don't remember which specific packages I selected, but this won't work if you really want everything from Xcode installed. Even with Pacifist, it was still an endeavor to install, but it was the only thing that worked for me. Then again, with your quad setup, you'll most likely have less of a problem (my CPU would spike and even almost max out during the installers).

 

[mac57mac57]

Thanks for the input @JackAHyde. I will be doing the install this morning, and I will let you know how it goes later today

 

[barracuda156]

I am about to install XCode into my Air Quad Sorbet Leopard install. I know I have done this on other Sorbet installs but I can't find any written notes. Is there a specific version of XCode for Sorbet, or should I just install the vanilla Leopard tools?

Are you even serious? "Sorbet" Leopard is just Leopard with some tweaks, for the better or worse. Why would it have it own special Xcode? Wallpapers are not a part of the SDK

 

[mac57mac57]

Are you even serious?

Quite serious, @barracuda156. Sorbet is fundamentally a large assembled set of Leopard optimizations - why not XCode optimizations as well? It was sensible (IMHO) to check before installing the vanilla version.

I have at this point a nearly perfectly configured AirQuad environment running Sorbet. The LAST thing I want to do now is mess it up with a bad install of new tools.

 

[barracuda156]

Quite serious, @barracuda156. Sorbet is fundamentally a large assembled set of Leopard optimizations - why not XCode optimizations as well? It was sensible (IMHO) to check before installing the vanilla version.

I have at this point a nearly perfectly configured AirQuad environment running Sorbet. The LAST thing I want to do now is mess it up with a bad install of new tools.

These are mutually contradictory goals. The most stable and reliable system on powerpc is the official release of Leopard: it was tested by Apple, after all. Any tweaks inevitably make it less stable and reliable, at least potentially (no guarantee a given bug hits you, of course). Of course, you may get various improvements, but if the ultimate aim is vanilla reliability, the very start was wrong.

 

[Doq]

I'm just going to avoid this bikeshedding session and just point OP to the last available Xcode for at least 10.5.7, version 3.1.4

https://macintoshgarden.org/apps/apple-xcode

(3.2.0 and later require Snow Leopard)

 

[mac57mac57]

I am pleased to report that, as expected, the vanilla Leopard XCode installed cleanly - no issues whatsoever. I ran a few test compiles and it's working as it should... at least at this level of testing.

Just as a data point, I have been running Sorbet for months now on four different G5s (two Quads, two Duals) and on a G4 Sawtooth - across the board it has been rock solid. I am aware of only one issue, that being iSight support, but even that has cleared up on my latest install.

 

[JackAHyde]

I am somewhat envious that you got it to install cleanly with zero issues. I only wish I had as easy of a time when I attempted it. Regardless, congrats on getting it to work just fine.

EDIT: While it's not likely that it caused my issues installing Xcode, I did notice that my "About this Mac" was reporting my OS as 10.8.5 instead of 10.5.8, so maybe the Mountain Leopard install pack that I was using caused this whole mess? I reverted things back and manually changed it to 10.5.8 to get certain apps like Mactracker to work again. I might try reinstalling Xcode eventually to see if that had anything to do with my issues.

 

[barracuda156]

I did notice that my "About this Mac" was reporting my OS as 10.8.5 instead of 10.5.8, so maybe the Mountain Leopard install pack that I was using caused this whole mess?

Why would you install anything 10.8-related onto 10.5? There are 0 ppc slices in 10.8, AFAIK. (10.7 still have some remnants, perhaps.)

 

[JackAHyde]

Why would you install anything 10.8-related onto 10.5? There are 0 ppc slices in 10.8, AFAIK. (10.7 still have some remnants, perhaps.)

No, not actual Mountain Lion software. It was a cosmetic install pack that made Sorbet look like Mountain Lion, down to changing the version number for some reason.

 

[barracuda156]

No, not actual Mountain Lion software. It was a cosmetic install pack that made Sorbet look like Mountain Lion, down to changing the version number for some reason.

Well, it is rather bad on the part of whomever developed this amazing “upgrade” not to warn end-users of potential consequences.

 

[JackAHyde]

Well, it is rather bad on the part of whomever developed this amazing “upgrade” not to warn end-users of potential consequences.

It was one of the bundled features with Sorbet along with the macOS High Sierra cosmetic pack and the iOS wallpaper pack. Regardless, I didn't know that the ML pack was going to actually affect things that much. I've since removed it, but the only thing I miss from the Mountain Lion pack now is the login background. I'm honestly liking how much more skeuomorphic vanilla Leopard looks by comparison.

 

[barracuda156]

It was one of the bundled features with Sorbet along with the macOS High Sierra cosmetic pack and the iOS wallpaper pack. Regardless, I didn't know that the ML pack was going to actually affect things that much.

That’s exactly the point. End-user should not be expected to debug anything, and more so “Easter egg” bugs deliberately hidden in a bundle. Whoever made that should probably stay away from development of end-user-targeted products.

P. S. If that “version upgrade” was done via changing the value in the system plist file, no surprise it will lead to obscure breakages. Several APIs get OS version from there, and that value can be used for conditional code.

 

[Doq]

P. S. If that “version upgrade” was done via changing the value in the system plist file, no surprise it will lead to obscure breakages. Several APIs get OS version from there, and that value can be used for conditional code.

I believe this is the reason why the version string change in LeopardRebirth is done in the language file instead.