I recently discovered the pharo launcher. However, it only gives me options to use outdated images, and I'm not sure about the vm. Is there any way to change this?
On Sun, Aug 13, 2017 at 10:31 AM, Vityou . <zlee314@gmail.com> wrote:
I recently discovered the pharo launcher. However, it only gives me options to use outdated images, and I'm not sure about the vm. Is there any way to change this?
Usually it will download the right vm for your image so you don't have to care. -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13
Christophe did a pass because he faced the same problem and he improved the situation. Now he left on vacation (and was stopped because of a huge jenkins crash because he left) and I do not know the status. (because we are also annoyed and sorry than you by the situation). Stef On Sun, Aug 13, 2017 at 10:31 AM, Vityou . <zlee314@gmail.com> wrote:
I recently discovered the pharo launcher. However, it only gives me options to use outdated images, and I'm not sure about the vm. Is there any way to change this?
Hi, I published an update of the Launcher yesterday fixing some issues to run Pharo images from Linux. You can find latest-versions (0.2.13) here: http://files.pharo.org/platform/launcher/ It already propose to download Pharo 70 images. The VM is now downloaded automatically if the adequate one is not available. Let us know if everything is fine. Regards, Christophe ----- Mail original -----
De: "Vityou ." <zlee314@gmail.com> Ã: pharo-users@lists.pharo.org Envoyé: Dimanche 13 Août 2017 10:31:06 Objet: [Pharo-users] (no subject)
I recently discovered the pharo launcher. However, it only gives me options to use outdated images, and I'm not sure about the vm. Is there any way to change this?
On 14-09-17 14:25, Christophe Demarey wrote:
I published an update of the Launcher yesterday fixing some issues to run Pharo images from Linux. You can find latest-versions (0.2.13) here: http://files.pharo.org/platform/launcher/ It already propose to download Pharo 70 images. The VM is now downloaded automatically if the adequate one is not available. Let us know if everything is fine.
- not downloading the sources; - sources now need to be next to the image; - when you upgrade the vm, you need to replace all those sources files - default now dark theme, and not easy to switch - icons only shown on hover (Ubuntu 16.10LTS) Stephan
Hi Stephan,
Le 14 sept. 2017 à 14:49, stephan <stephan@stack.nl> a écrit :
On 14-09-17 14:25, Christophe Demarey wrote:
I published an update of the Launcher yesterday fixing some issues to run Pharo images from Linux. You can find latest-versions (0.2.13) here: http://files.pharo.org/platform/launcher/ It already propose to download Pharo 70 images. The VM is now downloaded automatically if the adequate one is not available. Let us know if everything is fine.
- not downloading the sources;
What do you mean? For Pharo images < 70, sources file for the current version and the previous version are downloaded with the VM.
- sources now need to be next to the image;
For Pharo 7 images, no sources file are dowloaded since they come with the image.
- when you upgrade the vm, you need to replace all those sources files - default now dark theme, and not easy to switch
I think default theme for the Launcher should be the same as the Pharo theme. Would a (Launcher) preference help?
- icons only shown on hover
yes, Pharo 6 regression. I had the problem on other UIs. Will see if I can find a fix quickly.
On Thu, Sep 14, 2017 at 2:25 PM, Christophe Demarey < christophe.demarey@inria.fr> wrote:
Hi,
I published an update of the Launcher yesterday fixing some issues to run Pharo images from Linux. You can find latest-versions (0.2.13) here: http://files.pharo.org/platform/launcher/ It already propose to download Pharo 70 images. The VM is now downloaded automatically if the adequate one is not available. Let us know if everything is fine.
âHi Christophe, thank you for your support on PharoLauncher ! âI dl the last version for Mac OS X: Pharo_0.2.13.dmg This is really nice to be able to download the VM depending on the VM. I have only two issues: - some icons do no show up when PharoLauncher is launch. They only appear when on mouse hover. - for some of my images, I have an error: Instances of UndefinedObject are not indexable. Thank you. -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/
Hi Serge,
Le 14 sept. 2017 à 14:59, Serge Stinckwich <serge.stinckwich@gmail.com> a écrit :
On Thu, Sep 14, 2017 at 2:25 PM, Christophe Demarey <christophe.demarey@inria.fr <mailto:christophe.demarey@inria.fr>> wrote: Hi,
I published an update of the Launcher yesterday fixing some issues to run Pharo images from Linux. You can find latest-versions (0.2.13) here: http://files.pharo.org/platform/launcher/ <http://files.pharo.org/platform/launcher/> It already propose to download Pharo 70 images. The VM is now downloaded automatically if the adequate one is not available. Let us know if everything is fine.
âHi Christophe,
thank you for your support on PharoLauncher ! âI dl the last version for Mac OS X: Pharo_0.2.13.dmg This is really nice to be able to download the VM depending on the VM.
Yes. without that feature, the launcher started to be useless.
I have only two issues: - some icons do no show up when PharoLauncher is launch. They only appear when on mouse hover.
yes, a regression in Pharo 6 :(
- for some of my images, I have an error: Instances of UndefinedObject are not indexable.
Could you send me the stacktrace and / or the images if possible?
On 14-09-17 14:25, Christophe Demarey wrote:
automatically if the adequate one is not available. Let us know if everything is fine.
Because it is not so easy to determine what Pharo7 image version to actually try, I noticed that there is at least one 6521 image that is tried to be opened with a newer (32 bit) vm. Stephan
Thanks christophe this is super cool to see some efforts on that cool tool. Stef On Thu, Sep 14, 2017 at 2:25 PM, Christophe Demarey <christophe.demarey@inria.fr> wrote:
Hi,
I published an update of the Launcher yesterday fixing some issues to run Pharo images from Linux. You can find latest-versions (0.2.13) here: http://files.pharo.org/platform/launcher/ It already propose to download Pharo 70 images. The VM is now downloaded automatically if the adequate one is not available. Let us know if everything is fine.
Regards, Christophe
________________________________
De: "Vityou ." <zlee314@gmail.com> Ã: pharo-users@lists.pharo.org Envoyé: Dimanche 13 Août 2017 10:31:06 Objet: [Pharo-users] (no subject)
I recently discovered the pharo launcher. However, it only gives me options to use outdated images, and I'm not sure about the vm. Is there any way to change this?
demarey wrote
Let us know if everything is fine.
Was this issue [1] fixed:
I think I found it. It seems to be a bug in the way Launcher/Pharo unzips the downloaded VM. The symlink libgit2.dylib becomes unlinked and appears as just a regular file. If I delete the Pharo.app and unzip 70.zip (which btw maybe should have been deleted during cleanup after the dl) to ./vms/70, the error disappears!
[1] From http://forum.world.st/Launcher-Error-w-Pharo-7-tt4959777.html#a4960417 ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
On 17-09-17 05:21, Sean P. DeNigris wrote:
Was this issue [1] fixed:
I think I found it. It seems to be a bug in the way Launcher/Pharo unzips the downloaded VM. The symlink libgit2.dylib becomes unlinked and appears as just a regular file. If I delete the Pharo.app and unzip 70.zip (which btw maybe should have been deleted during cleanup after the dl) to ./vms/70, the error disappears!
[1] From http://forum.world.st/Launcher-Error-w-Pharo-7-tt4959777.html#a4960417
That sounds like the problem I encountered Stephan
Le 17 sept. 2017 à 05:21, Sean P. DeNigris <sean@clipperadams.com> a écrit :
demarey wrote
Let us know if everything is fine.
Was this issue [1] fixed:
I think I found it. It seems to be a bug in the way Launcher/Pharo unzips the downloaded VM. The symlink libgit2.dylib becomes unlinked and appears as just a regular file. If I delete the Pharo.app and unzip 70.zip (which btw maybe should have been deleted during cleanup after the dl) to ./vms/70, the error disappears!
[1] From http://forum.world.st/Launcher-Error-w-Pharo-7-tt4959777.html#a4960417
Not solved. Indeed, it is a problem of the Zip library that does not unzip properly (no preservation of permissions, does not handle symlinks). It is a workaround but maybe I will add a strategy to use the unzip exe if I can find it on the system. That should solve most problems. WDYT?
demarey wrote
It is a workaround but maybe I will add a strategy to use the unzip exe if I can find it on the system. That should solve most problems. WDYT?
Sounds like a reasonable workaround for now. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
On 17/09/17 05:21, Sean P. DeNigris wrote:
demarey wrote
Let us know if everything is fine.
Was this issue [1] fixed:
I think I found it. It seems to be a bug in the way Launcher/Pharo unzips the downloaded VM. The symlink libgit2.dylib becomes unlinked and appears as just a regular file. If I delete the Pharo.app and unzip 70.zip (which btw maybe should have been deleted during cleanup after the dl) to ./vms/70, the error disappears!
With todays bleedingEdge PharoLauncher on mac I was able to download and start 60510. When trying to load GToolKit Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load. I ran into some problem with libgit2 that I could solve by doing the unzipping of the downloaded vm zipfile with the Archive Utility and replacing the vm (and re-adding the sources). Stephan
Le 20 sept. 2017 à 23:36, Stephan Eggermont <stephan@stack.nl> a écrit :
On 17/09/17 05:21, Sean P. DeNigris wrote:
demarey wrote
Let us know if everything is fine. Was this issue [1] fixed: I think I found it. It seems to be a bug in the way Launcher/Pharo unzips the downloaded VM. The symlink libgit2.dylib becomes unlinked and appears as just a regular file. If I delete the Pharo.app and unzip 70.zip (which btw maybe should have been deleted during cleanup after the dl) to ./vms/70, the error disappears!
With todays bleedingEdge PharoLauncher on mac I was able to download and start 60510. When trying to load GToolKit
Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load.
I ran into some problem with libgit2 that I could solve by doing the unzipping of the downloaded vm zipfile with the Archive Utility and replacing the vm (and re-adding the sources).
I tried to reproduce the problem with the same configuration without success. It works well. I guess you already downloaded the required VM with a previous version of the launcher (using Pharo unzipping). If you delete this VM and use the launcher to run the image, it should download the VM and uses your system unzip command to extract it.
On Thu, Sep 14, 2017 at 8:25 PM, Christophe Demarey < christophe.demarey@inria.fr> wrote:
Hi,
I published an update of the Launcher yesterday fixing some issues to run Pharo images from Linux. You can find latest-versions (0.2.13) here: http://files.pharo.org/platform/launcher/ It already propose to download Pharo 70 images. The VM is now downloaded automatically if the adequate one is not available. Let us know if everything is fine.
Thanks Christophe for updating PharoLauncher. I'm trying it with Pharo 7 images for the first time. I hit a problem using Iceberg in downloaded images. $ unzip Pharo-linux-0.2.13.zip $ cd pharo $ unzip ../PharoLauncher-user-stable-2017.09.14.zip $ ./pharo + PharoLauncher > Settings > Enable development environment + World > Tools > Iceberg ==> iceberg opens okay + PharoLauncher > Templates > Pharo 7.0(beta) > latest-32 <Create Image> '7latest32' + '7latest32' <Launch> + World > Tools > Iceberg ==> "Error: EXternal module not found" $ uname -a ==> Linux 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) i686 GNU/Linux cheers -ben
On Wed, Sep 20, 2017 at 1:12 PM, Ben Coman <btc@openinworld.com> wrote:
On Thu, Sep 14, 2017 at 8:25 PM, Christophe Demarey < christophe.demarey@inria.fr> wrote:
Hi,
I published an update of the Launcher yesterday fixing some issues to run Pharo images from Linux. You can find latest-versions (0.2.13) here: http://files.pharo.org/platform/launcher/ It already propose to download Pharo 70 images. The VM is now downloaded automatically if the adequate one is not available. Let us know if everything is fine.
Thanks Christophe for updating PharoLauncher. I'm trying it with Pharo 7 images for the first time. I hit a problem using Iceberg in downloaded images.
$ unzip Pharo-linux-0.2.13.zip $ cd pharo $ unzip ../PharoLauncher-user-stable-2017.09.14.zip $ ./pharo + PharoLauncher > Settings > Enable development environment + World > Tools > Iceberg ==> iceberg opens okay + PharoLauncher > Templates > Pharo 7.0(beta) > latest-32 <Create Image> '7latest32' + '7latest32' <Launch> + World > Tools > Iceberg ==> "Error: EXternal module not found"
$ uname -a ==> Linux 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) i686 GNU/Linux
but this works okay... $ curl get.pharo.org/70+vm | bash $ ./pharo-ui + World > Tools > Iceberg ==> iceberg opens okay while this PharoLauncher alternative fails... $ curl get.pharo.org | bash $ ./pharo-ui + World > Tools > Catalog > PharoLauncher <Install stable configuration> + World > PharoLauncher ==> Doesn't show Pharo 7 templates + World > Monticello > ...PharoLauncher/main <Open Repository> + ConfigurationOfPharoLauncher-ChristopheDemarey.56 <Load> + World > Playground > "ConfigurationOfPharoLauncher load" <DoIt> + World > PharoLauncher > Settings > Hard reset persistant state ==> Pharo 7 templates showing + '7latest32' <Launch> "i.e. the previously downloaded image" + World > Tools > Iceberg ==> "Error: External module not found" + World > Monticello... load latest mczs... * PharoLauncher-Core-ChristopheDemarey.123 * PharoLauncher-Spec-ChristopheDemarey.51 + '7latest32' <Launch> "i.e. the previously downloaded image" ==> "Fetching VM to run Pharo 70 images" + World > Tools > Iceberg ==> "Error: External module not found" Version comparison... direct get.pharo.org/70+vm /home/ben/Pharo/adhoc/Pharo7/Pharo.image Pharo7.0alpha.build.132.sha.4ea2f39a9f43185d31b844be5ad33b677f43bf17 /home/ben/Pharo/adhoc/Pharo7/pharo-vm/lib/pharo/5.0-201708271955/pharo CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 via PharoLauncher... /home/ben/Pharo/images/7latest32/7latest32.image Pharo7.0alpha.build.132.sha.4ea2f39a9f43185d31b844be5ad33b677f43bf17 /home/ben/Pharo/vms/70-x86/lib/pharo/5.0-201708271955/pharo CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 Must be something environmental in lookup paths. Can you reproduce or suggest further investigation I can do? cheers -ben
On 20-09-17 08:26, Ben Coman wrote:
Must be something environmental in lookup paths. Can you reproduce or suggest further investigation I can do?
If I understand it correctly it is a problem with the unzipping. Not handling symlinks and preserving permissions. Is that a plugin problem? Stephan
Hi Sean, Stephan, I just updated the PharoLauncher and it should now work fine for 64-bits images. I just had time to test it roughly but you can give it a try (https://ci.inria.fr/pharo/view/Launcher/job/Launcher/149/). Christophe.
Le 20 sept. 2017 à 10:52, stephan <stephan@stack.nl> a écrit :
On 20-09-17 08:26, Ben Coman wrote:
Must be something environmental in lookup paths. Can you reproduce or suggest further investigation I can do?
If I understand it correctly it is a problem with the unzipping. Not handling symlinks and preserving permissions. Is that a plugin problem?
Stephan
On 20/09/17 12:17, Christophe Demarey wrote:
I just updated the PharoLauncher and it should now work fine for 64-bits images. I just had time to test it roughly but you can give it a try (https://ci.inria.fr/pharo/view/Launcher/job/Launcher/149/).
Pharo7 64 bit starts fine on Mac. Good work. Stephan
Christophe which version should we take? Stef On Wed, Sep 20, 2017 at 12:17 PM, Christophe Demarey <christophe.demarey@inria.fr> wrote:
Hi Sean, Stephan,
I just updated the PharoLauncher and it should now work fine for 64-bits images. I just had time to test it roughly but you can give it a try (https://ci.inria.fr/pharo/view/Launcher/job/Launcher/149/).
Christophe.
Le 20 sept. 2017 à 10:52, stephan <stephan@stack.nl> a écrit :
On 20-09-17 08:26, Ben Coman wrote:
Must be something environmental in lookup paths. Can you reproduce or suggest further investigation I can do?
If I understand it correctly it is a problem with the unzipping. Not handling symlinks and preserving permissions. Is that a plugin problem?
Stephan
Hi Ben, Could you test it with the bleedingEdge version of the launcher to see if the problem is solved? Thanks, Christophe.
Le 20 sept. 2017 à 08:26, Ben Coman <btc@openinworld.com> a écrit :
On Wed, Sep 20, 2017 at 1:12 PM, Ben Coman <btc@openinworld.com <mailto:btc@openinworld.com>> wrote: On Thu, Sep 14, 2017 at 8:25 PM, Christophe Demarey <christophe.demarey@inria.fr <mailto:christophe.demarey@inria.fr>> wrote:
Hi,
I published an update of the Launcher yesterday fixing some issues to run Pharo images from Linux. You can find latest-versions (0.2.13) here: http://files.pharo.org/platform/launcher/ <http://files.pharo.org/platform/launcher/> It already propose to download Pharo 70 images. The VM is now downloaded automatically if the adequate one is not available. Let us know if everything is fine.
Thanks Christophe for updating PharoLauncher. I'm trying it with Pharo 7 images for the first time. I hit a problem using Iceberg in downloaded images.
$ unzip Pharo-linux-0.2.13.zip $ cd pharo $ unzip ../PharoLauncher-user-stable-2017.09.14.zip $ ./pharo + PharoLauncher > Settings > Enable development environment + World > Tools > Iceberg ==> iceberg opens okay + PharoLauncher > Templates > Pharo 7.0(beta) > latest-32 <Create Image> '7latest32' + '7latest32' <Launch> + World > Tools > Iceberg ==> "Error: EXternal module not found"
$ uname -a ==> Linux 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) i686 GNU/Linux
but this works okay... $ curl get.pharo.org/70+vm <http://get.pharo.org/70+vm> | bash $ ./pharo-ui + World > Tools > Iceberg ==> iceberg opens okay
while this PharoLauncher alternative fails... $ curl get.pharo.org <http://get.pharo.org/> | bash $ ./pharo-ui + World > Tools > Catalog > PharoLauncher <Install stable configuration> + World > PharoLauncher ==> Doesn't show Pharo 7 templates + World > Monticello > ...PharoLauncher/main <Open Repository> + ConfigurationOfPharoLauncher-ChristopheDemarey.56 <Load> + World > Playground > "ConfigurationOfPharoLauncher load" <DoIt> + World > PharoLauncher > Settings > Hard reset persistant state ==> Pharo 7 templates showing + '7latest32' <Launch> "i.e. the previously downloaded image" + World > Tools > Iceberg ==> "Error: External module not found"
+ World > Monticello... load latest mczs... * PharoLauncher-Core-ChristopheDemarey.123 * PharoLauncher-Spec-ChristopheDemarey.51 + '7latest32' <Launch> "i.e. the previously downloaded image" ==> "Fetching VM to run Pharo 70 images" + World > Tools > Iceberg ==> "Error: External module not found"
Version comparison...
direct get.pharo.org/70+vm <http://get.pharo.org/70+vm> /home/ben/Pharo/adhoc/Pharo7/Pharo.image Pharo7.0alpha.build.132.sha.4ea2f39a9f43185d31b844be5ad33b677f43bf17 /home/ben/Pharo/adhoc/Pharo7/pharo-vm/lib/pharo/5.0-201708271955/pharo CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017
via PharoLauncher... /home/ben/Pharo/images/7latest32/7latest32.image Pharo7.0alpha.build.132.sha.4ea2f39a9f43185d31b844be5ad33b677f43bf17 /home/ben/Pharo/vms/70-x86/lib/pharo/5.0-201708271955/pharo CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017
Must be something environmental in lookup paths. Can you reproduce or suggest further investigation I can do?
cheers -ben
Could you clarify where to download from? I tried PharoLauncher-user-bleedingEdge-2017.09.20.zip from... https://ci.inria.fr/pharo/view/Launcher/job/Launcher/149/PHARO=61,VERSION=bl... with the Pharo-linux-0.2.13.zip I previously downloaded (limited time before bed) cheers -ben On Thu, Sep 21, 2017 at 9:45 PM, Christophe Demarey < christophe.demarey@inria.fr> wrote:
Hi Ben,
Could you test it with the bleedingEdge version of the launcher to see if the problem is solved?
Thanks, Christophe.
Le 20 sept. 2017 à 08:26, Ben Coman <btc@openinworld.com> a écrit :
On Wed, Sep 20, 2017 at 1:12 PM, Ben Coman <btc@openinworld.com> wrote:
On Thu, Sep 14, 2017 at 8:25 PM, Christophe Demarey < christophe.demarey@inria.fr> wrote:
Hi,
I published an update of the Launcher yesterday fixing some issues to run Pharo images from Linux. You can find latest-versions (0.2.13) here: http://files.pharo.org/platform/launcher/ It already propose to download Pharo 70 images. The VM is now downloaded automatically if the adequate one is not available. Let us know if everything is fine.
Thanks Christophe for updating PharoLauncher. I'm trying it with Pharo 7 images for the first time. I hit a problem using Iceberg in downloaded images.
$ unzip Pharo-linux-0.2.13.zip $ cd pharo $ unzip ../PharoLauncher-user-stable-2017.09.14.zip $ ./pharo + PharoLauncher > Settings > Enable development environment + World > Tools > Iceberg ==> iceberg opens okay + PharoLauncher > Templates > Pharo 7.0(beta) > latest-32 <Create Image> '7latest32' + '7latest32' <Launch> + World > Tools > Iceberg ==> "Error: EXternal module not found"
$ uname -a ==> Linux 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) i686 GNU/Linux
but this works okay... $ curl get.pharo.org/70+vm | bash $ ./pharo-ui + World > Tools > Iceberg ==> iceberg opens okay
while this PharoLauncher alternative fails... $ curl get.pharo.org | bash $ ./pharo-ui + World > Tools > Catalog > PharoLauncher <Install stable configuration> + World > PharoLauncher ==> Doesn't show Pharo 7 templates + World > Monticello > ...PharoLauncher/main <Open Repository> + ConfigurationOfPharoLauncher-ChristopheDemarey.56 <Load> + World > Playground > "ConfigurationOfPharoLauncher load" <DoIt> + World > PharoLauncher > Settings > Hard reset persistant state ==> Pharo 7 templates showing + '7latest32' <Launch> "i.e. the previously downloaded image" + World > Tools > Iceberg ==> "Error: External module not found"
+ World > Monticello... load latest mczs... * PharoLauncher-Core-ChristopheDemarey.123 * PharoLauncher-Spec-ChristopheDemarey.51 + '7latest32' <Launch> "i.e. the previously downloaded image" ==> "Fetching VM to run Pharo 70 images" + World > Tools > Iceberg ==> "Error: External module not found"
Version comparison...
direct get.pharo.org/70+vm /home/ben/Pharo/adhoc/Pharo7/Pharo.image Pharo7.0alpha.build.132.sha.4ea2f39a9f43185d31b844be5ad33b677f43bf17 /home/ben/Pharo/adhoc/Pharo7/pharo-vm/lib/pharo/5.0-201708271955/pharo CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017
via PharoLauncher... /home/ben/Pharo/images/7latest32/7latest32.image Pharo7.0alpha.build.132.sha.4ea2f39a9f43185d31b844be5ad33b677f43bf17 /home/ben/Pharo/vms/70-x86/lib/pharo/5.0-201708271955/pharo CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017
Must be something environmental in lookup paths. Can you reproduce or suggest further investigation I can do?
cheers -ben
participants (9)
-
Ben Coman -
Christophe Demarey -
Guillermo Polito -
Sean P. DeNigris -
Serge Stinckwich -
stephan -
Stephan Eggermont
-
Stephane Ducasse -
Vityou .