Thank you Norbert and IID.
Another brick in the bridge towards mainstream. :)
Regards,
El jue., 22 nov. 2018 a las 18:11, Sven Van Caekenberghe
() escribió:
>
> Nice. Another piece of the puzzle. Thank you.
>
> > On 22 Nov 2018, at 17:56, Norbert Hartl wrote:
> >
> > JSONSchema
> > ===
This is great.
Thanks!
On Thu, 22 Nov 2018 at 18:10 Sven Van Caekenberghe wrote:
> Nice. Another piece of the puzzle. Thank you.
>
> > On 22 Nov 2018, at 17:56, Norbert Hartl wrote:
> >
> > JSONSchema
> > ===
> >
> > This is an implementation of JSON Schema for the pharo language. It
Nice. Another piece of the puzzle. Thank you.
> On 22 Nov 2018, at 17:56, Norbert Hartl wrote:
>
> JSONSchema
> ===
>
> This is an implementation of JSON Schema for the pharo language. It is used
> to define the structure and values of a JSON string and to validate it. The
> schema
--- Begin Message ---
EstebanLM wrote
> Hi,
>
> You are missing to initialise the Voyage repository.
> I don’t know how is explained in the Mooc, but you will probably need to
> do something like:
>
> VOMemoryRepository new enableSingleton.
>
> Cheers,
> Esteban
Hi Esteban.
actually I'm
It can't find the display drivers since the appropriate 32 bit libraries
are missing. Use the 'ldd' command on the VM binary and on the shared
libraries in its directory to find out which ones you're missing.
Cheers,
Hans-Martin
Am 22. November 2018 4:22:19 nachm. schrieb horrido
:
I'm
Okay, I've resolved everything. First, the reason why I'm getting the
'pthread_setschedparam failed' error when I run Pharo under Debian is
because it must be run as 'root'! Don't ask me why, but that's the reason
why Pharo can't set thread priorities. (This wasn't an issue under Ubuntu
Server –
Hi,
You are missing to initialise the Voyage repository.
I don’t know how is explained in the Mooc, but you will probably need to do
something like:
VOMemoryRepository new enableSingleton.
Cheers,
Esteban
> On 22 Nov 2018, at 17:51, iu136 via Pharo-users
> wrote:
>
>
> From: iu136
>
JSONSchema
===
This is an implementation of JSON Schema for the pharo language. It is used to
define the structure and values of a JSON string and to validate it. The schema
itself can be externalized for being consumed by a third party.
I like to announce the availability of a JSON
--- Begin Message ---
hi guys
I'm following the Pharo MOOC and I'm at Week 4. the other day, I was trying
to implement TinyBlog: Data Persistency using Voyage and Mongo, when I tried
to compile the code, I've got an Error. the title of Error says:
"MessageNotUnderstood: receiver of "save:" is
On Thu, 22 Nov 2018 at 23:22, horrido wrote:
> I'm running 64-bit Debian in a VirtualBox image on my Mac.
>
> When I install 64-bit Pharo, it works fine. When I install 32-bit Pharo, I
> get the error message below. What's the difference??? Why can one find the
> display driver and the other
Using Linux requires certain skills/knowledge, this has nothing to do with
Pharo or Smalltalk.
To run 32-bit binaries on a 64-bit system you need 32-bit libraries.
This might help (although maybe it is not totally up to date for Pharo 7)
I'm running 64-bit Debian in a VirtualBox image on my Mac.
When I install 64-bit Pharo, it works fine. When I install 32-bit Pharo, I
get the error message below. What's the difference??? Why can one find the
display driver and the other can't? This makes no sense.
Earlier, people have been
It works like a charm now!!! Thanks!
On Tue, Nov 13, 2018 at 11:23 AM Marcus Denker
wrote:
> More progress… in the latest Pharo7 this is now working... (#operation
> reifies the original operation):
>
> | link choice |
>
> choice := true.
> link := MetaLink new metaObject: [ :operation |
>
Those errors are not related to a 32 or 64 bits problem. The issue looks
like you've launched pharo-ui which looks for a physical screen that
isn't there. Are you trying to run pharo-ui in a debian VPS ?
You should run 'pharo' and 'pharo-ui', something like this:
$ pharo myApplication.image
On Thu, 22 Nov 2018 at 20:27, horrido wrote:
> I tried recompiling the SHA256 library without the '-m32' flag and 64-bit
>
Would the in-Image SHA256 be sufficient to start with?
Perhaps allow you to move forward while sorting out the main problem.
Another option could be libsodium
David Buck provided a revision on his proposal:
I agree with tossing the VM hack - it's not worth it.
An objective score is best and I would prefer not to score based on number
of classes, number of methods or method size. The score should be simply
the highest total of captured cells in the
I ran 32-bit Pharo under 64-bit Debian and got this error:
[1] 8127
richard@debian:~/pharo32$ could not find display driver vm-display-X11;
either:
- check that
/home/richard/pharo32/pharo-vm/lib/pharo/5.0-201806281256//vm-display-X11.so
exists, or
- use the '-plugins ' option to tell me
I tried recompiling the SHA256 library without the '-m32' flag and 64-bit
Pharo seg faulted:
pthread_setschedparam failed: Operation not permitted
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
He's got a 32 bit library that he wants to use, that won't work with a 64
bit VM.
Of course, recompiling the library for 64 bit is an option, too, but
probably more complicated.
Cheers,
Hans-Martin
Am 22. November 2018 9:21:47 vorm. schrieb Sven Van Caekenberghe
:
Just use 64 bit Pharo 7
I think Sven is probably right - but my notes show a DO installation from 5
months ago with:
curl https://get.pharo.org | bash
wget -O -
http://download.opensuse.org/repositories/devel:/languages:/pharo:/stable/xUbuntu_16.04/Release.key
| apt-key add -
echo "deb
Just use 64 bit Pharo 7 on a 64 bit Linux and be done with all this mess.
> On 22 Nov 2018, at 01:39, horrido wrote:
>
> Using zeroconf, I installed 32-bit Pharo under 64-bit Debian. Pharo refused
> to run – it threw up a bunch of errors.
>
>
>
> Mariano Martinez Peck wrote
>> Run Pharo 32
21 matches
Mail list logo
