I gave up working on this issue back in September because I had other things to do, but never resolved it â unless you call screen-sharing to another machine that does continue to run Pharo a "solution" As far as I can see, the problem is that my Pharo VM can't find the primitives that allow it to access the file system. This means that nothing that requires file system access â including getting the sources â will work. Of course, this makes no sense, because Iceberg had just loaded my code from the file system ... but perhaps using a different mechanism? I did try your suggestion to get a more stable Pharo:
$ curl https://get.pharo.org/64 | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 237 100 237 0 0 49 0 0:00:04 0:00:04 --:--:-- 52 bash: line 1: syntax error near unexpected token `newline' bash: line 1: ` < !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN" > ' $
Then I tried
$ curl https://get.pharo.org/64/stable | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 3260 100 3260 0 0 4234 0 --:--:-- --:--:-- --:--:-- 4239 Downloading the latest 70 Image: http://files.pharo.org/get-files/70/pharo64.zip Pharo.image $
which created Pharo.changes, Pharo.image, and Pharo7.0-32bit-ccd1f64.sources in the current directory. Presumably, it also put the 64-bit VM somewhere, but I don't know where. If I just do
$ open Pharo.image
Pharo runs, and so does Iceberg, but the image that it's running is my broken Pharo launcher image, not the new one that was just downloaded, and the VM running it is a 32-bit VM, because MacOS warns me that it is out of date, and that it won't keep working for much longer. So clearly Zeroconf is not, and I have issues with broken bits of old Pharos on this particular computer, but I'm no closer to figuring out how to actually run Pharo again. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html