[squeak-dev] #installExtraPackages - fails on new install

tim Rowledge tim at rowledge.org
Mon Oct 26 17:33:37 UTC 2020



> On 2020-10-26, at 9:59 AM, John-Reed Maffeo <jrmaffeo at gmail.com> wrote:
> 
> I tried to update the image to see if that would help and a got a seg fault.
> 
> "Segmentation fault Mon Oct 26 09:36:22 2020
> 
> /usr/lib/squeak/5.0-201610101924/squeak
> Squeak VM version: 5.0-201610101924  Wed Oct 12 14:50:05 PDT 2016 gcc 4.9.2 [Production Spur VM]
> Built from: CoInterpreter VMMaker.oscog-eem.1950 uuid: b4089b49-1494-49d2-8966-57cba5c92194 Oct 12 2016
> With: StackToRegisterMappingCogit VMMaker.oscog-eem.1950 uuid: b4089b49-1494-49d2-8966-57cba5c92194 Oct 12 2016
> Revision: VM: 201610101924 tim at Diziet.local:Documents/Squeak/Rasbian-VM/vm $ Date: Mon Oct 10 12:24:25 2016 -0700 $ Plugins: 201610101924 tim at Diziet.local:Documents/Squeak/Rasbian-VM/vm $
> Build host: Linux Goldskin 4.4.21-v7+ #911 SMP Thu Sep 15 14:22:38 BST 2016 armv7l GNU/Linux
> plugin path: /usr/lib/squeak/5.0-201610101924 [default: /usr/lib/squeak/5.0-201610101924/]"

OK, it looks like you somehow ended up running a *very* old VM that I built (in 2016!) for the NuScratch install in Raspbian. That might explain this.

This is actually an artefact of the completely broken way we are bundling and installing linux VM packages, exposded by the Pi having an already installed VM in the 'proper' place but the package you downloaded relying on a VM in a completely different place!

There's a bunch of different ways to fix this, many of them far more unix-expert than I can handle.  The simplest I can think of *for Raspbian* is to edit the file properties of an image file to pint to the newer vm.

Start by opening the file browser and finding an image file. Select it and r-click->Properties. In that dialog you should see (about halfway down) 'open with' and a pulldown menu. At the bottom of that should be 'Customize' - click on that. 

Next comes a 'Choose Application' dialog and you could slelct from a wide variety of incorrect choices. Do not click on 'Games->Minecraft Pi' and try running Squeak in Minecraft. It only leads to Fear, and Fear leads to Eating Too Many Biscuits.

Instead, click on the 'Custom Command Line' tab. Now you see a way to enter an actual command line (duh!). I always use the 'Browse...' button to open a file finder, locate the 'Squeak' shell script and choose that. The shell script will be in some fairly deeply buried directory within the package you downloaded.

Once you have found it and selected it and clicked on the 'OK' button in the file finder the path will appear back in the 'Choose Application' dialog. Almost done!

Now in that 'Command line to execute:' text field, add %f at the end (with a space after the final bit of the filename!) so that the name of the image file you click on will be passed to the squeak shell script. I always put sometihng hopefully helpful in the 'Application name' text field as well. Finally, click on the OK button.

One last step I almost always have to do is to to set the permissions of the image file(s) to have 'nobody' for the 'Execute:' permission. No idea why.

With all that done, you should find that a d-click on the image file will run the latest VM for you.

Like I said, broken.

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Programming is an art form that fights back.




More information about the Squeak-dev mailing list