2017-01-23 12:57 GMT+01:00 Esteban Lorenzano <[email protected]>:

>
> On 23 Jan 2017, at 12:46, Thierry Goubier <[email protected]>
> wrote:
>
>
>
> 2017-01-23 12:40 GMT+01:00 Esteban Lorenzano <[email protected]>:
>
>>
>> On 23 Jan 2017, at 12:37, Thierry Goubier <[email protected]>
>> wrote:
>>
>>
>>
>> 2017-01-23 12:26 GMT+01:00 Esteban Lorenzano <[email protected]>:
>>
>>>
>>>
>>> me neither :)
>>> I added AioPlugin (as external) to all linux distributions… they will be
>>> available in latest VMs.
>>>
>>> can someone test it?
>>>
>>
>> I'll try. Where is the source for the current pharo vms? On github,
>> pharo-vm?
>>
>>
>> https://github.com/pharo-project/pharo-vm
>>
>
> Thanks.
>
> How do you build a 64bits linux vm? The doc is limited to 32 bits.
>
>
> README is not updated, and process is not like that anymore.
> Now, you have to go do:
>
> cd opensmalltalk-vm/build.linux64x64/pharo.cog.spur/build (for threaded)
> cd opensmalltalk-vm/build.linux64x64/pharo.cog.spur/build.itimerheartbeat
> (for itimer)
>
> then just ./mvm
>

And you reply y / n to the clean? question in the mvm script?

Regards,

Thierry


>
> cheers,
> Esteban
>
>
> Regards,
>
> Thierry
>
>
>>
>> cheers,
>> Esteban
>>
>>
>> I'd like to try building it, to see if my 64bits issues would be solved.
>>
>> Thierry
>>
>>
>>>
>>> Esteban
>>>
>>> >
>>> > Whatever the reason for that, the notifier about the missing plugin was
>>> > too annoying, so I got rid of it in the latest OSProcess update:
>>> >
>>> >  Name: OSProcess-Base-dtl.56
>>> >  Time: 17 January 2017, 8:47:36.321587 am
>>> >
>>> >  OSProcess 4.6.7
>>> >
>>> >  Add nil checks in #shutDown: to prevent failures when exiting existing
>>> >  image with a VM that does not include OSPP (e.g. SqueakJS).
>>> >
>>> >  For AIO event hander, if the AIO plugin is not present, write an error
>>> >  to console rather than interrupting the image with a notifer. Reduces
>>> the
>>> >  annoyance level if VM provider provides OSPP but neglects to include
>>> the
>>> >  AIO plugin.
>>> >
>>> > Dave
>>> >
>>> >
>>>
>>
>

Reply via email to