Smalltalk › Squeak › Squeak VM

compiling legacy macos carbon vm

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

2 messages Options

Nicolas Cellier

compiling legacy macos carbon vm

Hi all,

I was wondering about the interest of keeping the platforms/Mac\ OS code.

This code is not alive (not tested, not maintained) and is rotting, slowly but surely.

I did try it, and after a few changes, succeeded in compiling a legacy carbon universal squeak.cog.v3 & squeak.cog.spur

- for a mac os 10.5 (leopard) target (i386 only)

- from a mac os 10.14.6 mojave

- with xcode 10.3 augmented by legacy SDKs thanks to xcode-legacy

https://github.com/devernay/xcodelegacy

- via mvm scripts driving gnu makefiles

installing the legacy SDKs is becoming harder and harder, because Apple now distributes signed xip archives with shortly expiring signatures!

https://github.com/devernay/xcodelegacy/issues/56

But as long as we can sudo date, that's stupid hurdles...

The VM runs in mojave, but it's far from perfect (mouse click does not work, keyboard is OK though). Optimized spur crashes the llvm-gcc-4.2 compiler (../../spursrc/vm/gcc3x-cointerp.c:78381: internal compiler error: Segmentation fault: 11, never mind, I won't send report to Apple!), and with classic gcc-4.2, optimized spur VM crashes at run time soon after startup. Optimized V3 seems to work.

I may publish this work in a branch if ever someone is interested and also retry compilation on a legacy snow leopard machine.

Otherwise, we may as well remove platforms/Mac\ OS entirely.

Thoughts?

johnmci

Re: compiling legacy macos carbon vm

Nicolas, how about you create a legacy folder and move the Mac OS folder there? Although there are many legacy macs about still in use, they don't get upgraded either.

However if someone wants to use such a machine and needs a plugin or VM change can they not just compile the existing source from a commit back in the mid/late 200x era on a machine of that era? For example I have a working 2007 powerbook, it can't really surf the web anymore due to changes in SSL/HTTPS validation.

....

John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Thursday, November 7, 2019 12:44 PM, Nicolas Cellier <[hidden email]> wrote:

Hi all,
I was wondering about the interest of keeping the platforms/Mac\ OS code.
This code is not alive (not tested, not maintained) and is rotting, slowly but surely.
I did try it, and after a few changes, succeeded in compiling a legacy carbon universal squeak.cog.v3 & squeak.cog.spur
- for a mac os 10.5 (leopard) target (i386 only)
- from a mac os 10.14.6 mojave
- with xcode 10.3 augmented by legacy SDKs thanks to xcode-legacy
https://github.com/devernay/xcodelegacy
- via mvm scripts driving gnu makefiles

installing the legacy SDKs is becoming harder and harder, because Apple now distributes signed xip archives with shortly expiring signatures!
https://github.com/devernay/xcodelegacy/issues/56
But as long as we can sudo date, that's stupid hurdles...

The VM runs in mojave, but it's far from perfect (mouse click does not work, keyboard is OK though). Optimized spur crashes the llvm-gcc-4.2 compiler (../../spursrc/vm/gcc3x-cointerp.c:78381: internal compiler error: Segmentation fault: 11, never mind, I won't send report to Apple!), and with classic gcc-4.2, optimized spur VM crashes at run time soon after startup. Optimized V3 seems to work.

I may publish this work in a branch if ever someone is interested and also retry compilation on a legacy snow leopard machine.
Otherwise, we may as well remove platforms/Mac\ OS entirely.
Thoughts?