On 29 Dec 2015, at 12:35, stepharo <stepharo(a)free.fr> wrote:
> Oh…
>
> I have no idea. Maybe something related to Nativeboost.
> If you use a pre-Spur image and VM you will not have any problem.
>
> I am really wondering whether having Spur for Pharo 5 is such a good idea.
>
>
> I don't know. Before running faster, I need to be able to run something. Or at
least some key packages like Roassal2 :)
>
> Today I spent all day trying to run Pharo 5 + Roassal2 in Windows 8.1 without hangs.
Not working yet, even with stack VM
http://get.pharo.org/50+vm
<
http://get.pharo.org/50+vmS>
> The 0-byte crash.dmp is not helping at all. This is dissapointing because I was not
planning to debug the VM, or consider moving to Linux.
>
> Anyway, is there a way to get a pharo 5 pre-spur image and VM now?
Guys
This is christmax. We worked 8 h a day last week teaching. We travel from the other part
of the world.
Why do you update the bleeding Pharo 50 and after complain?
I do not get it. I did not update for some of my projects because I do not have the time
to allocate.
Just report your problems to the Pharo mailing-list and we will see.
Esteban will work on Fixing the glitches. Now if people would have helped us to work on
Spur
we would have spare probably 6 months effort. Now this was not the case so it took us 6
months.
yes, people often forgets Pharo 5 is still alpha. We encourage people to use it as a way
to find bugs and solve them… now they cannot expect it is stable until it is not alpha any
more :)
Esteban
ps: Roassal2 was working on mac and linux, I didn’t tested it on windows but I did test
Athens… anyway, I need a bug report and patience :)
Stef
>
> Cheers,
>
> Hernán
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel
http://www.bergel.eu <
http://www.bergel.eu/>
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>> On Dec 27, 2015, at 11:37 PM, Hernán Morales Durand <hernan.morales(a)gmail.com
<mailto:hernan.morales@gmail.com>> wrote:
>>
>> I tried, everything loaded without errors but next this happens:
>>
>>
http://es.tinypic.com/r/10di0w5/9 <
http://es.tinypic.com/r/10di0w5/9>
>>
http://es.tinypic.com/r/2d6k39c/9 <
http://es.tinypic.com/r/2d6k39c/9>
>>
>> crash.dmp is empty
>>
>> Do you recommend to try another Windows VM?
>>
>> (I'm using Windows 8.1, Cog Spur VM 5.0 (release) from Dec 13 2015)
>>
>> Cheers,
>>
>> Hernán
>>
>>
>> 2015-12-27 19:40 GMT-03:00 Alexandre Bergel <
<mailto:alexandre.bergel@me.com>alexandre.bergel@me.com
<mailto:alexandre.bergel@me.com>>:
>> Hi!
>>
>> I have fixed this.
>> If you load Roassal2 in Pharo5, you need to load the slice 17280 from the Pharo5
inbox.
>>
>> Cheers,
>> Alexandre
>>
>>
>> > On Dec 27, 2015, at 4:31 AM, Hernán Morales Durand <
<mailto:hernan.morales@gmail.com>hernan.morales@gmail.com
<mailto:hernan.morales@gmail.com>> wrote:
>> >
>> > Hi guys,
>> >
>> > Installing stable Roassal2 from the Catalog Browser, in Pharo 5 (#50509),
leads to a vanish dialog :
>> >
>> > Information
>> > There was an error while trying to install Roassal2. Installation was
cancelled.
>> >
>> > and to the following message in Transcript:
>> >
>> > Loading 1.20 of ConfigurationOfRoassal2...
>> > ...
>> > Loaded -> ConfigurationOfGlamour-AndreiChis.217 ---
http://smalltalkhub.com/mc/Moose/Glamour/main/
<
http://smalltalkhub.com/mc/Moose/Glamour/main/> ---
http://smalltalkhub.com/mc/Moose/Glamour/main/Error
<
http://smalltalkhub.com/mc/Moose/Glamour/main/Error>: Unable to resolve project
package for 'GlamourCore'. It is likely that that the configuration referencing
this project will not validate properly (see MetacelloToolBox
class>>validateConfiguration:).
>> >
>> > Is Roassal2 configuration broken?
>> >
>> > Cheers,
>> >
>> > Hernán
>> >
>> >
>> > _______________________________________________
>> > Moose-dev mailing list
>> > Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch>
>> >
https://www.list.inf.unibe.ch/listinfo/moose-dev
<
https://www.list.inf.unibe.ch/listinfo/moose-dev>
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel <
http://www.bergel.eu/>http://www.bergel.eu
<
http://www.bergel.eu/>
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch>
>>
https://www.list.inf.unibe.ch/listinfo/moose-dev
<
https://www.list.inf.unibe.ch/listinfo/moose-dev>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch>
>>
https://www.list.inf.unibe.ch/listinfo/moose-dev
<
https://www.list.inf.unibe.ch/listinfo/moose-dev>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch>
>
https://www.list.inf.unibe.ch/listinfo/moose-dev
<
https://www.list.inf.unibe.ch/listinfo/moose-dev>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch>
>
https://www.list.inf.unibe.ch/listinfo/moose-dev
<
https://www.list.inf.unibe.ch/listinfo/moose-dev>
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev