Hi Folks, I've installed pharo-vm and pharo-launcher from AUR as stated in the pharo site. Everything works fine for Pharo 4. But when I try to load a Pharo 5 image I get the following error: This interpreter (vers. 6502) cannot read file image (vers. 6521) and when I do pharo --version: 3.9-7 #1 Thu Dec 17 00:38:38 CET 2015 gcc 4.6.3 [Production ITHB VM] NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Dec 17 2015 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Dec 17 2015 https://github.com/pharo-project/pharo-vm.git Commit: bad6fa2684afcf1d7cdb485f11049a4a4290fbc8 Date: 2015-12-14 12:47:06 +0100 By: Esteban Lorenzano <estebanlm@gmail.com> Jenkins build #15024 Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux plugin path: /usr/share/pharo-vm/ [default: /usr/share/pharo-vm/] Any clues? Thanks in advance Nacho ----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/VM-error-in-Arch-Linux-tp4868239.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
I guess that that image is a Spur one, requiring a Spur VM. Phil On Tue, Dec 22, 2015 at 11:14 AM, nacho <0800nacho@gmail.com> wrote:
Hi Folks, I've installed pharo-vm and pharo-launcher from AUR as stated in the pharo site. Everything works fine for Pharo 4. But when I try to load a Pharo 5 image I get the following error: This interpreter (vers. 6502) cannot read file image (vers. 6521)
and when I do pharo --version: 3.9-7 #1 Thu Dec 17 00:38:38 CET 2015 gcc 4.6.3 [Production ITHB VM] NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Dec 17 2015 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Dec 17 2015 https://github.com/pharo-project/pharo-vm.git Commit: bad6fa2684afcf1d7cdb485f11049a4a4290fbc8 Date: 2015-12-14 12:47:06 +0100 By: Esteban Lorenzano <estebanlm@gmail.com> Jenkins build #15024 Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux plugin path: /usr/share/pharo-vm/ [default: /usr/share/pharo-vm/]
Any clues?
Thanks in advance Nacho
----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/VM-error-in-Arch-Linux-tp4868239.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Le 22/12/2015 11:14, nacho a écrit :
Hi Folks, I've installed pharo-vm and pharo-launcher from AUR as stated in the pharo site. Everything works fine for Pharo 4. But when I try to load a Pharo 5 image I get the following error: This interpreter (vers. 6502) cannot read file image (vers. 6521)
and when I do pharo --version: 3.9-7 #1 Thu Dec 17 00:38:38 CET 2015 gcc 4.6.3 [Production ITHB VM] NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Dec 17 2015 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Dec 17 2015 https://github.com/pharo-project/pharo-vm.git Commit: bad6fa2684afcf1d7cdb485f11049a4a4290fbc8 Date: 2015-12-14 12:47:06 +0100 By: Esteban Lorenzano <estebanlm@gmail.com> Jenkins build #15024 Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux plugin path: /usr/share/pharo-vm/ [default: /usr/share/pharo-vm/]
Any clues?
Hi, Since last week a new VM is use for Pharo 5 beta. You need to download the new VM on http://files.pharo.org/vm/pharo-spur32/. Then you need to update Pharo Launcher. For now the easiest way I think is to enable the development mode in PharoLauncher, go in Monticello, and load the last version of Pharo Launcher core. Later I think that a new release of Pharo Launcher will make thing easier. Then you can disable the development mode and do Alt + Shift + S to save you image. After this everything should be fine.
Thanks in advance Nacho
----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/VM-error-in-Arch-Linux-tp4868239.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France
On Uto, 2015-12-22 at 11:56 +0100, Ferlicot D. Cyril wrote:
Since last week a new VM is use for Pharo 5 beta.
Beginning Pharo user here...I had the same problem on my Debian box: "This interpreter (vers. 6505) cannot read image file (vers. 6521)."
You need to download the new VM on http://files.pharo.org/vm/pharo-spu r32/.
Then I downloaded the new VM image and tried to use it with latest Pharo Launcher ('Bleeding Edge'), but now I get: "This interpreter (vers. 6521) cannot read image file (vers. 6505)."Â which is kind of catch-22 situation...
Then you need to update Pharo Launcher.
...and it looks that I do not have updated Pharo Launcher.
For now the easiest way I think is to enable the development mode in PharoLauncher, go in Monticello, and load the last version of Pharo Launcher core.
Tried that as well, but didn't work.
Later I think that a new release of Pharo Launcher will make thing easier.
Let me say that the potential of Pharo Launcher is really great - it allows (if I got it right) to have many development machines available via different VMs, while still keeping developer's machine in sane state which cannot be said when one does regular development with other (mostly compiled) languages, which is "simply wonderful!". Now I wonder if you can provide any further hint how to resolve the above? Is there a plan that in the future Pharo Launcher will become regular part of 'normal' Pharo image? I know that probably there would be more luch with V4.0, but I simply would like to try latest code eagerly anticipating the day to try 64bit VM. Still, kudos to all Pharo devs for providing human development environment in the days when things are going insane all around us. Sincerely, Gour -- As a lamp in a windless place does not waver, so the transcendentalist, whose mind is controlled, remains always steady in his meditation on the transcendent self.
Is there a plan that in the future Pharo Launcher will become regular part of 'normal' Pharo image? I know that probably there would be more luch with V4.0, but I simply would like to try latest code eagerly anticipating the day to try 64bit VM. Still, kudos to all Pharo devs for providing human development environment in the days when things are going insane all around us. Sincerely, Gour We plan to develop a new version of Launcher with Brick. Now we will make sure that it works with Pharo 50. Stef
There is a setting in PharoLauncher A different approach to workaround Pharo 5 alpha transition in image file format... 1. Download latest VM + Image http://pharo.org/download -- Development version: Pharo5 or, get.pharo.org ... 50+vmLatest 2. After opening image, from World Menu go Tools > Catalog Browser 3. Install Pharo Launcher 4. Start PharoLauncher from the World Menu Now I guess you will get the same in reverse, this wont open the old image format. It would be nice for PharoLauncher to handle multiple VMs, but in the meantime you may want to keep two PharoLauncher: Spur & pre-Spur. cheers -ben On Sun, Dec 27, 2015 at 5:03 AM, Saša Janiška <gour@atmarama.com> wrote:
On Uto, 2015-12-22 at 11:56 +0100, Ferlicot D. Cyril wrote:
Since last week a new VM is use for Pharo 5 beta.
Beginning Pharo user here...I had the same problem on my Debian box:
"This interpreter (vers. 6505) cannot read image file (vers. 6521)."
You need to download the new VM on http://files.pharo.org/vm/pharo-spu r32/.
Then I downloaded the new VM image and tried to use it with latest Pharo Launcher ('Bleeding Edge'), but now I get:
"This interpreter (vers. 6521) cannot read image file (vers. 6505)."
which is kind of catch-22 situation...
Then you need to update Pharo Launcher.
...and it looks that I do not have updated Pharo Launcher.
For now the easiest way I think is to enable the development mode in PharoLauncher, go in Monticello, and load the last version of Pharo Launcher core.
Tried that as well, but didn't work.
Later I think that a new release of Pharo Launcher will make thing easier.
Let me say that the potential of Pharo Launcher is really great - it allows (if I got it right) to have many development machines available via different VMs, while still keeping developer's machine in sane state which cannot be said when one does regular development with other (mostly compiled) languages, which is "simply wonderful!".
Now I wonder if you can provide any further hint how to resolve the above?
Is there a plan that in the future Pharo Launcher will become regular part of 'normal' Pharo image?
I know that probably there would be more luch with V4.0, but I simply would like to try latest code eagerly anticipating the day to try 64bit VM.
Still, kudos to all Pharo devs for providing human development environment in the days when things are going insane all around us.
Sincerely, Gour
-- As a lamp in a windless place does not waver, so the transcendentalist, whose mind is controlled, remains always steady in his meditation on the transcendent self.
Le 29/12/2015 04:03, Ben Coman a écrit :
There is a setting in PharoLauncher
A different approach to workaround Pharo 5 alpha transition in image file format... 1. Download latest VM + Image http://pharo.org/download -- Development version: Pharo5 or, get.pharo.org ... 50+vmLatest
2. After opening image, from World Menu go Tools > Catalog Browser
3. Install Pharo Launcher
4. Start PharoLauncher from the World Menu
Now I guess you will get the same in reverse, this wont open the old image format. It would be nice for PharoLauncher to handle multiple VMs, but in the meantime you may want to keep two PharoLauncher: Spur & pre-Spur.
cheers -ben
Hi Ben, With the development version of pharo launcher you can give a path to the cog VM and a path to the spur VM. The launcher will know which image need which VM. So with the development version of PharoLauncher you only need 1 version to be able to launch all images. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France
On Tue, Dec 29, 2015 at 7:58 PM, Ferlicot D. Cyril <cyril.ferlicot@gmail.com> wrote:
Le 29/12/2015 04:03, Ben Coman a écrit :
There is a setting in PharoLauncher
A different approach to workaround Pharo 5 alpha transition in image file format... 1. Download latest VM + Image http://pharo.org/download -- Development version: Pharo5 or, get.pharo.org ... 50+vmLatest
2. After opening image, from World Menu go Tools > Catalog Browser
3. Install Pharo Launcher
4. Start PharoLauncher from the World Menu
Now I guess you will get the same in reverse, this wont open the old image format. It would be nice for PharoLauncher to handle multiple VMs, but in the meantime you may want to keep two PharoLauncher: Spur & pre-Spur.
cheers -ben
Hi Ben,
With the development version of pharo launcher you can give a path to the cog VM and a path to the spur VM. The launcher will know which image need which VM.
So with the development version of PharoLauncher you only need 1 version to be able to launch all images.
Nice. Thanks for the update Cyril. How soon will that be pushed to the Catalog Browser? Alternately, what individual packages would you recommend loading? (limited warranty accepted :) cheers -ben
You just happen to coincide with a transition point from V3 system to new Spur system, which gets us ready for native 64-bit. Just as a point of experiment, try Pharo build 50495 rather than (presumably) Pharo-latest. Then look at upgrading PharoLauncher as others described. Cheers -ben On Tuesday, December 22, 2015, nacho <0800nacho@gmail.com> wrote:
Hi Folks, I've installed pharo-vm and pharo-launcher from AUR as stated in the pharo site. Everything works fine for Pharo 4. But when I try to load a Pharo 5 image I get the following error: This interpreter (vers. 6502) cannot read file image (vers. 6521)
and when I do pharo --version: 3.9-7 #1 Thu Dec 17 00:38:38 CET 2015 gcc 4.6.3 [Production ITHB VM] NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Dec 17 2015 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Dec 17 2015 https://github.com/pharo-project/pharo-vm.git Commit: bad6fa2684afcf1d7cdb485f11049a4a4290fbc8 Date: 2015-12-14 12:47:06 +0100 By: Esteban Lorenzano <estebanlm@gmail.com <javascript:;>> Jenkins build #15024 Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux plugin path: /usr/share/pharo-vm/ [default: /usr/share/pharo-vm/]
Any clues?
Thanks in advance Nacho
----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/VM-error-in-Arch-Linux-tp4868239.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
participants (7)
-
Ben Coman -
Ben Coman
-
Ferlicot D. Cyril -
nacho -
phil＠highoctane.be -
Saša Janiška -
stepharo