[Vm-dev] CRC fix input (David T. Lewis)

David T. Lewis lewis at mail.msen.com
Mon Jul 25 22:48:03 UTC 2022


Hi Ken,

On Mon, Jul 25, 2022 at 06:36:23AM -0700, ken.dickey at whidbey.com wrote:
>  
> Dave,
> 
> Many thanks for the explanations.
> 
> At this point I am using the image scripts to generate a VMMaker image, 
> which on RasPi4 Linux gets close and dies, but I am able to run the 
> CoInterp init methods and generate code.
> 
> One wrinkle with the Squeak 6 version is that attempting to open a repo 
> in the Monticello Browser (e.g. VMMakerInbox) generates "Error: 
> primitiveSSLCreate failed".

I recognize this error, it's actually a Linux distro issue that is
difficult to work around for precompiled binaries such as the VM.

I am currently running an out of date Ubuntu 16.04 LTS distribution,
and for me the new VM distributed with Squeak 6.0 is not able to
find a dynamic library required by the SSL plugin, hence the failure
to initialize an https session. For me the console error looks like
this:

$ ./squeak.sh
Using /home/lewis/squeak/Squeak6.0/Squeak6.0-22104-64bit-202206021410-Linux-x64/bin/squeak ...
SqueakSSL tryLoading /home/lewis/squeak/Squeak6.0/Squeak6.0-22104-64bit-202206021410-Linux-x64/bin/SqueakSSL.so: dlopen: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not found (required by /home/lewis/squeak/Squeak6.0/Squeak6.0-22104-64bit-202206021410-Linux-x64/bin/SqueakSSL.so)

Obviously I need to update my operating system, but in the mean
time the workaround that I use is either of these two things:

1) Use an up to date VM that I have compiled and installed locally.

2) Copy an SqueakSSL.so plugin file from a working VM into the
folder for the VM that is not working.

Usually I am doing #1, but if you are building the VMMaker image
using Eliot's scripts, you can find an older SqueakSSL.so file
and copy it into the folder for whatever VM the scripts have
downloaded. Any SSL plugin that you have compiled locally should
be fine, or you can copy one from some earlier VM distribution
(such as the VM that was packaged with Squeak 5.3 for example).

You can also specify your own VM as a command line option for
the various VMMaker scripts. In any case, the solution is to
use a precompiled SqueakSSL.so from a different VM build.

Dave



More information about the Vm-dev mailing list