mmm... what is probably not correct is the image...
which 2.0 version are you using? which VM version?
please, check this bug report:
https://pharo.fogbugz.com/f/cases/10395/
it describes the workaround followed to avoid that, but that would be in latests 2.0 images, you can get one here:
http://files.pharo.org/image/20/latest.zip
Esteban
On May 23, 2013, at 7:12 AM, Alexandre Bergel alexandre.bergel@me.com wrote:
If you get the error SmallInteger>>#add, then your VM is probably not the right one. Try instead of using the Cog vm instead if the one shipped with the one-click
Alexandre
Le 21 mai 2013 à 12:24, "roberto.minelli@usi.ch" roberto.minelli@usi.ch a écrit :
Hi,
It's me again. Sorry for bothering you but I'm not able to load Moose from my ConfigurationOf in a fresh 2.0 image… I tried every possible version: minimal, stable, default, and development but it does not load correctly.
Either I got a..
- SmallInteger>>#add: error which leads me to https://pharo.fogbugz.com/f/cases/10395/ but I cannot understand the fix.
- With development (or default) I got a SmallInteger(Object)>>doesNotUnderstand: #isEmpty.
- Some missing dependencies with BlockContext
I'm wondering if someone can please take a fresh Pharo 2.0 image and try to load Moose (stable, default, or whatever) using the Configuration and kindly tell me how to set up my configuration to load it.
FYI I'm loading Moose by doing the following in my configuration of:
spec project: 'Moose' with: [ spec className: 'ConfigurationOfMoose'; loads: #('default'); file: 'ConfigurationOfMoose'; repository: 'http://smalltalkhub.com/mc/Moose/Moose/main' ]
Then I tried to replace #loads: with #versionString: and change the version string but I had no luck.
Thanks in advance, Roberto Minelli _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev