August 2018 - Pharo-users - lists.pharo.org

Dynabook and authentic learning pedagogy

by Hilaire

Hi, A few notes on how Dynabook and authentic learning methodology could be related. http://blog.drgeo.eu/post/2018/Authentic-learning Hilaire -- Dr. Geo http://drgeo.eu

Aug. 23, 2018

Re: [Pharo-users] Making TDD in pharo work properly (aka - walkback on a missing class is nasty)

by Marcus Denker

> On 22 Aug 2018, at 16:24, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - but I guess my question is (and excuse my basic knowledge in this area) - when a class isnât found - can we do better than return nil so that the debugger can give a better msg and presumably the code Iâve written could live on that undefined object? Or am thinking about this wrong? In pharo7 we could easily do that (due to the âbindingâ, the meta class of the variable) being different. We could return a nil subclass or add code into the method directly. But the problem with that is that nil checks are always identity checksâ¦ Could you not in the case you now raise the error just fall back to the âdefine methodâ, the behaviour we have now? Marcus > > I will also put together a pr for this in Pharo 7 if you think itâs a decent fix. > > Tim > > Sent from my iPhone > > > > Sent from my iPhone >> On 22 Aug 2018, at 09:51, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hi, >> >> I played with it, nice! >> >> I guess the case when you really get a DNU on nil (and want to create method there) does not really happenâ¦ extending nil is for special cases. >> >> Marcus >> >> >>> On 22 Aug 2018, at 13:39, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>> Sorry Marcus - you needed to follow the exercism instructions and right click on the exercism package to get an exercism menu to fetch a new exercise (e.g. hello-world). The is then using the TonalReader to pull in code - and then you get a test class that can reference a class that isnât there yet. (But you need to have the exercism cli installed as per the instructions etc). >>> >>> In retrospect I think it might be simpler to download this 6.1 image that already has done that - https://www.dropbox.com/s/x2ot9f8arbbvlyb/PharoExercism.zip?dl=0 >>> It has TwoFerTest that is in that state. If you click on the TestWithName orb, you will see "#new was sent to nilâ - can you can see how my Create button has been fixed per you suggestions to create a class. (The code I wrote is in ExercismTools:DoesNotUnderstandDebugAction>>createMissingClassIn:) >>> >>> Tim >>> >>> >>>> On 22 Aug 2018, at 04:44, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>>> >>>> >>>> >>>>> On 17 Aug 2018, at 14:20, Tim Mackinnon <tim(a)testit.works> wrote: >>>>> >>>>> The direct link to instructions is here: https://exercism.io/tracks/pharo/installation (not sure if you have to be signed up to see it otherwise its in the repo here: https://github.com/exercism/pharo/blob/master/docs/INSTALLATION.md) >>>> >>>> Hmâ¦ AllExercismTests seems to not be there (just a green test in Welcome) >>>> >>>> Is this supposed to contain the code below (the createMissingClassActionFor:in:) ? >>>> >>>> It would be nice to have an image that shows exactly the problem (I do not have that much time sadly to work on it,but I do have some time to check if I have an image that is set up to the point where i can easily recreate the problem) >>>> >>>> Marcus >>>> >>>> >>>>> Tim >>>>> >>>>>> On 17 Aug 2018, at 07:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>>>>> >>>>>> >>>>>> >>>>>>> On 17 Aug 2018, at 13:00, Tim Mackinnon <tim(a)testit.works> wrote: >>>>>>> >>>>>>> >>>>>>> Hi Marcus - I can put an image somewhere if that helps (do you just need the .image and .changes)? >>>>>>> >>>>>>> Or you can repro from a fresh 6.1 if you follow the exercism Pharo instructions (https://exercism.io/tracks/pharo) to load the first hello world-world example and run the tests. This has my code changes to make create work with a nil class - but maybe we can do better? >>>>>> I will do that and have a look! >>>>>> >>>>>>> Tim >>>>>>> >>>>>>> >>>>>>> Sent from my iPhone >>>>>>> >>>>>>>> On 17 Aug 2018, at 06:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On 10 Aug 2018, at 23:16, Tim Mackinnon <tim(a)testit.works> wrote: >>>>>>>>> >>>>>>>>> Actually I think I figured that bit out - a bit clumsily - (pointers appreciated) >>>>>>>>> >>>>>>>>> createMissingClassActionFor: aMessage in: aContext >>>>>>>>> |errorNode senderContext newClass variableNode | >>>>>>>>> senderContext := aContext sender. >>>>>>>>> errorNode := senderContext method sourceNodeExecutedForPC: senderContext pc. >>>>>>>>> variableNode := errorNode receiver receiver. >>>>>>>>> >>>>>>>>> newClass := OCUndeclaredVariableWarning new node: variableNode; defineClass: variableNode name. >>>>>>>>> aContext restart. >>>>>>>>> >>>>>>>>> However that last line is wrong, as it doesnât restart with my newly defined class - I also tried >>>>>>>>> >>>>>>>>> aContext restartWithNewReceiver: newClass >>>>>>>>> >>>>>>>>> But again, I get a debugger where my class is still bound to nil. So whatâs the trick to re-evaluate with the new class Iâve created? Or maybe Iâm totally on the wrong track (still its very interestingâ¦) >>>>>>>> >>>>>>>> >>>>>>>> what is a bit bad is that you catch the problem âtoo lateâ (that is, the DNU to nil, not the read of nil), so nil is already pushed on the stack at this point. >>>>>>>> >>>>>>>> I tried it in the inspector and at least the class binding was correct after defining the classâ¦ do you have an image with the whole code to try? >>>>>>>> >>>>>>>> Marcus >> >> > >

Aug. 23, 2018

Re: [Pharo-users] How do I get ZeroMQ working?

by Marten Feldtmann

Simple question: Pharo 32 or 64 bit ? If you work with Pharo32 you need to install the 32bit (Unix)-libraries for 0MQ. If you work with Pharo64 you use the 64bit (Unix)-Libraries. So - what is your environment ? Marten Am 23.08.2018 um 10:54 schrieb H. Hirzel: > Hello > > I installed JupyterTalk [1]. With it comes a ZeroMQ implementation > [2]. This was done on Ubuntu 18.04.1 (Bionic Beaver, 64bit). > > However the ZeroMQ tests all fail. > > I assume there is something missing in the installation. > > How can I test that? Any other suggestions? > > Kind regards > Hannes > > > > > > > > [1] JupyterTalk (https://github.com/jmari/JupyterTalk) is a Smalltalk > kernel for the Jupyter notebook system: http://jupyter.org/ > > [2] ZeroMQ is a high-performance asynchronous messaging library, aimed > at use in distributed or concurrent applications. > It provides a message queue, but unlike message-oriented middleware, a > ZeroMQ system can run without a dedicated message broker. > https://en.wikipedia.org/wiki/ZeroMQ > -- Marten Feldtmann

Aug. 23, 2018

Re: [Pharo-users] How do I get ZeroMQ working?

by H. Hirzel

P.S. I assume I have to install a package on Ubuntu 18.04 Bionic Beaver. The question is which one. Note: I plan to write a comprehensive installation instruction for JuypterTalk. On 8/23/18, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Hello > > I installed JupyterTalk [1]. With it comes a ZeroMQ implementation > [2]. This was done on Ubuntu 18.04.1 (Bionic Beaver, 64bit). > > However the ZeroMQ tests all fail. > > I assume there is something missing in the installation. > > How can I test that? Any other suggestions? > > Kind regards > Hannes > > > > > > > > [1] JupyterTalk (https://github.com/jmari/JupyterTalk) is a Smalltalk > kernel for the Jupyter notebook system: http://jupyter.org/ > > [2] ZeroMQ is a high-performance asynchronous messaging library, aimed > at use in distributed or concurrent applications. > It provides a message queue, but unlike message-oriented middleware, a > ZeroMQ system can run without a dedicated message broker. > https://en.wikipedia.org/wiki/ZeroMQ >

Aug. 23, 2018

How do I get ZeroMQ working?

by H. Hirzel

Hello I installed JupyterTalk [1]. With it comes a ZeroMQ implementation [2]. This was done on Ubuntu 18.04.1 (Bionic Beaver, 64bit). However the ZeroMQ tests all fail. I assume there is something missing in the installation. How can I test that? Any other suggestions? Kind regards Hannes [1] JupyterTalk (https://github.com/jmari/JupyterTalk) is a Smalltalk kernel for the Jupyter notebook system: http://jupyter.org/ [2] ZeroMQ is a high-performance asynchronous messaging library, aimed at use in distributed or concurrent applications. It provides a message queue, but unlike message-oriented middleware, a ZeroMQ system can run without a dedicated message broker. https://en.wikipedia.org/wiki/ZeroMQ

Aug. 23, 2018

Re: [Pharo-users] Pharo 6 snap package

by Esteban Lorenzano

Hi, Guille made this one time ago: https://github.com/guillep/pharo-snapcraft <https://github.com/guillep/pharo-snapcraft> cheers, Esteban > On 22 Aug 2018, at 17:19, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > > Hello > > Are there plans to do a Pharo 6.1 snap package in the upcoming > months? (Ubuntu 18.04.1) > > --Hannes > > On 6/13/17, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >> On Tue, Jun 13, 2017 at 11:34 AM, Alistair Grant <akgrant0710(a)gmail.com> >> wrote: >> >>> On Tue, Jun 13, 2017 at 11:25:15AM +0200, phil(a)highoctane.be wrote: >>>> I need to upgrade to 16.04 now :-) >>> >>> :-) >>> >>> Don't forget you can install snapd on Ubuntu 14.04: >>> >>> https://snapcraft.io/docs/core/install-ubuntu >>> >>> >> Ah, wasn't aware of that. Thx Alistair! >> >> Phil >> >> >>> Cheers, >>> Alistair >>> >>> >>>> Phil >>>> >>>> On Tue, Jun 13, 2017 at 11:04 AM, Stephane Ducasse < >>> stepharo.self(a)gmail.com> >>>> wrote: >>>> >>>> THANKS A LOT ALISTAIR. >>>> I mean it :) >>>> >>>> On Tue, Jun 13, 2017 at 10:58 AM, Alistair Grant < >>> akgrant0710(a)gmail.com> >>>> wrote: >>>>> Hi Everyone, >>>>> >>>>> I've updated the Pharo 6 snap package for Ubuntu. >>>>> >>>>> The major advantages of using the snap package are: >>>>> >>>>> - No need to install all the 32 bit dependencies on a 64 bit >>> system, >>>>> they're all contained and isolated within the snap package. >>>>> - Automagically distinguish between 32 bit and 64 bit images and >>> run the >>>>> appropriate VM (as with the ZeroConf package, the 64 bit VM >>>> still >>>>> needs more testing). >>>>> >>>>> >>>>> >>>>> To get Pharo up and running on Ubuntu 16.04 or later: >>>>> >>>>> # Install Pharo >>>>> $ sudo snap install --candidate pharo --classic >>>>> # If your system isn't configured for threaded heartbeat: >>>>> $ sudo pharo.config >>>>> # Download the latest Pharo 6 image >>>>> $ pharo.getimage >>>>> # Go... >>>>> $ pharo.ui Pharo.image >>>>> # or: >>>>> $ pharo Pharo.image eval 4+3 >>>>> >>>>> To get a list of available commands: >>>>> >>>>> $ snap info pharo >>>>> >>>>> >>>>> If you're on Debian or Ubuntu 14.04 you'll need to install snapd, >>> see >>>>> https://snapcraft.io/docs/core/install >>>>> >>>>> >>>>> The VM is the threaded heartbeat, dated 201705310241. >>>>> >>>>> The installation flags are: >>>>> >>>>> --candidate - The edge and beta channels are for development >>> versions. >>>>> It progresses to candidate and then stable. >>>>> --classic - Snap packages are normally sandboxed for security >>>>> reasons. Since Pharo is a development environment >>>>> in which we want to be able to run any executable, >>>>> or load any library, it is installed with access to >>>>> the entire system (as the running user). >>>>> >>>>> Why use snap packages? >>>>> >>>>> - They include all dependencies. In particular, for the 32 bit >>>>> versions, this means that it isn't necessary to install all the >>> 32 bit >>>>> architecture and associated dependencies. >>>>> - Including dependencies means that there shouldn't be any >>> problems with >>>>> incompatible library versions when upgrading. >>>>> >>>>> Why not use snap packages? >>>>> >>>>> - It's a relatively new technology, with a number of rough edges. >>>>> - There may still be issues with its sandboxing that I haven't >>>>> discovered yet. >>>>> - Because the package uses classic confinement, it isn't >>>>> cross-distribution in practice (unfortunately). >>>>> >>>>> Please let me know of any other advantages or disadvantages you >>> think >>>>> should be listed here. >>>>> >>>>> If you don't trust me to configure your system correctly (which >>> requires >>>>> sudo): >>>>> >>>>> - All the scripts that make up the sub-commands are visible, e.g. >>>>> pharo.config can be viewed at /snap/pharo/current/usr/bin/CONFIG >>>>> >>>>> >>>>> The packaging code is at: https://github.com/akgrant43/pharo-snap >>>>> >>>>> >>>>> Cheers, >>>>> Alistair >>> >>> >>> >> >

Aug. 23, 2018

Re: [Pharo-users] Jupyter notebooks / Dynabook / JupyterTalk

by H. Hirzel

I restarted the machine and DID NOT start Pharo. Just jupyter notebook. and then in the browser 'New ' / 'Pharo Smalltalk' --> Pharo was started up automatically. But the error is still there. More details see screen shot On 8/22/18, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > P.S. Probably noteworthy is that for some reason a second instance of > Pharo was opened. Probably by the command > > jupyter notebook > > I could close one but after closing the other instance it was opened > automatically again. > > On 8/22/18, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> The installation progressed, success seems to be near, but still a >> problem >> >> The process so far: >> >> 1. Ubuntu 18.04.1 (64bit Bionic beaver) >> >> 2. Anaconda python distribution which includes the Jupyter notebook >> https://www.anaconda.com/download/#linux >> (Version for 3.6) >> >> 3. Pharo 6.1 64 bit >> >> 4. In a playground evaluate >> Metacello new >> baseline: 'JupyterTalk'; >> repository: 'github://jmari/JupyterTalk:master/repository'; >> load:'all' >> >> 5. Hit proceed for skipping the complaint about missing Roassal classes. >> >> 6. Save and quit image --> error message pops up, --> hit proceed. >> >> 7. Restart image. >> >> 8. Start Jupyter on command line with >> >> jupyter notebook >> >> The result is that a browser window is opened which allows to >> connect to the pharo >> kernel (see screen shot) >> >> 9. A crash when opening the new notebook [details below]. >> >> Suggestions how to proceed are welcome! >> >> --Hannes >> >> >> ---------------------------------------------------------------------------------------------------------------- >> The Pharo stack from the debugger >> ---------------------------------------------------------------------------------------------------------------- >> >> ExternalLibraryFunction(Object)>>error: >> ExternalLibraryFunction(Object)>>externalCallFailed >> ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: >> ZmqApi class>>apiZmqVersion:minor:patch: >> FFICalloutAPI>>function:module: >> ZmqApi class(Object)>>ffiCall:module: >> ZmqApi class>>apiZmqVersion:minor:patch: >> ZmqApi class>>version >> ZmqApi class>>forCurrentVersion >> ZmqContext>>initialize >> ZmqContext class(Behavior)>>new >> ZmqContext class>>new >> ZmqContext class>>current >> IPharoCommandLineHandler>>activate >> IPharoCommandLineHandler class(CommandLineHandler class)>>activateWith: >> [ aCommandLinehandler activateWith: commandLine ] in >> PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: >> in Block: [ aCommandLinehandler activateWith: commandLine ] >> BlockClosure>>on:do: >> PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: >> PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand >> PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: >> [ self >> handleArgument: >> (self arguments >> ifEmpty: [ '' ] >> ifNotEmpty: [ :arguments | arguments first ]) ] in >> PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: [ >> self... >> BlockClosure>>on:do: >> PharoCommandLineHandler(BasicCommandLineHandler)>>activate >> PharoCommandLineHandler>>activate >> PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: >> [ super activateWith: aCommandLine ] in PharoCommandLineHandler >> class>>activateWith: in Block: [ super activateWith: aCommandLine ] >> WorldState>>runStepMethodsIn: >> WorldMorph>>runStepMethods >> WorldState>>doOneCycleNowFor: >> WorldState>>doOneCycleFor: >> >

Aug. 22, 2018

Re: [Pharo-users] Jupyter notebooks / Dynabook / JupyterTalk

by H. Hirzel

P.S. Probably noteworthy is that for some reason a second instance of Pharo was opened. Probably by the command jupyter notebook I could close one but after closing the other instance it was opened automatically again. On 8/22/18, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > The installation progressed, success seems to be near, but still a problem > > The process so far: > > 1. Ubuntu 18.04.1 (64bit Bionic beaver) > > 2. Anaconda python distribution which includes the Jupyter notebook > https://www.anaconda.com/download/#linux > (Version for 3.6) > > 3. Pharo 6.1 64 bit > > 4. In a playground evaluate > Metacello new > baseline: 'JupyterTalk'; > repository: 'github://jmari/JupyterTalk:master/repository'; > load:'all' > > 5. Hit proceed for skipping the complaint about missing Roassal classes. > > 6. Save and quit image --> error message pops up, --> hit proceed. > > 7. Restart image. > > 8. Start Jupyter on command line with > > jupyter notebook > > The result is that a browser window is opened which allows to > connect to the pharo > kernel (see screen shot) > > 9. A crash when opening the new notebook [details below]. > > Suggestions how to proceed are welcome! > > --Hannes > > > ---------------------------------------------------------------------------------------------------------------- > The Pharo stack from the debugger > ---------------------------------------------------------------------------------------------------------------- > > ExternalLibraryFunction(Object)>>error: > ExternalLibraryFunction(Object)>>externalCallFailed > ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: > ZmqApi class>>apiZmqVersion:minor:patch: > FFICalloutAPI>>function:module: > ZmqApi class(Object)>>ffiCall:module: > ZmqApi class>>apiZmqVersion:minor:patch: > ZmqApi class>>version > ZmqApi class>>forCurrentVersion > ZmqContext>>initialize > ZmqContext class(Behavior)>>new > ZmqContext class>>new > ZmqContext class>>current > IPharoCommandLineHandler>>activate > IPharoCommandLineHandler class(CommandLineHandler class)>>activateWith: > [ aCommandLinehandler activateWith: commandLine ] in > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: > in Block: [ aCommandLinehandler activateWith: commandLine ] > BlockClosure>>on:do: > PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: > PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand > PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: > [ self > handleArgument: > (self arguments > ifEmpty: [ '' ] > ifNotEmpty: [ :arguments | arguments first ]) ] in > PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: [ > self... > BlockClosure>>on:do: > PharoCommandLineHandler(BasicCommandLineHandler)>>activate > PharoCommandLineHandler>>activate > PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: > [ super activateWith: aCommandLine ] in PharoCommandLineHandler > class>>activateWith: in Block: [ super activateWith: aCommandLine ] > WorldState>>runStepMethodsIn: > WorldMorph>>runStepMethods > WorldState>>doOneCycleNowFor: > WorldState>>doOneCycleFor: >

Aug. 22, 2018

Re: [Pharo-users] Jupyter notebooks / Dynabook / JupyterTalk

by H. Hirzel

The installation progressed, success seems to be near, but still a problem The process so far: 1. Ubuntu 18.04.1 (64bit Bionic beaver) 2. Anaconda python distribution which includes the Jupyter notebook https://www.anaconda.com/download/#linux (Version for 3.6) 3. Pharo 6.1 64 bit 4. In a playground evaluate Metacello new baseline: 'JupyterTalk'; repository: 'github://jmari/JupyterTalk:master/repository'; load:'all' 5. Hit proceed for skipping the complaint about missing Roassal classes. 6. Save and quit image --> error message pops up, --> hit proceed. 7. Restart image. 8. Start Jupyter on command line with jupyter notebook The result is that a browser window is opened which allows to connect to the pharo kernel (see screen shot) 9. A crash when opening the new notebook [details below]. Suggestions how to proceed are welcome! --Hannes ---------------------------------------------------------------------------------------------------------------- The Pharo stack from the debugger ---------------------------------------------------------------------------------------------------------------- ExternalLibraryFunction(Object)>>error: ExternalLibraryFunction(Object)>>externalCallFailed ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: ZmqApi class>>apiZmqVersion:minor:patch: FFICalloutAPI>>function:module: ZmqApi class(Object)>>ffiCall:module: ZmqApi class>>apiZmqVersion:minor:patch: ZmqApi class>>version ZmqApi class>>forCurrentVersion ZmqContext>>initialize ZmqContext class(Behavior)>>new ZmqContext class>>new ZmqContext class>>current IPharoCommandLineHandler>>activate IPharoCommandLineHandler class(CommandLineHandler class)>>activateWith: [ aCommandLinehandler activateWith: commandLine ] in PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: [ aCommandLinehandler activateWith: commandLine ] BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: [ self handleArgument: (self arguments ifEmpty: [ '' ] ifNotEmpty: [ :arguments | arguments first ]) ] in PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: [ self... BlockClosure>>on:do: PharoCommandLineHandler(BasicCommandLineHandler)>>activate PharoCommandLineHandler>>activate PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: [ super activateWith: aCommandLine ] in PharoCommandLineHandler class>>activateWith: in Block: [ super activateWith: aCommandLine ] WorldState>>runStepMethodsIn: WorldMorph>>runStepMethods WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor:

Aug. 22, 2018

Re: [Pharo-users] [Vm-dev] Pharo 6.1 installation problem on Ubuntu 18.04.1 Bionic Beaver

by H. Hirzel

Hello Alistair The 64bit download curl get.pharo.org/64/61+vm | bash did the the job. Thank you. I got to the script I used through http://pharo.org/news/pharo6.1-released (Link from the main page -- http://pharo.org/web !, Read more about here) and I thought it is a kind of generic script whereas it only downloads the 32 bit version. --Hannes On 8/22/18, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Hannes, > > > On Wed, 22 Aug 2018 at 18:48, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> >> >> Hello >> >> I'd like to install Pharo 6.1 in a new installation of >> >> Ubuntu 18.04.1 Bionic Beaver [1] >> >> I get a message >> >> ./pharo-ui >> Error. Could not determine platform's libc path for VM. >> Try forcing $PLATFORMLIBDIR in /home/user25/pharo6.1/pharo-vm/pharo, >> based on LIBC_SO. [2] >> >> Ubuntu 18.04.1 Bionic Beaver is a new installation. The only added sw >> is the Python anaconda distribution. >> https://www.anaconda.com/download/#linux >> >> Suggestions how fix this issue are welcome. >> >> Regards >> Hannes >> >> >> >> [1] http://releases.ubuntu.com/18.04/ >> >> >> [2] The installation sequence >> >> wget -O- get.pharo.org | bash >> >> >> ./pharo-ui >> Error. Could not determine platform's libc path for VM. >> Try forcing $PLATFORMLIBDIR in /home/user25/pharo6.1/pharo-vm/pharo, >> based on LIBC_SO. >> Please report what works to pharo [vm-dev] mail list. >> LIBC_SO= >> DISTRIB_ID=Ubuntu >> DISTRIB_RELEASE=18.04 >> DISTRIB_CODENAME=bionic >> DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" >> NAME="Ubuntu" >> VERSION="18.04.1 LTS (Bionic Beaver)" >> ID=ubuntu >> ID_LIKE=debian >> PRETTY_NAME="Ubuntu 18.04.1 LTS" >> VERSION_ID="18.04" >> VERSION_CODENAME=bionic >> UBUNTU_CODENAME=bionic >> UNAME=Linux Latitude2 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 >> 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux >> System seems to be 64 bit. You may need to (re)install the 32-bit >> libraries. > > As it says, it looks like you don't have the 32 bit libraries > installed (I assume you're on 64 bit Ubuntu). > > Do you really need 32 bit pharo? > > How about: > > curl get.pharo.org/64/61+vm | bash > > > HTH, > Alistair >

Aug. 22, 2018