I wonder how. AFAIK different length of word will warranty that you cannot use most of the plugins (in the case you actually can compile the vm without made any change). I know Dave made the interpreter vm compilable in 64bits, with a flag or something. But that not talks about the plugins (FFI, in particular, I do not think will work). For compiling the stack/cog there are other problems, I think. I may be wrong, but even the StackVM will have some problems because registers change in 64bits. ⦠or Iâm having wrong assumptions, and it is easily feasible, but I do not think so. Esteban On 16 May 2014, at 16:31, Chris Cunningham <cunningham.cb@gmail.com> wrote:
Right. Running an image natively in 64 bits doesn't mean you have to have a 64 bit image as well. http://timmydosmalltalk.wordpress.com/2014/03/13/howto-build-a-64-native-sta... (not my work at all - just sharing).
-cbc
On Fri, May 16, 2014 at 6:33 AM, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote: the SqueakVM https://packages.debian.org/sid/amd64/squeak-vm/download is linked against 64bits libraries, at least as far as I am correct this is what say:
ldd squeakvm
Next I tested I can run DrGeo (1.4 pharo based, 32 bits image) with this VM on a 64 bits host (uname -a).
Pharo 2 does not work as this vm is too old.
Where am I wrong?
Hilaire
Le 16/05/2014 10:20, Esteban Lorenzano a écrit :
I do not understand. To compile a regular vm in a 64bits platform is trivial. You just need to have the 32bits library installed. But to have a 64bits vm that runs on 64bits⦠thatâs another very different history:
-- Dr. Geo http://drgeo.eu