On Fri, 7 Dec 2018 at 01:09, Alexandre Garreau
wrote:
> I didn’t find on the README enough informations (about which dir to use
> and what to do once inside), but found some on a random blog on the web
> [0], and now built it but it seems it only installed executable binary
> stuff under the name
Okay, now I ran it some stuff seems to be more okay, but it still
segfaults:
Segmentation fault Tue Dec 11 01:09:56 2018
/usr/local/lib/squeak/5.0-201812101325/squeak
Pharo VM version: 5.0-201812101325 Tue Dec 11 00:52:05 CET 2018 gcc 6.3.0
[Production Spur VM]
Built from: CoInterpreter VMMak
That sounds normal. "No stash" is not an error.
You should see new files in directory ".git/hooks"
which help give correct date to built VM to avoid "to old" message.
btw, make sure you match your 32/64-bitness between VM and Image.
cheers -ben
On Tue, 11 Dec 2018 at 00:51, Alexandre Garreau
Le 07/12/2018 à 02h25, Ben Coman a écrit :
> On Fri, 7 Dec 2018 at 01:43, Alexandre Garreau
> wrote:
>
>> I built the VM and when running the Pharo.image file got with curl by
>> the site, it runs but warns the VM is too old for this image (strangely,
>> since I built the git version),
>
>
> That
On Fri, 7 Dec 2018 at 01:43, Alexandre Garreau
wrote:
> I built the VM and when running the Pharo.image file got with curl by
> the site, it runs but warns the VM is too old for this image (strangely,
> since I built the git version),
That warning can occur if you didn't run "scripts/updateSCCS
I built the VM and when running the Pharo.image file got with curl by
the site, it runs but warns the VM is too old for this image (strangely,
since I built the git version), and when trying to run the one sitting
in the pharo-launcher archive (PharoLauncher.image), it segfaults (is
this normal? ca
I didn’t find on the README enough informations (about which dir to use
and what to do once inside), but found some on a random blog on the web
[0], and now built it but it seems it only installed executable binary
stuff under the name of “squeak”, is this normal? are you sure it’s not
related to
On Sat, Dec 01, 2018 at 07:37:12PM +0100, Alexandre Garreau wrote:
> > https://github.com/OpenSmalltalk/opensmalltalk-vm
>
> Wait if it’s the same than for squeak… knowing there’s a “squeak-vm”
> package in debian that claim to be able to run several images… could it
> be that it could be used t
On Sat, 1 Dec 2018 at 02:19, Alexandre Garreau
wrote:
> Hi,
>
> I tried to compile itself because I’m usually uncomfortable with using
> binaries downloaded from the internet whose sources couldn’t be checked
> afterwards. I don’t know the status of Pharo regarding Deterministic
> Builds, but I
Le 01/12/2018 à 09h34, Pierce Ng a écrit :
> On Fri, Nov 30, 2018 at 07:15:22PM +0100, Alexandre Garreau wrote:
>> But I saw the bootstrap process involve redownloading a binary image
>> anyway… I’d have just prefered to recompile it to be sure, as I’m
>> usually more comfortable with this idea. N
On Fri, Nov 30, 2018 at 07:15:22PM +0100, Alexandre Garreau wrote:
> But I saw the bootstrap process involve redownloading a binary image
> anyway… I’d have just prefered to recompile it to be sure, as I’m
> usually more comfortable with this idea. Normally compiling a new
> language is —though lo
Hi,
I tried to compile itself because I’m usually incomfortable with using
binaries downloaded from the internet whose sources couldn’t be checked
afterwards. I don’t know the status of Pharo regarding Deterministic
Builds, but I have come anyway to become more comfortable in trusting
what comes
Hi Alexandre,
as Cédrick said there is no need to generate a new image from scratch.
Pharo is basically divided in two parts an image (that is the one that it
is generated by the process you want to run) and a virtual machine to run
the image.
The image is multi-OS you can download a 32 bits ima
Hi Alexandre,
Do you really want to « bootstrap » an image ? You don’t need to (just use an
official image).
Try here, either through the launcher or the curl command line:
https://pharo.org/download (Linux for thé launcher or at the end of the page
from the command line.
HTH,
Cedrick
Env
Le 28/11/2018 à 11h17, Garreau, Alexandre a écrit :
> This VM uses a separate heartbeat thread to update its internal clock
> and handle events. For best operation, this thread should run at a
> higher priority, however the VM was unable to change the priority. The
> effect is that heavily loaded
I need Pharo soon for my studies, and since it’s not packaged for debian
(how sad for something requiring bootstraping hence binaries :/) I
wanted to compile it, but (please tell me what additional informations I
could give you, I’m under Debian GNU/Linux 32bits for now) since then:
galex-713@port
16 matches
Mail list logo
