I faced an issue that FFI calls fail with arguments of type size_t or the value that was passed to C function was completely wrong. For example you pass 1 but get 29834693165
Cheers, Alex On 28 October 2016 at 14:22, Thierry Goubier <thierry.goub...@gmail.com> wrote: > > > 2016-10-28 12:29 GMT+02:00 Thierry Goubier <thierry.goub...@gmail.com>: > >> >> >> 2016-10-28 11:56 GMT+02:00 Esteban Lorenzano <esteba...@gmail.com>: >> >>> VM here: http://bintray.com/estebanlm/pharo-vm/build#files/ >>> Image here: http://files.pharo.org/get-files/60/pharo-64.zip >>> >> >> Thanks. >> >> >>> >>> this is still not official (that’s why is not in official place) so >>> there are a couple of known problems: >>> >>> - version format is different, and that breaks some things in image that >>> depends on it to know what happens >>> - command line is different and probably you’ll need to play a bit with >>> options (one or two dashes). >>> - UFFI has some failing tests (but most of it works). >>> >>> I would appreciate some help to report and/or fix the emerging problems. >>> >> >> I'll make myself a Makefile for it and test; if I see it stable enough, >> I'll try to use it on a regular basis and report. >> > > Report: > > apart from the missing SSL support which makes loading complex stuff from > github a bit painfull, it seems to be usable enough. > > OSProcess and GitFileTree work fine. Which means gitfiletree:// urls work, > but not github:// urls. > > I loaded a large project (a compiler!) and saw no issues (apart from a > freetype / wrong glyph issue?). All SmaCC tests are green on it, and my > project tests were green as well. > > Thierry > > > >> >> Thierry >> >> >>> >>> cheers, >>> Esteban >>> >>> On 28 Oct 2016, at 10:39, Thierry Goubier <thierry.goub...@gmail.com> >>> wrote: >>> >>> Hi all, >>> >>> anybody knows how to get (and test) the 64bits version of the Pharo vm >>> and image? >>> >>> Thanks, >>> >>> Thierry >>> >>> >>> >> >
