Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

XCode for Sorbet Leopard?

mac57mac57

mac57mac57

macrumors 6502a
Original poster
Aug 2, 2024
688
431
Myrtle Beach, SC
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?
 
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 said:
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?
Click to expand...

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 ;)
 
barracuda156 said:
Are you even serious?
Click to expand...

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.
 
mac57mac57 said:
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.
Click to expand...

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.
 
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.
 
  • Like
Reactions: 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.
 
Last edited:
JackAHyde said:
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?
Click to expand...

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.)
 
barracuda156 said:
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.)
Click to expand...
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.
 
JackAHyde said:
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.
Click to expand...

Well, it is rather bad on the part of whomever developed this amazing “upgrade” not to warn end-users of potential consequences.
 
barracuda156 said:
Well, it is rather bad on the part of whomever developed this amazing “upgrade” not to warn end-users of potential consequences.
Click to expand...
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.
 
JackAHyde said:
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.
Click to expand...

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.
 
barracuda156 said:
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.
Click to expand...
I believe this is the reason why the version string change in LeopardRebirth is done in the language file instead.
 
Since we're on the subject, clicking the .pkg file to uninstall the Mountain Leopard cosmetic mods still won't change the version number back either. I had to manually edit a file to get the version number correct, and at this point, I thought it made more sense just to put the default Leopard version of 10.5.8 instead of Sorbet trying to be cute with 10.5.9 as its reported version number.
 
Well, I did a clean install of Sorbet Leopard on my G5, and I decided to try installing Xcode again since it seemed like it would be easy judging by this thread. Instead, I got a lot of the same errors where it gives up midway through, so I have no idea what I'm doing wrong by this point.

For the record, I didn't apply any cosmetic mods at all this time. I left the default Leopard look because I kind of missed how skeuomorphic older OS X looked.
 
I tried 3.1.4, which I recall was the last one for Leopard. Should I have tried 3.1.2 instead?
 
JackAHyde said:
Well, I did a clean install of Sorbet Leopard on my G5, and I decided to try installing Xcode again since it seemed like it would be easy judging by this thread. Instead, I got a lot of the same errors where it gives up midway through, so I have no idea what I'm doing wrong by this point.
Click to expand...

What types of errors are you getting, if I may ask?
 
z970 said:
What types of errors are you getting, if I may ask?
Click to expand...

During the install process, some random package or part fails to install entirely. It isn't always consistent. Sometimes it's just gcc, other times it's something different. It usually performs a partial install, forcing me to delete the folder and start again.

On my previous install, I tried to get around this by using Pacifist, but even that wasn't 100% reliable, and I could only partially install it instead of just clicking it and installing it like a normal package. If I'm doing something wrong, I have no clue what it is.
 
JackAHyde said:
During the install process, some random package or part fails to install entirely. It isn't always consistent. Sometimes it's just gcc, other times it's something different. It usually performs a partial install, forcing me to delete the folder and start again.

On my previous install, I tried to get around this by using Pacifist, but even that wasn't 100% reliable, and I could only partially install it instead of just clicking it and installing it like a normal package. If I'm doing something wrong, I have no clue what it is.
Click to expand...

This is just an idea, but if the errors are indeed completely inconsistent, the behavior you're describing here and in your earlier posts sounds a lot like it could be the beginnings of disk failure. I would suggest booting off and attempting an install from another drive to be sure; unpredictable write errors are usually the first to appear in my experience, followed by read errors (alongside an inability to boot the OS).
 
z970 said:
This is just an idea, but if the errors are indeed completely inconsistent, the behavior you're describing here and in your earlier posts sounds a lot like it could be the beginnings of disk failure. I would suggest booting off and attempting an install from another drive to be sure; unpredictable write errors are usually the first to appear in my experience, followed by read errors (alongside an inability to boot the OS).
Click to expand...
While that could be possible on some level, I just did a clean reinstall on a new SSD, and I got the same issue installing Xcode. In fact, Xcode is the only thing that does this to me. If what you're saying is true, it's simultaneously highly unlikely that both the old HDD and new SSD are failing.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back