Le 03/11/2016 à 19:25, Esteban Lorenzano a écrit :
On 3 Nov 2016, at 19:12, Casimiro de Almeida Barreto
<casimiro.barr...@gmail.com <mailto:casimiro.barr...@gmail.com>> wrote:
BTW, the threaded version requires to be run as super user because it
tries to do a pthread_setschedparam(). I tried to fiddle with
/etc/security/limits.conf... but it's not something fancy to do…
no, is not hard.
you just need to add this file:
pharo.conf
*hardrtprio2
*soft rtprio2
to:
/etc/security/limits.d
And reboot for this to be applied.
Thierry
Esteban
Best regards,
Casimiro Barreto
Em 03-11-2016 13:53, Thierry Goubier escreveu:
Hi Esteban,
Another question about Pharo 64 bits.
Why are libgit/libSDL/libssh included in the vm? Ubuntu 16.10
provides them with the same version numbers, more or less.
(libgit2 is so.0.24.0 on ubuntu instead of so.0.24.2 in the pharo vm,
SDL and ssh are the exact same versions).
Collectively, those three libs are ~ 5M.
Thierry
2016-10-28 11:56 GMT+02:00 Esteban Lorenzano <esteba...@gmail.com
<mailto:esteba...@gmail.com>>:
VM here: http://bintray.com/estebanlm/pharo-vm/build#files/
<http://bintray.com/estebanlm/pharo-vm/build#files/>
Image here: http://files.pharo.org/get-files/60/pharo-64.zip
<http://files.pharo.org/get-files/60/pharo-64.zip>
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.
cheers,
Esteban
On 28 Oct 2016, at 10:39, Thierry Goubier
<thierry.goub...@gmail.com <mailto: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
--
The information contained in this message is confidential and intended
to the recipients specified in the headers. If you received this
message by error, notify the sender immediately. The unauthorized use,
disclosure, copy or alteration of this message are strictly forbidden
and subjected to civil and criminal sanctions.
==
This email may be signed using PGP key *ID: 0x4134A417*
