[Vm-dev] How to run a Mac Interpreter VM without sound?
frank.shearar at gmail.com
Mon Sep 8 19:43:44 UTC 2014
I am using a Unix VM on a Mac. I guess that's not the right thing to
do, despite OS X being a Unix-like system? I don't care about visuals
or audio: I'm only interested in interacting with the image through
stdout/stdin so had thought that wouldn't be a problem.
I can _build_ the VM just fine. I just can't _run_ it, because
squeak.sh demands a sound driver, and I don't know why it can't find
one of the many that were built.
On 8 September 2014 15:30, David T. Lewis <lewis at mail.msen.com> wrote:
> It sounds like you are compiling a Unix VM on Mac. I can't tell if this is
> a build problem or a runtime problem. Does the official VM from
> http://squeakvm.org/unix/ work on your build slave machine?
>> The OS X (10.8.0) build slave I use for CI fails to run any
>> interpreter-vm-using commands because of sound issues. If I use the
>> arguments "-vm-display-null" it says
>> squeak: could not find any sound driver
>> and aborts.
>> If I use the arguments "-vm-display-null -vm-sound-null" it says
>> could not find module vm-sound-null
>> and aborts.
>> This is a VM that's freshly baked, from the standard
>> download-configure-make dance. An ls in the bld/ directory shows a
>> wealth of sound plugins: vm-sound-null, vm-sound-MacOSX, and so on.
>> Using any of these plugins fails, all because the VM "could not find
>> module vm-sound-FOO".
>> -help says
>> Available drivers:
>> and you'll note the absence of any sound drivers there. The sad thing
>> is I don't even _care_ about sound. The machine runs CI jobs only. If
>> I could do without random Beep sounds, I'd be even happier.
>> So how do I find out what incantation I need to chant while
>> sacrificing the chicken, if I want to run an Interpreter VM on OSX?
More information about the Vm-dev