On 21/02/13 3:12 AM, Sven Van Caekenberghe wrote:

On 20 Feb 2013, at 22:23, Yanni Chiu 
<[email protected]> wrote:

Switch to a CogVM (early version of PharoVM) that was lying around.

This is a bit to be expected when you use older VMs, the one-click or 
designated Pharo (NBCog) VMs would have prevented these issues.

Actually, the older VM worked fine - it's just a version of PharoVM, before it's name was changed from CogVM. The problem is that even the latest cog vm from http://mirandabanda.org will not work with Pharo-2.0.

Next step, try to load my custom code…

Let us know how it goes !

I just had to change my build script to stop loading an older version of Fuel on top of the version already present in Pharo-2.0. After some quick manual testing, things look good.

But, the newer Fuel version means I have to migrate Fuel versions again, which is not something I expected to have to do. Hmmm, will have to back away from moving to 2.0, for now.



Reply via email to