- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - PharoDebug.log
by Esteban Lorenzano Sept. 24, 2018

Sept. 24, 2018

That means primAllocateExecutablePage failed. There should be an errorCode value there, that can help us understand better the problem. Can you check at it? Thanks! Esteban > On 24 Sep 2018, at 17:49, Petr Fischer via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > >

2 1

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - corrected screenshot link
by Guillermo Polito Sept. 24, 2018

Sept. 24, 2018

This looks like an FFI error... Can you try running uFFI tests in your system and sen us the results? Tx, Guille On Sun, Sep 23, 2018 at 9:54 PM Petr Fischer via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > Ohh sorry - better screenshot link: > > > > https://app.box.com/s/isd7tdyv8lgr8aj5449xqkrxt4y4uxqy > > > > pf > > > > Hi Petr, > > > > On Sun, 23 Sep 2018 at 19:52, Petr Fischer via Pharo-dev > > <pharo-dev(a)lists.pharo.org> wrote: > > > > > > Hello, I want to propose some small fixes to Pharo, it took me hours > just to run Pharo with Iceberg on CentOS 7 (I don't care about Ubuntu)... > > > > > > Now I am stuck with this Iceberg error: > > > https://app.box.com/file/321243070589 > > > > I was presented with a login box when I tried to view this. > > > > > > > I am using 64bit Pharo VM + latest Pharo7 image from zeroconf (and > latest CentOS7) - is Iceberg OK on 64bits? > > > > Yes, I use it all the time (on Ubuntu 16.04 64 bit). > > > > Cheers, > > Alistair > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

2 1

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage - PharoDebug.log
by Petr Fischer Sept. 24, 2018

Sept. 24, 2018

PharoDebug.log attached pf > Ohh sorry - better screenshot link: > > https://app.box.com/s/isd7tdyv8lgr8aj5449xqkrxt4y4uxqy > > pf > > > > Hi Petr, > > > > On Sun, 23 Sep 2018 at 19:52, Petr Fischer via Pharo-dev > > <pharo-dev(a)lists.pharo.org> wrote: > > > > > > Hello, I want to propose some small fixes to Pharo, it took me hours just to run Pharo with Iceberg on CentOS 7 (I don't care about Ubuntu)... > > > > > > Now I am stuck with this Iceberg error: > > > https://app.box.com/file/321243070589 > > > > I was presented with a login box when I tried to view this. > > > > > > > I am using 64bit Pharo VM + latest Pharo7 image from zeroconf (and latest CentOS7) - is Iceberg OK on 64bits? > > > > Yes, I use it all the time (on Ubuntu 16.04 64 bit). > > > > Cheers, > > Alistair >

1 0

[Pharo 7.0-dev] Build #1262: 22465 Examples in Number>>#printShowingDecimalPlaces: should be runnable
by ci-pharo-ci-jenkins2＠inria.fr Sept. 24, 2018

Sept. 24, 2018

There is a new Pharo build available! The status of the build #1262 was: FAILURE. The Pull Request #1813 was integrated: "22465 Examples in Number>>#printShowingDecimalPlaces: should be runnable" Pull request url: https://github.com/pharo-project/pharo/pull/1813 Issue Url: https://pharo.fogbugz.com/f/cases/22465 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Next Pharo Sprint: Sept 28
by Marcus Denker Sept. 24, 2018

Sept. 24, 2018

We will organize a Pharo sprint / Moose dojo Sept 28, starting at 10:00am. (Local Time Paris). Goals of this sprint: â¢ Pharo 7 issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come https://association.pharo.org/event-2973620

1 0

Re: [Pharo-dev] iceberg PrimitiveFailed allocateExecutablePage
by Alistair Grant Sept. 23, 2018

Sept. 23, 2018

Hi Petr, On Sun, 23 Sep 2018 at 19:52, Petr Fischer via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > Hello, I want to propose some small fixes to Pharo, it took me hours just to run Pharo with Iceberg on CentOS 7 (I don't care about Ubuntu)... > > Now I am stuck with this Iceberg error: > https://app.box.com/file/321243070589 I was presented with a login box when I tried to view this. > I am using 64bit Pharo VM + latest Pharo7 image from zeroconf (and latest CentOS7) - is Iceberg OK on 64bits? Yes, I use it all the time (on Ubuntu 16.04 64 bit). Cheers, Alistair

2 1

iceberg PrimitiveFailed allocateExecutablePage
by Petr Fischer Sept. 23, 2018

Sept. 23, 2018

Hello, I want to propose some small fixes to Pharo, it took me hours just to run Pharo with Iceberg on CentOS 7 (I don't care about Ubuntu)... Now I am stuck with this Iceberg error: https://app.box.com/file/321243070589 I am using 64bit Pharo VM + latest Pharo7 image from zeroconf (and latest CentOS7) - is Iceberg OK on 64bits? Thanks! pf

1 0

update linux info page again, please [CentOS/RHEL]
by Petr Fischer Sept. 23, 2018

Sept. 23, 2018

Hello, please, edit CentOS7 installation page: https://pharo.org/gnu-linux-installation-64 and add workaround for CentOS7 section, wihout this symlink, iceberg is broken: (do as root) cd /usr/lib64 ln -s libcurl.so.4 libcurl-gnutls.so.4 Best solution is to put this in the RPM post installation step (I mean RPM from official Pharo CentOS repository) - but we will wait for this fix for months, maybe years, so, workaround info on that page is necessary and easy to manage. More details here: http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2018-July/272624… Thanks! pf

1 0

Float should not implement #to:, #to:by:, etc...
by Julien Sept. 23, 2018

Sept. 23, 2018

Hello, I realised that it is possible to create an interval of floats. I think this is bad because, since intervals are computed by successively adding a number, it might result in precision errors. (0.0 to: 1.0 by: 0.1) asArray >>> #(0.0 0.1 0.2 0.30000000000000004 0.4 0.5 0.6000000000000001 0.7000000000000001 0.8 0.9 1.0) The correct (precise) way to do it would be to use ScaledDecimal: (0.0s1 to: 1.0s1 by: 0.1s1) asArray >>> #(0.0s1 0.1s1 0.2s1 0.3s1 0.4s1 0.5s1 0.6s1 0.7s1 0.8s1 0.9s1 1.0s1) I opened an issue about it: https://pharo.fogbugz.com/f/cases/22467/Float-should-not-implement-to-to-by… <https://pharo.fogbugz.com/f/cases/22467/Float-should-not-implement-to-to-by…> And Iâd like to discuss this with you. What do you think? Cheers, Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40

7 11

[Pharo 7.0-dev] Build #1261: Bug fix for bindings to inherited pool dictionaries (issue 22470)
by ci-pharo-ci-jenkins2＠inria.fr Sept. 22, 2018

Sept. 22, 2018

There is a new Pharo build available! The status of the build #1261 was: FAILURE. The Pull Request #1816 was integrated: "Bug fix for bindings to inherited pool dictionaries (issue 22470)" Pull request url: https://github.com/pharo-project/pharo/pull/1816 Issue Url: https://pharo.fogbugz.com/f/cases/22470 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0