No more support for running 64-bit VM on macOS < 10.13?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

No more support for running 64-bit VM on macOS < 10.13?

Tim Johnson-2
 
Hi,

Is running the 64-bit VM now unsupported on anything less than macOS
(nee OS X) 10.13 or 10.14?  Perhaps because of the Metal changes and
OpenGL deprecation...?

I just compiled the 64-bit VM[1] fresh and tried running it on my
10.12.6 system.  I got a Squeak window with no graphics inside (just
blackness) and a message on my terminal console:

2019-03-21 10:58:55.324 Squeak[70669:4778174] Pipeline state creation
error: Function screenQuadFragmentShader is using language version 2.1
which is incompatible with this OS.

If so, I may need to make a choice between:

- upgrading my operating system,
- using the 32-bit VM (though my image is 64-bit),
- staying on an older VM version (though I leave it running for many
days and its memory usage balloons from ~313 megabytes to multiple
gigabytes, perhaps due to the event handling memory leak bug, which I
was hoping to leave behind).

I wonder if it would be worth the effort to handle this situation
gracefully rather than bringing up a non-functioning environment which
requires a force-quit.  Perhaps this could be easily accomplished by
including the proper minimum OS version in the Info.plist of the 64-bit
app bundle and letting macOS do the work of disallowing a launch on
older OS versions.

Thanks,
Tim J



[1] build.macos64x64/squeak.cog.spur
Reply | Threaded
Open this post in threaded view
|

Re: No more support for running 64-bit VM on macOS < 10.13?

Eliot Miranda-2
 
Hi Tim,

On Thu, Mar 21, 2019 at 11:18 AM Tim Johnson <[hidden email]> wrote:
 
Hi,

Is running the 64-bit VM now unsupported on anything less than macOS
(nee OS X) 10.13 or 10.14?  Perhaps because of the Metal changes and
OpenGL deprecation...?

I just compiled the 64-bit VM[1] fresh and tried running it on my
10.12.6 system.  I got a Squeak window with no graphics inside (just
blackness) and a message on my terminal console:

2019-03-21 10:58:55.324 Squeak[70669:4778174] Pipeline state creation
error: Function screenQuadFragmentShader is using language version 2.1
which is incompatible with this OS.

My understanding is that this is a temporary situation, the result of Ronie having made an initial Metal implementation which needs to be revised to account for earlier versions.  The tip no longer runs on 10.13.  i hope that Ronie can solve this, or that I (we?) can work with Ronie to address this serious p[roblem quickly.
 

If so, I may need to make a choice between:

- upgrading my operating system,
- using the 32-bit VM (though my image is 64-bit),
- staying on an older VM version (though I leave it running for many
days and its memory usage balloons from ~313 megabytes to multiple
gigabytes, perhaps due to the event handling memory leak bug, which I
was hoping to leave behind).

I wonder if it would be worth the effort to handle this situation
gracefully rather than bringing up a non-functioning environment which
requires a force-quit.  Perhaps this could be easily accomplished by
including the proper minimum OS version in the Info.plist of the 64-bit
app bundle and letting macOS do the work of disallowing a launch on
older OS versions.

Thanks,
Tim J



[1] build.macos64x64/squeak.cog.spur


--
_,,,^..^,,,_
best, Eliot
Reply | Threaded
Open this post in threaded view
|

Re: No more support for running 64-bit VM on macOS < 10.13?

Ronie Salgado
 
Hi,

Give me until sunday for refactoring this and supporting the Metal backend, and the old OpenGL backend. I think that it should be possible to select the actual kind of view based on what is available(MTLDevice can be null if not supported), or by providing a command line option in the worst case.

Best regards,
Ronie

El jue., 21 mar. 2019 a las 16:48, Eliot Miranda (<[hidden email]>) escribió:
 
Hi Tim,

On Thu, Mar 21, 2019 at 11:18 AM Tim Johnson <[hidden email]> wrote:
 
Hi,

Is running the 64-bit VM now unsupported on anything less than macOS
(nee OS X) 10.13 or 10.14?  Perhaps because of the Metal changes and
OpenGL deprecation...?

I just compiled the 64-bit VM[1] fresh and tried running it on my
10.12.6 system.  I got a Squeak window with no graphics inside (just
blackness) and a message on my terminal console:

2019-03-21 10:58:55.324 Squeak[70669:4778174] Pipeline state creation
error: Function screenQuadFragmentShader is using language version 2.1
which is incompatible with this OS.

My understanding is that this is a temporary situation, the result of Ronie having made an initial Metal implementation which needs to be revised to account for earlier versions.  The tip no longer runs on 10.13.  i hope that Ronie can solve this, or that I (we?) can work with Ronie to address this serious p[roblem quickly.
 

If so, I may need to make a choice between:

- upgrading my operating system,
- using the 32-bit VM (though my image is 64-bit),
- staying on an older VM version (though I leave it running for many
days and its memory usage balloons from ~313 megabytes to multiple
gigabytes, perhaps due to the event handling memory leak bug, which I
was hoping to leave behind).

I wonder if it would be worth the effort to handle this situation
gracefully rather than bringing up a non-functioning environment which
requires a force-quit.  Perhaps this could be easily accomplished by
including the proper minimum OS version in the Info.plist of the 64-bit
app bundle and letting macOS do the work of disallowing a launch on
older OS versions.

Thanks,
Tim J



[1] build.macos64x64/squeak.cog.spur


--
_,,,^..^,,,_
best, Eliot
Reply | Threaded
Open this post in threaded view
|

Re: No more support for running 64-bit VM on macOS < 10.13?

Eliot Miranda-2
 


On Mar 21, 2019, at 3:11 PM, Ronie Salgado <[hidden email]> wrote:

Hi,

Give me until sunday for refactoring this and supporting the Metal backend, and the old OpenGL backend. I think that it should be possible to select the actual kind of view based on what is available(MTLDevice can be null if not supported), or by providing a command line option in the worst case.

Thanks Ronie!  Take the time you need; don’t wreck your weekend.  I for one am really thankful for this great work.  LMK if I can help test.  I have a 10.13 and IIRC a 10.12 system I can test with.


Best regards,
Ronie

El jue., 21 mar. 2019 a las 16:48, Eliot Miranda (<[hidden email]>) escribió:
 
Hi Tim,

On Thu, Mar 21, 2019 at 11:18 AM Tim Johnson <[hidden email]> wrote:
 
Hi,

Is running the 64-bit VM now unsupported on anything less than macOS
(nee OS X) 10.13 or 10.14?  Perhaps because of the Metal changes and
OpenGL deprecation...?

I just compiled the 64-bit VM[1] fresh and tried running it on my
10.12.6 system.  I got a Squeak window with no graphics inside (just
blackness) and a message on my terminal console:

2019-03-21 10:58:55.324 Squeak[70669:4778174] Pipeline state creation
error: Function screenQuadFragmentShader is using language version 2.1
which is incompatible with this OS.

My understanding is that this is a temporary situation, the result of Ronie having made an initial Metal implementation which needs to be revised to account for earlier versions.  The tip no longer runs on 10.13.  i hope that Ronie can solve this, or that I (we?) can work with Ronie to address this serious p[roblem quickly.
 

If so, I may need to make a choice between:

- upgrading my operating system,
- using the 32-bit VM (though my image is 64-bit),
- staying on an older VM version (though I leave it running for many
days and its memory usage balloons from ~313 megabytes to multiple
gigabytes, perhaps due to the event handling memory leak bug, which I
was hoping to leave behind).

I wonder if it would be worth the effort to handle this situation
gracefully rather than bringing up a non-functioning environment which
requires a force-quit.  Perhaps this could be easily accomplished by
including the proper minimum OS version in the Info.plist of the 64-bit
app bundle and letting macOS do the work of disallowing a launch on
older OS versions.

Thanks,
Tim J



[1] build.macos64x64/squeak.cog.spur


--
_,,,^..^,,,_
best, Eliot
Reply | Threaded
Open this post in threaded view
|

Re: No more support for running 64-bit VM on macOS < 10.13?

Tim Johnson-2
 

On Mar 21, 2019, at 5:43 PM, Eliot Miranda <[hidden email]> wrote:



On Mar 21, 2019, at 3:11 PM, Ronie Salgado <[hidden email]> wrote:

Hi,

Give me until sunday for refactoring this and supporting the Metal backend, and the old OpenGL backend. I think that it should be possible to select the actual kind of view based on what is available(MTLDevice can be null if not supported), or by providing a command line option in the worst case.

Thanks Ronie!  Take the time you need; don’t wreck your weekend.  I for one am really thankful for this great work.  LMK if I can help test.  I have a 10.13 and IIRC a 10.12 system I can test with.

+1

I also have a 10.11 machine for testing, though I don't know if that would be needed.

Thanks,
Tim


Reply | Threaded
Open this post in threaded view
|

Re: No more support for running 64-bit VM on macOS < 10.13?

Ronie Salgado
 
Hi,

With this PR: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/382 I am now compiling the shaders from source in runtime, and trying to compile the shader library before creating the Metal view. In addition to this, I added the following command line options:

-opengl Select the OpenGL view
-metal Select the Metal view
-core-graphics Select the Core graphics view.

Because command line parsing is done after creating the view, I had to add a hack specific for this options in main() function. So these options only work when used as the first command line option. In addition to these option, if -headless is used as the first command line option, then a view that does not render or handle events will be selected instead.

Best regards,
Ronie

El sáb., 23 mar. 2019 a las 13:20, Tim Johnson (<[hidden email]>) escribió:
 

On Mar 21, 2019, at 5:43 PM, Eliot Miranda <[hidden email]> wrote:



On Mar 21, 2019, at 3:11 PM, Ronie Salgado <[hidden email]> wrote:

Hi,

Give me until sunday for refactoring this and supporting the Metal backend, and the old OpenGL backend. I think that it should be possible to select the actual kind of view based on what is available(MTLDevice can be null if not supported), or by providing a command line option in the worst case.

Thanks Ronie!  Take the time you need; don’t wreck your weekend.  I for one am really thankful for this great work.  LMK if I can help test.  I have a 10.13 and IIRC a 10.12 system I can test with.

+1

I also have a 10.11 machine for testing, though I don't know if that would be needed.

Thanks,
Tim