With latest VM for P7 fetched with get.pharo.org/vmTLatest70
<http://get.pharo.org/vmTLatest70> Then when using the VM with a P7 image: ./pharo ../../../DrGeoII/Dev-pharo7/Pharo7.0-64bit-f82fc36.image This error shows up: This interpreter (vers. 6521) cannot read image file (vers. 68021). Version: ./pharo --version 5.0-201708271955 Sun Aug 27 20:09:20 UTC 2017 gcc 4.6.3 [Production Spur VM] CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 VM: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Sun Aug 27 21:55:26 2017 +0200 $ Plugins: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Linux testing-gce-ebf45dd8-6a4c-43a5-abd0-e5d8673d05a4 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC 2017 i686 i686 i386 GNU/Linux -- Dr. Geo http://drgeo.eu |
On 14 December 2017 at 20:27, Hilaire <[hidden email]> wrote: With latest VM for P7 fetched with get.pharo.org/vmTLatest70 <http://get.pharo.org/vmTLates You have is a 32-bit VM ^^^^ (four digit vers.) and a 64-bit Image (five digit vers.) vvvvvv cannot read image file (vers. 68021). The https://pharo.org/download shows how to one flavour of 64-bit VM curl https://get.pharo.org/64/ | bash but I can't guess how that interfaces with getting a 64-bit vmTLatest70 I wonder if rather than squeezing "64" onto the path side of url, it would be easier to squeeze it into the host name... get64.pharo.org and all existing url-paths remain unchanged?(?) cheers -ben P.S. it would be useful if --version more prominently displayed whether it was 32bit or 64bit something like... "[Production Spur VM 64bit]"
|
Instructions for at http://get.pharo.org were followed, there is no
option about 32 or 64 bits VM Installed P6 VM seems too old for git, got some complains/errors on that. http://files.pharo.org did not help either for lates 64bits P7 VM. Will try with a newer P6 VM in case... Le 14/12/2017 à 14:21, Ben Coman a écrit : > You have is a 32-bit VM ^^^^ (four digit vers.) > and a 64-bit Image (five digit vers.) vvvvvv > > cannot read image file (vers. 68021). > > > > The https://pharo.org/download shows how to one flavour of 64-bit VM > curl https://get.pharo.org/64/ | bash > > but I can't guess how that interfaces with getting a 64-bit vmTLatest70 > I wonder if rather than squeezing "64" onto the path side of url, > it would be easier to squeeze it into the host name... get64.pharo.org > <http://get64.pharo.org> > and all existing url-paths remain unchanged?(?) -- Dr. Geo http://drgeo.eu |
In reply to this post by Ben Coman
On 14-12-17 14:21, Ben Coman wrote:
> > > On 14 December 2017 at 20:27, Hilaire > <[hidden email] > <mailto:[hidden email]>> wrote: > Version: > > ./pharo --version > 5.0-201708271955 Sun Aug 27 20:09:20 UTC 2017 gcc 4.6.3 [Production > Spur VM] > CoInterpreter VMMaker.oscog-eem.2265 uuid: > 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: > 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 > VM: 201708271955 Yes, that linux 32 bit vm hasn't been build recently and has known crashes. On the opensmalltalk bintray the linux 32 x86 pharo vm is also currently missing https://bintray.com/opensmalltalk/vm/cog/201712121955#files Stephan |
In reply to this post by HilaireFernandes
> On 14 Dec 2017, at 16:14, Hilaire <[hidden email]> wrote: > > Instructions for at http://get.pharo.org were followed, there is no option about 32 or 64 bits VM > Related entry: https://pharo.fogbugz.com/f/cases/20803/http-get-pharo-org-does-not-list-any-64-bits-version It is very high on my todo to add an explanation (this is not that simple, as the page is auto-generated and I need to find out how to do it) Marcus |
Free forum by Nabble | Edit this page |