- Pharo-dev - lists.pharo.org

Esteban's ChangeLog week of 13 March 2017

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 13 March 2017 to 19 March 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=13/3/2017&to=19/3/2017 ChangeLog ========= 17 March 2017: -------------- * So, I changed the build process for linux to do what I suggested [here](http://forum.world.st/changing-pharo-packaging-in-linux-td4938906.html). I also prepared the [zeroconf](http://get.pharo.org) scripts, but now I cannot build a VM because there is a problem with latest sources. I hope it will be fixed soon :) * I reverted LD_LIBRARY_PATH I added to [zeroconf](http://get.pharo.org) scripts. There are two reasons for this: * It was bugged. * It will not be necesary as soon as I can build new VMs because we will be distributing a script to execute in linux, with everything prepared there. 15 March 2017: -------------- * I made a new change to [zeroconf](http://get.pharo.org) scripts, this time going back to my location of resources (libraries) on linux. This time, I changed the execution script for linux into something like this: ---- LD_LIBRARY_PATH=$DIR/pharo-vm:$LD_LIBRARY_PATH $DIR/pharo-vm/pharo --nodisplay "$@" ---- this needs to be like that due to the problem with libgit2 dependences, since there is still a possibility that linux will found the incorrect library versions. This matches with the old distribution script, who was adding: ---- LD_LIBRARY_PATH="$PLUGINS:$SVMLLP:${LD_LIBRARY_PATH}" exec $GDB "$BIN/pharo" "$@" ---- so now we will be on track... but still, the "regular" (no zerconf) distribution will not work out of the box, I think we need to change it to the old script in some way. I will think how can we do that without break our current process. 13 March 2017: -------------- * I continued working on [zeroconf](http://get.pharo.org): I added linux threaded VMs. Of course, not as default since it requieres a special configuration, but at least people wanting to use them now can do it. * Continuing with this "administrative" day, I updated [zeroconf](http://get.pharo.org) to use +PharoConsole.exe+ in Windows VM. This will allow windows users to start an image from command line and be able to write to console. Now, to take advantage of this it was necessary to rollback a change I made... like 5 years ago! (it was one of the first workarounds I applied to the image, when we were working on the CI for Pharo). Anyway, the [case: 19832](https://pharo.fogbugz.com/f/cases/19832) is there to fix that. * last post I forget to clarify that I needed to do this update because older VMs didn't work on macOS sierra. * I made some administrative stuff and I updated downloads of Pharo 3.0 and Pharo 4.0 for macOS at [http://files.pharo.org/platform/](http://files.pharo.org/platform/), I also updated the "platform files" for this versions. ... and I also updated the [get-files](http://files.pharo.org/get-files) files for Pharo 3.0. * I started the week tooking some minutes to fix a problem in Catalog I caused when trying to enhance the behaviour between sessions (fix is [case: 19831](https://pharo.fogbugz.com/f/cases/19831)) cheers! Esteban

March 20, 2017

Re: [Pharo-dev] [ANN] PharoNOS

by jan.struz

Hi Stef, what I want, is NativeBoost for Pharo 5+. Because we could do this: primInPortByte: portNumber <primitive: 'primitiveNativeCall' module: 'NativeBoostPlugin' error: errorCode> ^ self nbCallout function: #(uint8 ( uint16 portNumber )) emit: [:gen | | asm result proxy | asm := gen asm. proxy := gen proxy. result := gen reserveTemp. asm pop: asm EDX; "EDX = portNumber" push: asm EDI; "save EDI" mov: result to: asm EDI; "EDI = temp address for result" db: 16rEC; "IN AL, DX" pop: asm EDI. "restore EDI" gen releaseTemps: 1. ]. This is a rewrite of one method from C source(calling asm) in internal SqueakNOSPlugin into NativeBoost Smalltalk code. It calls privileged (kernel mode only) instruction to directly access HW I/O - disk access. I have tried to run it, and it worked fine. However there is one little problem. NativeBoost needs method source, which is stored where? On the disk it wants to access... Solution - the source code can be embedded into compiled method trailer - this is only way to make it work. The first run will generate native code, and replaces the embedded source, so you can't touch the method anymore (at runtime)... so it is not perfect. This is how SqueakNOSPlugin can be removed entirelly. But I'm afraid nobody can play with it in Pharo7 images... ----- Save The World! -- View this message in context: http://forum.world.st/ANN-PharoNOS-tp4939247p4939313.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 19, 2017

Re: [Pharo-dev] [Vm-dev] 64bits Pharo VM for windows

by ClÃ©ment Bera

Thank you very much for doing Nicolas. It is very important for many Pharo users to use Pharo 64 bits on Windows. What are the problems you have when trying to build the VM with the JIT that you don't have when building the stack VM ? Is it about API to make the memory executable, is it about calling conventions ? On Sun, Mar 19, 2017 at 12:14 PM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > > And the appveyor builds are green > https://ci.appveyor.com/project/OpenSmalltalk/vm/build/1.0.579 > > 2017-03-19 17:31 GMT+01:00 Nicolas Cellier <nicolas.cellier.aka.nice@ > gmail.com>: > >> Hi, >> I've built a 64bits pharo.stack.spur VM for windows on my machine, >> and I'm uploading the changes to opensmalltalk-vm in branch >> build_pharo_win32_with_cygwin >> >> If the appveyor job correctly succeed, I will emit a pull request. >> >> The VM does not have the SqueakSSL plugin yet. >> >> The 64bits squeak/pharo.cog.spur JIT for windows is still to come, >> but I did not work on it for a few months... >> One thing at a time. >> >> Let's cross finger >> >> Nicolas >> > > >

March 19, 2017

Re: [Pharo-dev] 64bits Pharo VM for windows

by Nicolas Cellier

And the appveyor builds are green https://ci.appveyor.com/project/OpenSmalltalk/vm/build/1.0.579 2017-03-19 17:31 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > Hi, > I've built a 64bits pharo.stack.spur VM for windows on my machine, > and I'm uploading the changes to opensmalltalk-vm in branch > build_pharo_win32_with_cygwin > > If the appveyor job correctly succeed, I will emit a pull request. > > The VM does not have the SqueakSSL plugin yet. > > The 64bits squeak/pharo.cog.spur JIT for windows is still to come, > but I did not work on it for a few months... > One thing at a time. > > Let's cross finger > > Nicolas >

March 19, 2017

Re: [Pharo-dev] [ANN] PharoNOS

by jan.struz

Hi Damien, I just tried it under Virtualbox. The disk image is RAW format, it should run everywhere, but VB is dumb, you need to convert it first. And the size is not divisible by 512, so can't even convert it with VB tools... qemu-img convert -f raw -O vmdk NOS.img NOS.vmdk But current PharoNOS version supports only "Realtek8139" network card, and I don't see it in Virtualbox... You should set the pointing device to PS/2 (mouse), not USB, but I personally don't see the cursor either then... Docker relies on Linux kernel, but PharoNOS has its own kernel, so you can't run it there. But, if you want, you can use the last link, with statically linked (single binary) version of Pharo Spur VM, which works in Docker! In addition to this, you will need only Pharo image, changes and sources. Regarding the ARM version, Denis, I don't know, there are many inlined assembler x86 instructions, I don't know how virtual memory works on ARM. I think some refactoring is needed first, to support multiple processors. ----- Save The World! -- View this message in context: http://forum.world.st/ANN-PharoNOS-tp4939247p4939295.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 19, 2017

Re: [Pharo-dev] platforms/Nopsys submodule

by Dale Henrichs

If there are discussions about submodules, I would like to participate ... submodules have a lot of the flavor of a ConfigurationOf where a new version needs to be created when the sub-project's version changes - I think I've got that detail right - this cause tight coupling between projects and makes cross-platform usage of such projects nearly impossible... All of this doesn't mean that there aren't specific cases where submodules may make sense ... Dale On 3/18/17 8:24 AM, Guido Chari wrote: > Hi, > > We didn't expect to be found yet :). But well...we are actually > working on a second revival of the SqueakNOS project. Hope to give > news in the mailing list soon, but we are still far from having > something working with all the new stuff. > > Concerning submodules, yes there are plenty of arguments for and > against. I've been using them successfully in some projects depending > on the Truffle/Graal platform. Nonetheless, in case we managed to make > progress and the community is interested on the results, for sure we > will be open to discuss about this. > > Best, > Guido. > > 2017-03-18 10:53 GMT-03:00 Ben Coman <btc(a)openinworld.com > <mailto:btc@openinworld.com>>: > > In the network graph hovering over charig/2-March commit I see a new > platform Nopsys added for SqueakNOS. > [A] https://github.com/OpenSmalltalk/opensmalltalk-vm/network > <https://github.com/OpenSmalltalk/opensmalltalk-vm/network> > > Thats cool !!! It'll be great to see this work with OpenSmalltalk. > However I notice its been added as a submodule. > [B] > https://github.com/charig/opensmalltalk-vm/commit/2bd87b525b6b46439c90506c0… > <https://github.com/charig/opensmalltalk-vm/commit/2bd87b525b6b46439c90506c0…> > > Submodules bring additional complexity, so I thought there should be > some discussion on this topic. > Here are a couple of balanced introductions to submodules... > [C] > http://www.catalyst-au.net/blog/git-submodule-misunderstood-beast-or-remors… > <http://www.catalyst-au.net/blog/git-submodule-misunderstood-beast-or-remors…> > [D] > https://www.philosophicalhacker.com/post/using-git-submodules-effectively/ > <https://www.philosophicalhacker.com/post/using-git-submodules-effectively/> > > And a couple of cautions about using them... > [E] http://slopjong.de/2013/06/04/git-why-submodules-are-evil/ > <http://slopjong.de/2013/06/04/git-why-submodules-are-evil/> > [F] https://rufflewind.com/2017-02-21/quirks-with-submodules > <https://rufflewind.com/2017-02-21/quirks-with-submodules> > > > Guido & Javier, > Have you used submodules successfully elsewhere? > Could you discuss your strategy using a submodule for the platform > code rather than adding directly into the opensmalltalk-vm repository? > > I see your parent repository includes opensmalltalk-vm as a submodule > similar to how I *thought* Pharo was doing it, but wait on comment > from Esteban. . > [G] https://github.com/charig/Nopsys > <https://github.com/charig/Nopsys> > [H] https://github.com/charig/Nopsys/blob/master/.gitmodules > <https://github.com/charig/Nopsys/blob/master/.gitmodules> > So it seems platforms/Nopsys is a sub-sub-module. > > > > Esteban, > I thought that you were using submodules to incorporate > opensmalltlak-vm into the pharo-vm, > but I can't see a .gitmodules file there. > [I] https://github.com/pharo-project/pharo-vm > <https://github.com/pharo-project/pharo-vm> > So did you do it another way, or am I missing something? > Could you report your experience with adding opensmalltalk-vm into the > pharo-vm repository? > > > cheers -ben > >

March 19, 2017

64bits Pharo VM for windows

by Nicolas Cellier

Hi, I've built a 64bits pharo.stack.spur VM for windows on my machine, and I'm uploading the changes to opensmalltalk-vm in branch build_pharo_win32_with_cygwin If the appveyor job correctly succeed, I will emit a pull request. The VM does not have the SqueakSSL plugin yet. The 64bits squeak/pharo.cog.spur JIT for windows is still to come, but I did not work on it for a few months... One thing at a time. Let's cross finger Nicolas

March 19, 2017

Re: [Pharo-dev] [ANN] PharoNOS

by Damien Pollet

Is it specific to KVM, or is it possible to run it on top of different hypervisors? E.g. is it possible to make a demo VirtualBox image, or to launch PharoNOS as a Docker container? On 19 March 2017 at 15:33, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi. > > How difficult it would be to support ARM processor? > > 2017-03-19 0:30 GMT+01:00 jan.struz <public%2Bpharo(a)struz.cz>: > >> Hi, >> I successfully ported SqueakNOS to Pharo, and want to share it with you! >> It works with Pharo 4.0 image, networking included, ping works! >> >> *What is different:* >> - I use my own CMake build file, with "out-of-tree" build support, >> instead of "build.xyz" directories inside source tree + some template >> scripts to build any VM type, but it is not complete... >> - I use MUSL <http://www.musl-libc.org/> instead of GlibC, >> cross-compiling GlibC statically on 64bit for 32bit seems impossible, but >> anyway I use 32bit environment to build it >> - It works with pre-opensmalltalk-vm migration directory structure, so >> the "sync" with latest trunk remains #TODO, or maybe start a new branch >> again from the latest upstream commit should work too >> - freetype is included, but will not load any fonts, since the filesystem >> driver is image-side... so you will need to make new fonts embedded, if you >> want them >> - known issues: image snapshot and fileout are not working, current >> date+time hacked to make fat32 timestamps work >> - revision needed: timer (heartbeat) vs. GC vs. interrupts enable/disable >> - there are even some hacks to image-side methods >> >> *PharoNOS platform directory sources: [pharonos branch]* >> SRC: https://gitlab.com/johnnyzz/pharonos >> >> *VM sources: [dev branch]* >> SRC: https://gitlab.com/johnnyzz/pharo-vm >> - added platform directory, build scripts and CMake templates >> - added VMMaker configs >> >> *Build Environment (32bit) - Docker image repository, with CI:* >> https://gitlab.com/johnnyzz/dev-build >> >> *PharoNOS CI (uses previous Docker image):* >> CI: https://gitlab.com/johnnyzz/pharo-nos-build >> >> *How to run it:* >> You can download fresh disk image from CI and then run: >> (sudo) kvm -hda build/NOS.img -enable-kvm -cpu kvm32 -vga qxl -m 256 >> -netdev tap,id=user.3,ifname=tap2,vhost=on -net >> nic,model=rtl8139,netdev=user.3 -global isa-fdc.driveA= -serial stdio >> >> *One more thing:* >> Statically linked Pharo Spur32 (headless) VM, with only one dependency - >> Linux kernel: >> CI: https://gitlab.com/johnnyzz/pharo-build-static >> Size: 2,4MB (too big?, but Freetype included too!) >> >> enjoy >> >> Jan >> Save The World! >> >> ------------------------------ >> View this message in context: [ANN] PharoNOS >> <http://forum.world.st/ANN-PharoNOS-tp4939247.html> >> Sent from the Pharo Smalltalk Developers mailing list archive >> <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> at >> Nabble.com. >> > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

March 19, 2017

Re: [Pharo-dev] platforms/Nopsys submodule

by Ben Coman

On Sat, Mar 18, 2017 at 11:24 PM, Guido Chari <charig(a)gmail.com> wrote: > Hi, > > We didn't expect to be found yet :). > haHaaa!! *grin* the many eyeballs of opensource strikes again! Hopefully there is some benefit in my poking my nose to learn of Jan's work. Release early, Release often is the mantra on the day. btw, This history page initially confused me... https://gitlab.com/johnnyzz/pharonos/network/pharonos The top five commits (Oct 25 - Nov 3) are Jan's 2016 work. Commit six (Apr 7) and lower is your work from 2011. Its a pain there is nothing to indicate such a jump in time. cheers -ben > But well...we are actually working on a second revival of the SqueakNOS > project. Hope to give news in the mailing list soon, but we are still far > from having something working with all the new stuff. > > Concerning submodules, yes there are plenty of arguments for and against. > I've been using them successfully in some projects depending on the > Truffle/Graal platform. Nonetheless, in case we managed to make progress > and the community is interested on the results, for sure we will be open to > discuss about this. > > Best, > Guido. > > 2017-03-18 10:53 GMT-03:00 Ben Coman <btc(a)openinworld.com>: > >> In the network graph hovering over charig/2-March commit I see a new >> platform Nopsys added for SqueakNOS. >> [A] https://github.com/OpenSmalltalk/opensmalltalk-vm/network >> >> Thats cool !!! It'll be great to see this work with OpenSmalltalk. >> However I notice its been added as a submodule. >> [B] https://github.com/charig/opensmalltalk-vm/commit/2bd87b525b >> 6b46439c90506c0a47e17ea1d5ac93 >> >> Submodules bring additional complexity, so I thought there should be >> some discussion on this topic. >> Here are a couple of balanced introductions to submodules... >> [C] http://www.catalyst-au.net/blog/git-submodule-misunderstood- >> beast-or-remorseless-slavering-monster >> [D] https://www.philosophicalhacker.com/post/using-git-submodule >> s-effectively/ >> >> And a couple of cautions about using them... >> [E] http://slopjong.de/2013/06/04/git-why-submodules-are-evil/ >> [F] https://rufflewind.com/2017-02-21/quirks-with-submodules >> >> >> Guido & Javier, >> Have you used submodules successfully elsewhere? >> Could you discuss your strategy using a submodule for the platform >> code rather than adding directly into the opensmalltalk-vm repository? >> >> I see your parent repository includes opensmalltalk-vm as a submodule >> similar to how I *thought* Pharo was doing it, but wait on comment >> from Esteban. . >> [G] https://github.com/charig/Nopsys >> [H] https://github.com/charig/Nopsys/blob/master/.gitmodules >> So it seems platforms/Nopsys is a sub-sub-module. >> >> cheers -ben >> >> >

March 19, 2017

Re: [Pharo-dev] [ANN] PharoNOS

by Denis Kudriashov

Hi. How difficult it would be to support ARM processor? 2017-03-19 0:30 GMT+01:00 jan.struz <public%2Bpharo(a)struz.cz>: > Hi, > I successfully ported SqueakNOS to Pharo, and want to share it with you! > It works with Pharo 4.0 image, networking included, ping works! > > *What is different:* > - I use my own CMake build file, with "out-of-tree" build support, instead > of "build.xyz" directories inside source tree + some template scripts to > build any VM type, but it is not complete... > - I use MUSL <http://www.musl-libc.org/> instead of GlibC, > cross-compiling GlibC statically on 64bit for 32bit seems impossible, but > anyway I use 32bit environment to build it > - It works with pre-opensmalltalk-vm migration directory structure, so the > "sync" with latest trunk remains #TODO, or maybe start a new branch again > from the latest upstream commit should work too > - freetype is included, but will not load any fonts, since the filesystem > driver is image-side... so you will need to make new fonts embedded, if you > want them > - known issues: image snapshot and fileout are not working, current > date+time hacked to make fat32 timestamps work > - revision needed: timer (heartbeat) vs. GC vs. interrupts enable/disable > - there are even some hacks to image-side methods > > *PharoNOS platform directory sources: [pharonos branch]* > SRC: https://gitlab.com/johnnyzz/pharonos > > *VM sources: [dev branch]* > SRC: https://gitlab.com/johnnyzz/pharo-vm > - added platform directory, build scripts and CMake templates > - added VMMaker configs > > *Build Environment (32bit) - Docker image repository, with CI:* > https://gitlab.com/johnnyzz/dev-build > > *PharoNOS CI (uses previous Docker image):* > CI: https://gitlab.com/johnnyzz/pharo-nos-build > > *How to run it:* > You can download fresh disk image from CI and then run: > (sudo) kvm -hda build/NOS.img -enable-kvm -cpu kvm32 -vga qxl -m 256 > -netdev tap,id=user.3,ifname=tap2,vhost=on -net > nic,model=rtl8139,netdev=user.3 -global isa-fdc.driveA= -serial stdio > > *One more thing:* > Statically linked Pharo Spur32 (headless) VM, with only one dependency - > Linux kernel: > CI: https://gitlab.com/johnnyzz/pharo-build-static > Size: 2,4MB (too big?, but Freetype included too!) > > enjoy > > Jan > Save The World! > > ------------------------------ > View this message in context: [ANN] PharoNOS > <http://forum.world.st/ANN-PharoNOS-tp4939247.html> > Sent from the Pharo Smalltalk Developers mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> at > Nabble.com. >

March 19, 2017