January 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Vm-dev] FFICallback crashes windows spur i386 vm

by Nicolas Cellier

2017-01-17 19:49 GMT+01:00 Holger Freyther <holger(a)freyther.de>: > > > > On 17 Jan 2017, at 19:43, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > Hi Nicolas, Hi Esteban, > > Hi all, > > > > > > > so is it feasible to insist on clang? The mingw compiler is > ancient, so my preference is to move to clang. If so, could someone update > the HowToBuild to describe the problem with mingw and how to install the > clang-based toolchain? > > > > from cygwin (or cygwin64) shell: > > > > $ i686-w64-mingw32-gcc --version > > i686-w64-mingw32-gcc (GCC) 5.4.0 > > Copyright (C) 2015 Free Software Foundation, Inc. > > This is free software; see the source for copying conditions. There is > NO > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > PURPOSE. > > > maybe I am missing something but GCC 5.4 was released in Summer 2016 and is > still supported. Couldn't it be that the better optimizers in GCC expose an > issue that clang is not capable of exposing (yet?)? > > just my two cents > > holger Hi Holger, maybe... One should compile with -O0 to check if it's really about optimization and retry if it solves anything. If yes, then play the game of selecting each individual optimization option. What I know is that the mingw version of gcc have strange stack management with bytes reserved below alloca which is causing some complications in our implemenation of FFI. Personnally I don't have a clue of the reason behind the difference with linux gcc, so without further information, I tend to perceive such differences as a useless and never-ending-source of complications. I'm speaking for myself, but maybe Eliot has the same feeling. Not sure that it's a great choice to abandon gcc support, but it's quite tempting in those circumstances ;)

Jan. 17, 2017

Re: [Pharo-dev] [Vm-dev] FFICallback crashes windows spur i386 vm

by Holger Freyther

> On 17 Jan 2017, at 19:43, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Nicolas, Hi Esteban, Hi all, > > so is it feasible to insist on clang? The mingw compiler is ancient, so my preference is to move to clang. If so, could someone update the HowToBuild to describe the problem with mingw and how to install the clang-based toolchain? > from cygwin (or cygwin64) shell: > > $ i686-w64-mingw32-gcc --version > i686-w64-mingw32-gcc (GCC) 5.4.0 > Copyright (C) 2015 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. maybe I am missing something but GCC 5.4 was released in Summer 2016 and is still supported. Couldn't it be that the better optimizers in GCC expose an issue that clang is not capable of exposing (yet?)? just my two cents holger

Jan. 17, 2017

Re: [Pharo-dev] [Vm-dev] FFICallback crashes windows spur i386 vm

by Eliot Miranda

Hi Nicolas, Hi Esteban, so is it feasible to insist on clang? The mingw compiler is ancient, so my preference is to move to clang. If so, could someone update the HowToBuild to describe the problem with mingw and how to install the clang-based toolchain? On Tue, Jan 17, 2017 at 6:47 AM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > > I've reproduced the crash in squeak.stack.spur Win32 with latest vm > sources (SHA aa11221d9ebb5d60b0b88a2f1f8e27f19909d718) > This crashing VM is compiled with gcc via ./mvm -f > > The Win64 version passes correctly. But it is compiled with clang by > default. > The Win32 compiled with clang also passes correctly for me. > > The test is translated in pure Alien for purpose of testing on Squeak 5.0 > (see instructions below). > > -------------------------------------------------------------- > > from cygwin (or cygwin64) shell: > > $ i686-w64-mingw32-gcc --version > i686-w64-mingw32-gcc (GCC) 5.4.0 > Copyright (C) 2015 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > $ i686-w64-mingw32-clang --version > clang version 3.8.1 (tags/RELEASE_381/final) > Target: i686-w64-windows-gnu > Thread model: posix > InstalledDir: /usr/bin > > $ x86_64-w64-mingw32-clang --version > clang version 3.8.1 (tags/RELEASE_381/final) > Target: x86_64-w64-windows-gnu > Thread model: posix > InstalledDir: /usr/bin > > -------------------------------------------------------------- > > $ cd build.win32x86/squeak.stack.spur > $ ./mvm -f -- CC=i686-w64-mingw32-clang > > or for 64 bits: > > $ cd build.win64x64/squeak.stack.spur > $ ./mvm -f > > -------------------------------------------------------------- > > $ cat >test.c << END > #include "stdint.h" > int8_t test(int8_t(*function)(int8_t), int8_t value) { > return function(value); > } > END > > $ i686-w64-mingw32-clang -c test.c > $ i686-w64-mingw32-clang -shared -o build/vm/test.dll test.o > $ build/vm/Squeak.exe > > -------------------------------------------------------------- > > then from Smalltalk image with Alien properly loaded (Alien-eem.39): > > Callback>>int8RetInt8: callbackContext regs: regsAlien > <signature: #(int8 (*)(int8))> > ^callbackContext wordResult: > (block value: (regsAlien signedCharAt: 1) asInteger) > > (for now, above method must be compiled in each Callback subclass since we > do not ask Pragma to scan superclass for signatures) > > TestCase subclass: #AlienCallbackSunit > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'Alien-CoreTest' > > AlienCallbackSunit>>createCallback > ^Callback > signature: #(int8 (*)(int8)) > block: [ :value | value ] > > AlienCallbackSunit>>primCall: aCallback int8: aNumber > | r | > (Alien lookup: 'test' inLibrary: 'test.dll') > primFFICallResult: (r := Alien new: 1) > with: aCallback thunk > with: aNumber. > ^(r signedCharAt: 1) asInteger > > AlienCallbackSunit>>test > self > assert: (self primCall: self createCallback int8: 0) > equals: 0 > > AlienCallbackSunit new test. > > > 2017-01-14 2:53 GMT+01:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > >> Hi Aliaksei, >> >> On Jan 13, 2017, at 10:27 AM, Aliaksei Syrel <alex.syrel(a)gmail.com> >> wrote: >> >> Hi >> >> The following code crashes windows spur32 VM without crash.dmp: >> (crashes not only in case of int8, but ulong, int16/32 and so on...) >> >> Callback instantiation: >> >> createCallback >>> ^ FFICallback >>> signature: #(int8 (int8)) >>> block: [ :value | value ] >> >> >> C function: >> >> int8_t test(int8_t(*function)(int8_t), int8_t value) { >>> return function(value); >>> } >> >> >> FFI call: >> >> primCall: aCallback int8: aNumber >>> ^ self ffiCall: #(int8 test(FFICallback aCallback, int8 aNumber)) >> >> >> Test case: >> >> test >>> self >>> assert: (self primCall: self createCallback int8: 0) >>> equals: 0 >> >> >> >> Windows 10. >> VM from today: >> http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386- >> 201701130756-83c0ef1.zip >> Image 60343: >> http://files.pharo.org/image/60/60343.zip >> >> P.S. what is the best place to report FFI / Alien issues? >> >> >> vm-dev >> >> P.P.S Iceberg works >> >> Cheers, >> Alex >> >> > > -- _,,,^..^,,,_ best, Eliot

Jan. 17, 2017

Re: [Pharo-dev] FFICallback crashes windows spur i386 vm

by Nicolas Cellier

I've reproduced the crash in squeak.stack.spur Win32 with latest vm sources (SHA aa11221d9ebb5d60b0b88a2f1f8e27f19909d718) This crashing VM is compiled with gcc via ./mvm -f The Win64 version passes correctly. But it is compiled with clang by default. The Win32 compiled with clang also passes correctly for me. The test is translated in pure Alien for purpose of testing on Squeak 5.0 (see instructions below). -------------------------------------------------------------- from cygwin (or cygwin64) shell: $ i686-w64-mingw32-gcc --version i686-w64-mingw32-gcc (GCC) 5.4.0 Copyright (C) 2015 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ i686-w64-mingw32-clang --version clang version 3.8.1 (tags/RELEASE_381/final) Target: i686-w64-windows-gnu Thread model: posix InstalledDir: /usr/bin $ x86_64-w64-mingw32-clang --version clang version 3.8.1 (tags/RELEASE_381/final) Target: x86_64-w64-windows-gnu Thread model: posix InstalledDir: /usr/bin -------------------------------------------------------------- $ cd build.win32x86/squeak.stack.spur $ ./mvm -f -- CC=i686-w64-mingw32-clang or for 64 bits: $ cd build.win64x64/squeak.stack.spur $ ./mvm -f -------------------------------------------------------------- $ cat >test.c << END #include "stdint.h" int8_t test(int8_t(*function)(int8_t), int8_t value) { return function(value); } END $ i686-w64-mingw32-clang -c test.c $ i686-w64-mingw32-clang -shared -o build/vm/test.dll test.o $ build/vm/Squeak.exe -------------------------------------------------------------- then from Smalltalk image with Alien properly loaded (Alien-eem.39): Callback>>int8RetInt8: callbackContext regs: regsAlien <signature: #(int8 (*)(int8))> ^callbackContext wordResult: (block value: (regsAlien signedCharAt: 1) asInteger) (for now, above method must be compiled in each Callback subclass since we do not ask Pragma to scan superclass for signatures) TestCase subclass: #AlienCallbackSunit instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'Alien-CoreTest' AlienCallbackSunit>>createCallback ^Callback signature: #(int8 (*)(int8)) block: [ :value | value ] AlienCallbackSunit>>primCall: aCallback int8: aNumber | r | (Alien lookup: 'test' inLibrary: 'test.dll') primFFICallResult: (r := Alien new: 1) with: aCallback thunk with: aNumber. ^(r signedCharAt: 1) asInteger AlienCallbackSunit>>test self assert: (self primCall: self createCallback int8: 0) equals: 0 AlienCallbackSunit new test. 2017-01-14 2:53 GMT+01:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > Hi Aliaksei, > > On Jan 13, 2017, at 10:27 AM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > Hi > > The following code crashes windows spur32 VM without crash.dmp: > (crashes not only in case of int8, but ulong, int16/32 and so on...) > > Callback instantiation: > > createCallback >> ^ FFICallback >> signature: #(int8 (int8)) >> block: [ :value | value ] > > > C function: > > int8_t test(int8_t(*function)(int8_t), int8_t value) { >> return function(value); >> } > > > FFI call: > > primCall: aCallback int8: aNumber >> ^ self ffiCall: #(int8 test(FFICallback aCallback, int8 aNumber)) > > > Test case: > > test >> self >> assert: (self primCall: self createCallback int8: 0) >> equals: 0 > > > > Windows 10. > VM from today: > http://files.pharo.org/vm/pharo-spur32/win/pharo-win- > i386-201701130756-83c0ef1.zip > Image 60343: > http://files.pharo.org/image/60/60343.zip > > P.S. what is the best place to report FFI / Alien issues? > > > vm-dev > > P.P.S Iceberg works > > Cheers, > Alex > >

Jan. 17, 2017

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

by Peter Uhnak

Indeed, this looks much more appropriate for my use case. Thanks! Peter On Tue, Jan 17, 2017 at 10:07:26AM +0100, Guillermo Polito wrote: > That looks cool, I put it in my todo :) > > On Tue, Jan 17, 2017 at 3:23 AM, Ben Coman <btc(a)openinworld.com> wrote: > > > > > > > On Mon, Jan 16, 2017 at 11:23 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > On Mon, Jan 16, 2017 at 02:40:36PM +0100, Guillermo Polito wrote: > > >> Hi all, > > >> > > >> First, Peter. Actually, this package is meant for those people using > > >> Snapcraft to install packages. It's like with docker, you need docker to > > >> make it work. Actually I made this not to make it the default way to > > >> distribute pharo, but just because they asked it in the university, it > > is > > >> the default way they want to install new packages in here... > > > > > > I guessed as much, but I am still confused about the sudo requirement > > for installation of new snaps; > > > > I infer from this page that sudo privileges *are* required to install new > > snaps... > > https://www.ubuntu.com/desktop/snappy > > > > > e.g. if I asked our university admin to install snapcraft, it still > > wouldn't help us (or other teachers), because they don't have sudo > > priviledges. > > > (And although an exception can be added from snapcraft, I am not sure > > whether the installation process itself is sandboxed.) > > > Is this correct? > > > > I guess your main issue has been running 32-bit Pharo on 64-bit Linux > > requiring sudo privileges to install 32-bit libs. > > In learning more about snapcraft I discovered AppImage which would seem to > > suit your case. > > It packages application lib dependencies into a compressed CD filesystem > > you downloaded and run without installation. > > > > * http://askubuntu.com/questions/866511/differences- > > between-snaps-appimage-flatpak-and-others > > * https://en.wikipedia.org/wiki/AppImage > > * http://appimage.org/ > > * https://github.com/probonopd/AppImageKit/blob/master/README.md > > * https://plus.google.com/+LinusTorvalds/posts/WyrATKUnmrS > > > > Even for 64-bit Pharo, AppImage could remain a good packing option for a > > case where university machines might not all have SDL libs installed. > > > > cheers -ben > > > > > > > > Thanks, > > > Peter > > > > > > > > >> > > >> Alistair, > > >> - thanks for the typo. Maybe we can force wget as a build dependency? > > >> Like that it will not fail like that ;) > > >> - I'll fix the typos. However, next time could you just open a pull > > >> request? or make an issue? emails tend to get lost (specially in a > > weekend > > >> and with many answers :P) > > >> > > >> Guille > > >> > > >> On Fri, Jan 13, 2017 at 11:35 PM, Alistair Grant <akgrant0710(a)gmail.com > > > > > >> wrote: > > >> > > >> > Never mind, I just saw the "wget not found" error. > > >> > > > >> > Sorry for the noise, > > >> > Alistair > > >> > > > >> > > > >> > On 14 January 2017 at 09:17, Alistair Grant <akgrant0710(a)gmail.com> > > wrote: > > >> > > Hi Guille, > > >> > > > > >> > > Thanks very much for making this available. > > >> > > > > >> > > I'm trying to build the snap and am getting the following error: > > >> > > > > >> > > # snapcraft > > >> > > Loaded local plugin for pharo-build-plugin > > >> > > Skipping pull pharo-sources (already ran) > > >> > > Skipping pull pharo-vm (already ran) > > >> > > Preparing to build pharo-sources > > >> > > Building pharo-sources > > >> > > Preparing to build pharo-vm > > >> > > Building pharo-vm > > >> > > scripts/build.sh > > >> > > + '[' '' = -h ']' > > >> > > + '[' '' = --help ']' > > >> > > + '[' 0 -gt 0 ']' > > >> > > ++ readlink scripts/build.sh > > >> > > + SCRIPT_DIR= > > >> > > + SCRIPT_DIR=scripts/build.sh > > >> > > ++ dirname scripts/build.sh > > >> > > + SCRIPT_DIR=scripts > > >> > > + cd scripts > > >> > > ++ pwd -P > > >> > > + SCRIPT_DIR=/home/pharo/pharo-snapcraft/parts/pharo-vm/ > > build/scripts > > >> > > ++ uname > > >> > > ++ tr '[:upper:]' '[:lower:]' > > >> > > + TMP_OS=linux > > >> > > + [[ {linux} = *darwin* ]] > > >> > > + [[ {linux} = *linux* ]] > > >> > > + OS=linux > > >> > > + cd /home/pharo/pharo-snapcraft/parts/pharo-vm/build/scripts/. > > ./image > > >> > > + ./newImage.sh > > >> > > ++ readlink ./newImage.sh > > >> > > + IMAGE_DIR= > > >> > > + IMAGE_DIR=./newImage.sh > > >> > > ++ dirname ./newImage.sh > > >> > > + IMAGE_DIR=. > > >> > > + cd . > > >> > > ++ pwd -P > > >> > > + IMAGE_DIR=/home/pharo/pharo-snapcraft/parts/pharo-vm/build/image > > >> > > + wget -O- get.pharo.org/50+vm > > >> > > + bash > > >> > > ./newImage.sh: line 12: wget: command not found > > >> > > + echo -e 'LOADING VM MAKER SOURCES INTO IMAGE' > > >> > > LOADING VM MAKER SOURCES INTO IMAGE > > >> > > + set -x > > >> > > + ./pharo Pharo.image > > >> > > /home/pharo/pharo-snapcraft/parts/pharo-vm/build/image/../ > > >> > scripts/LoadVMMaker.st > > >> > > ./newImage.sh: line 16: ./pharo: No such file or directory > > >> > > Command '['/bin/sh', '/tmp/tmpgelke1nt', 'scripts/build.sh']' > > returned > > >> > > non-zero exit status 1 > > >> > > > > >> > > > > >> > > I haven't built the VM before, so it will take me a while to track > > >> > > this down. If this is a common problem with an easy solution I'd > > like > > >> > > to know :-) > > >> > > > > >> > > P.S. In the readme under Installing snapcraft, build-essential > > doesn't > > >> > > have an "s", and git is required, e.g. > > >> > > > > >> > > $ sudo apt install build-essential git > > >> > > > > >> > > Thanks again, > > >> > > Alistair > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > On 13 January 2017 at 21:50, Guillermo Polito < > > guillermopolito(a)gmail.com> > > >> > wrote: > > >> > >> Hi all, > > >> > >> > > >> > >> Just wanted to share this: > > >> > >> > > >> > >> https://github.com/guillep/pharo-snapcraft > > >> > >> > > >> > >> It is basically the code to generate a snap package of the pharo-vm > > >> > using > > >> > >> snapcraft. Using this, the VM is generated and packaged with all > > >> > >> dependencies. This should help in running pharo in different linux > > >> > >> distributions. > > >> > >> > > >> > >> I invite you to check it, report problems and submit fixes. > > >> > >> > > >> > >> Cheers, > > >> > >> Guille > > >> > > > >> > > > > > >

Jan. 17, 2017

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

by Guillermo Polito

That looks cool, I put it in my todo :) On Tue, Jan 17, 2017 at 3:23 AM, Ben Coman <btc(a)openinworld.com> wrote: > > > On Mon, Jan 16, 2017 at 11:23 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > On Mon, Jan 16, 2017 at 02:40:36PM +0100, Guillermo Polito wrote: > >> Hi all, > >> > >> First, Peter. Actually, this package is meant for those people using > >> Snapcraft to install packages. It's like with docker, you need docker to > >> make it work. Actually I made this not to make it the default way to > >> distribute pharo, but just because they asked it in the university, it > is > >> the default way they want to install new packages in here... > > > > I guessed as much, but I am still confused about the sudo requirement > for installation of new snaps; > > I infer from this page that sudo privileges *are* required to install new > snaps... > https://www.ubuntu.com/desktop/snappy > > > e.g. if I asked our university admin to install snapcraft, it still > wouldn't help us (or other teachers), because they don't have sudo > priviledges. > > (And although an exception can be added from snapcraft, I am not sure > whether the installation process itself is sandboxed.) > > Is this correct? > > I guess your main issue has been running 32-bit Pharo on 64-bit Linux > requiring sudo privileges to install 32-bit libs. > In learning more about snapcraft I discovered AppImage which would seem to > suit your case. > It packages application lib dependencies into a compressed CD filesystem > you downloaded and run without installation. > > * http://askubuntu.com/questions/866511/differences- > between-snaps-appimage-flatpak-and-others > * https://en.wikipedia.org/wiki/AppImage > * http://appimage.org/ > * https://github.com/probonopd/AppImageKit/blob/master/README.md > * https://plus.google.com/+LinusTorvalds/posts/WyrATKUnmrS > > Even for 64-bit Pharo, AppImage could remain a good packing option for a > case where university machines might not all have SDL libs installed. > > cheers -ben > > > > > Thanks, > > Peter > > > > > >> > >> Alistair, > >> - thanks for the typo. Maybe we can force wget as a build dependency? > >> Like that it will not fail like that ;) > >> - I'll fix the typos. However, next time could you just open a pull > >> request? or make an issue? emails tend to get lost (specially in a > weekend > >> and with many answers :P) > >> > >> Guille > >> > >> On Fri, Jan 13, 2017 at 11:35 PM, Alistair Grant <akgrant0710(a)gmail.com > > > >> wrote: > >> > >> > Never mind, I just saw the "wget not found" error. > >> > > >> > Sorry for the noise, > >> > Alistair > >> > > >> > > >> > On 14 January 2017 at 09:17, Alistair Grant <akgrant0710(a)gmail.com> > wrote: > >> > > Hi Guille, > >> > > > >> > > Thanks very much for making this available. > >> > > > >> > > I'm trying to build the snap and am getting the following error: > >> > > > >> > > # snapcraft > >> > > Loaded local plugin for pharo-build-plugin > >> > > Skipping pull pharo-sources (already ran) > >> > > Skipping pull pharo-vm (already ran) > >> > > Preparing to build pharo-sources > >> > > Building pharo-sources > >> > > Preparing to build pharo-vm > >> > > Building pharo-vm > >> > > scripts/build.sh > >> > > + '[' '' = -h ']' > >> > > + '[' '' = --help ']' > >> > > + '[' 0 -gt 0 ']' > >> > > ++ readlink scripts/build.sh > >> > > + SCRIPT_DIR= > >> > > + SCRIPT_DIR=scripts/build.sh > >> > > ++ dirname scripts/build.sh > >> > > + SCRIPT_DIR=scripts > >> > > + cd scripts > >> > > ++ pwd -P > >> > > + SCRIPT_DIR=/home/pharo/pharo-snapcraft/parts/pharo-vm/ > build/scripts > >> > > ++ uname > >> > > ++ tr '[:upper:]' '[:lower:]' > >> > > + TMP_OS=linux > >> > > + [[ {linux} = *darwin* ]] > >> > > + [[ {linux} = *linux* ]] > >> > > + OS=linux > >> > > + cd /home/pharo/pharo-snapcraft/parts/pharo-vm/build/scripts/. > ./image > >> > > + ./newImage.sh > >> > > ++ readlink ./newImage.sh > >> > > + IMAGE_DIR= > >> > > + IMAGE_DIR=./newImage.sh > >> > > ++ dirname ./newImage.sh > >> > > + IMAGE_DIR=. > >> > > + cd . > >> > > ++ pwd -P > >> > > + IMAGE_DIR=/home/pharo/pharo-snapcraft/parts/pharo-vm/build/image > >> > > + wget -O- get.pharo.org/50+vm > >> > > + bash > >> > > ./newImage.sh: line 12: wget: command not found > >> > > + echo -e 'LOADING VM MAKER SOURCES INTO IMAGE' > >> > > LOADING VM MAKER SOURCES INTO IMAGE > >> > > + set -x > >> > > + ./pharo Pharo.image > >> > > /home/pharo/pharo-snapcraft/parts/pharo-vm/build/image/../ > >> > scripts/LoadVMMaker.st > >> > > ./newImage.sh: line 16: ./pharo: No such file or directory > >> > > Command '['/bin/sh', '/tmp/tmpgelke1nt', 'scripts/build.sh']' > returned > >> > > non-zero exit status 1 > >> > > > >> > > > >> > > I haven't built the VM before, so it will take me a while to track > >> > > this down. If this is a common problem with an easy solution I'd > like > >> > > to know :-) > >> > > > >> > > P.S. In the readme under Installing snapcraft, build-essential > doesn't > >> > > have an "s", and git is required, e.g. > >> > > > >> > > $ sudo apt install build-essential git > >> > > > >> > > Thanks again, > >> > > Alistair > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > On 13 January 2017 at 21:50, Guillermo Polito < > guillermopolito(a)gmail.com> > >> > wrote: > >> > >> Hi all, > >> > >> > >> > >> Just wanted to share this: > >> > >> > >> > >> https://github.com/guillep/pharo-snapcraft > >> > >> > >> > >> It is basically the code to generate a snap package of the pharo-vm > >> > using > >> > >> snapcraft. Using this, the VM is generated and packaged with all > >> > >> dependencies. This should help in running pharo in different linux > >> > >> distributions. > >> > >> > >> > >> I invite you to check it, report problems and submit fixes. > >> > >> > >> > >> Cheers, > >> > >> Guille > >> > > >> > > > >

Jan. 17, 2017

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

by Ben Coman

On Mon, Jan 16, 2017 at 11:23 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > On Mon, Jan 16, 2017 at 02:40:36PM +0100, Guillermo Polito wrote: >> Hi all, >> >> First, Peter. Actually, this package is meant for those people using >> Snapcraft to install packages. It's like with docker, you need docker to >> make it work. Actually I made this not to make it the default way to >> distribute pharo, but just because they asked it in the university, it is >> the default way they want to install new packages in here... > > I guessed as much, but I am still confused about the sudo requirement for installation of new snaps; I infer from this page that sudo privileges *are* required to install new snaps... https://www.ubuntu.com/desktop/snappy > e.g. if I asked our university admin to install snapcraft, it still wouldn't help us (or other teachers), because they don't have sudo priviledges. > (And although an exception can be added from snapcraft, I am not sure whether the installation process itself is sandboxed.) > Is this correct? I guess your main issue has been running 32-bit Pharo on 64-bit Linux requiring sudo privileges to install 32-bit libs. In learning more about snapcraft I discovered AppImage which would seem to suit your case. It packages application lib dependencies into a compressed CD filesystem you downloaded and run without installation. * http://askubuntu.com/questions/866511/differences-between-snaps-appimage-fl… * https://en.wikipedia.org/wiki/AppImage * http://appimage.org/ * https://github.com/probonopd/AppImageKit/blob/master/README.md * https://plus.google.com/+LinusTorvalds/posts/WyrATKUnmrS Even for 64-bit Pharo, AppImage could remain a good packing option for a case where university machines might not all have SDL libs installed. cheers -ben > > Thanks, > Peter > > >> >> Alistair, >> - thanks for the typo. Maybe we can force wget as a build dependency? >> Like that it will not fail like that ;) >> - I'll fix the typos. However, next time could you just open a pull >> request? or make an issue? emails tend to get lost (specially in a weekend >> and with many answers :P) >> >> Guille >> >> On Fri, Jan 13, 2017 at 11:35 PM, Alistair Grant <akgrant0710(a)gmail.com> >> wrote: >> >> > Never mind, I just saw the "wget not found" error. >> > >> > Sorry for the noise, >> > Alistair >> > >> > >> > On 14 January 2017 at 09:17, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> > > Hi Guille, >> > > >> > > Thanks very much for making this available. >> > > >> > > I'm trying to build the snap and am getting the following error: >> > > >> > > # snapcraft >> > > Loaded local plugin for pharo-build-plugin >> > > Skipping pull pharo-sources (already ran) >> > > Skipping pull pharo-vm (already ran) >> > > Preparing to build pharo-sources >> > > Building pharo-sources >> > > Preparing to build pharo-vm >> > > Building pharo-vm >> > > scripts/build.sh >> > > + '[' '' = -h ']' >> > > + '[' '' = --help ']' >> > > + '[' 0 -gt 0 ']' >> > > ++ readlink scripts/build.sh >> > > + SCRIPT_DIR= >> > > + SCRIPT_DIR=scripts/build.sh >> > > ++ dirname scripts/build.sh >> > > + SCRIPT_DIR=scripts >> > > + cd scripts >> > > ++ pwd -P >> > > + SCRIPT_DIR=/home/pharo/pharo-snapcraft/parts/pharo-vm/build/scripts >> > > ++ uname >> > > ++ tr '[:upper:]' '[:lower:]' >> > > + TMP_OS=linux >> > > + [[ {linux} = *darwin* ]] >> > > + [[ {linux} = *linux* ]] >> > > + OS=linux >> > > + cd /home/pharo/pharo-snapcraft/parts/pharo-vm/build/scripts/../image >> > > + ./newImage.sh >> > > ++ readlink ./newImage.sh >> > > + IMAGE_DIR= >> > > + IMAGE_DIR=./newImage.sh >> > > ++ dirname ./newImage.sh >> > > + IMAGE_DIR=. >> > > + cd . >> > > ++ pwd -P >> > > + IMAGE_DIR=/home/pharo/pharo-snapcraft/parts/pharo-vm/build/image >> > > + wget -O- get.pharo.org/50+vm >> > > + bash >> > > ./newImage.sh: line 12: wget: command not found >> > > + echo -e 'LOADING VM MAKER SOURCES INTO IMAGE' >> > > LOADING VM MAKER SOURCES INTO IMAGE >> > > + set -x >> > > + ./pharo Pharo.image >> > > /home/pharo/pharo-snapcraft/parts/pharo-vm/build/image/../ >> > scripts/LoadVMMaker.st >> > > ./newImage.sh: line 16: ./pharo: No such file or directory >> > > Command '['/bin/sh', '/tmp/tmpgelke1nt', 'scripts/build.sh']' returned >> > > non-zero exit status 1 >> > > >> > > >> > > I haven't built the VM before, so it will take me a while to track >> > > this down. If this is a common problem with an easy solution I'd like >> > > to know :-) >> > > >> > > P.S. In the readme under Installing snapcraft, build-essential doesn't >> > > have an "s", and git is required, e.g. >> > > >> > > $ sudo apt install build-essential git >> > > >> > > Thanks again, >> > > Alistair >> > > >> > > >> > > >> > > >> > > >> > > On 13 January 2017 at 21:50, Guillermo Polito < guillermopolito(a)gmail.com> >> > wrote: >> > >> Hi all, >> > >> >> > >> Just wanted to share this: >> > >> >> > >> https://github.com/guillep/pharo-snapcraft >> > >> >> > >> It is basically the code to generate a snap package of the pharo-vm >> > using >> > >> snapcraft. Using this, the VM is generated and packaged with all >> > >> dependencies. This should help in running pharo in different linux >> > >> distributions. >> > >> >> > >> I invite you to check it, report problems and submit fixes. >> > >> >> > >> Cheers, >> > >> Guille >> > >> > >

Jan. 17, 2017

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

by Guillermo Polito

On Mon, Jan 16, 2017 at 4:23 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > On Mon, Jan 16, 2017 at 02:40:36PM +0100, Guillermo Polito wrote: > > Hi all, > > > > First, Peter. Actually, this package is meant for those people using > > Snapcraft to install packages. It's like with docker, you need docker to > > make it work. Actually I made this not to make it the default way to > > distribute pharo, but just because they asked it in the university, it is > > the default way they want to install new packages in here... > > I guessed as much, but I am still confused about the sudo requirement for > installation of new snaps; > e.g. if I asked our university admin to install snapcraft, it still > wouldn't help us (or other teachers), because they don't have sudo > priviledges. > (And although an exception can be added from snapcraft, I am not sure > whether the installation process itself is sandboxed.) > Is this correct? > I guess so... But I just know the basics I learnt while building the package. BTW, I just enhanced some things: https://github.com/guillep/pharo-snapcraft - fix the typos - fixed build dependencies to make it work in a clean linux box (added cmake, unzip, wget...) - added a travis job to validate that the package can be built ;) > > Thanks, > Peter > > > > > > Alistair, > > - thanks for the typo. Maybe we can force wget as a build dependency? > > Like that it will not fail like that ;) > > - I'll fix the typos. However, next time could you just open a pull > > request? or make an issue? emails tend to get lost (specially in a > weekend > > and with many answers :P) > > > > Guille > > > > On Fri, Jan 13, 2017 at 11:35 PM, Alistair Grant <akgrant0710(a)gmail.com> > > wrote: > > > > > Never mind, I just saw the "wget not found" error. > > > > > > Sorry for the noise, > > > Alistair > > > > > > > > > On 14 January 2017 at 09:17, Alistair Grant <akgrant0710(a)gmail.com> > wrote: > > > > Hi Guille, > > > > > > > > Thanks very much for making this available. > > > > > > > > I'm trying to build the snap and am getting the following error: > > > > > > > > # snapcraft > > > > Loaded local plugin for pharo-build-plugin > > > > Skipping pull pharo-sources (already ran) > > > > Skipping pull pharo-vm (already ran) > > > > Preparing to build pharo-sources > > > > Building pharo-sources > > > > Preparing to build pharo-vm > > > > Building pharo-vm > > > > scripts/build.sh > > > > + '[' '' = -h ']' > > > > + '[' '' = --help ']' > > > > + '[' 0 -gt 0 ']' > > > > ++ readlink scripts/build.sh > > > > + SCRIPT_DIR= > > > > + SCRIPT_DIR=scripts/build.sh > > > > ++ dirname scripts/build.sh > > > > + SCRIPT_DIR=scripts > > > > + cd scripts > > > > ++ pwd -P > > > > + SCRIPT_DIR=/home/pharo/pharo-snapcraft/parts/pharo-vm/ > build/scripts > > > > ++ uname > > > > ++ tr '[:upper:]' '[:lower:]' > > > > + TMP_OS=linux > > > > + [[ {linux} = *darwin* ]] > > > > + [[ {linux} = *linux* ]] > > > > + OS=linux > > > > + cd /home/pharo/pharo-snapcraft/parts/pharo-vm/build/scripts/. > ./image > > > > + ./newImage.sh > > > > ++ readlink ./newImage.sh > > > > + IMAGE_DIR= > > > > + IMAGE_DIR=./newImage.sh > > > > ++ dirname ./newImage.sh > > > > + IMAGE_DIR=. > > > > + cd . > > > > ++ pwd -P > > > > + IMAGE_DIR=/home/pharo/pharo-snapcraft/parts/pharo-vm/build/image > > > > + wget -O- get.pharo.org/50+vm > > > > + bash > > > > ./newImage.sh: line 12: wget: command not found > > > > + echo -e 'LOADING VM MAKER SOURCES INTO IMAGE' > > > > LOADING VM MAKER SOURCES INTO IMAGE > > > > + set -x > > > > + ./pharo Pharo.image > > > > /home/pharo/pharo-snapcraft/parts/pharo-vm/build/image/../ > > > scripts/LoadVMMaker.st > > > > ./newImage.sh: line 16: ./pharo: No such file or directory > > > > Command '['/bin/sh', '/tmp/tmpgelke1nt', 'scripts/build.sh']' > returned > > > > non-zero exit status 1 > > > > > > > > > > > > I haven't built the VM before, so it will take me a while to track > > > > this down. If this is a common problem with an easy solution I'd > like > > > > to know :-) > > > > > > > > P.S. In the readme under Installing snapcraft, build-essential > doesn't > > > > have an "s", and git is required, e.g. > > > > > > > > $ sudo apt install build-essential git > > > > > > > > Thanks again, > > > > Alistair > > > > > > > > > > > > > > > > > > > > > > > > On 13 January 2017 at 21:50, Guillermo Polito < > guillermopolito(a)gmail.com> > > > wrote: > > > >> Hi all, > > > >> > > > >> Just wanted to share this: > > > >> > > > >> https://github.com/guillep/pharo-snapcraft > > > >> > > > >> It is basically the code to generate a snap package of the pharo-vm > > > using > > > >> snapcraft. Using this, the VM is generated and packaged with all > > > >> dependencies. This should help in running pharo in different linux > > > >> distributions. > > > >> > > > >> I invite you to check it, report problems and submit fixes. > > > >> > > > >> Cheers, > > > >> Guille > > > > > > > >

Jan. 16, 2017

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

by Peter Uhnak

On Mon, Jan 16, 2017 at 02:40:36PM +0100, Guillermo Polito wrote: > Hi all, > > First, Peter. Actually, this package is meant for those people using > Snapcraft to install packages. It's like with docker, you need docker to > make it work. Actually I made this not to make it the default way to > distribute pharo, but just because they asked it in the university, it is > the default way they want to install new packages in here... I guessed as much, but I am still confused about the sudo requirement for installation of new snaps; e.g. if I asked our university admin to install snapcraft, it still wouldn't help us (or other teachers), because they don't have sudo priviledges. (And although an exception can be added from snapcraft, I am not sure whether the installation process itself is sandboxed.) Is this correct? Thanks, Peter > > Alistair, > - thanks for the typo. Maybe we can force wget as a build dependency? > Like that it will not fail like that ;) > - I'll fix the typos. However, next time could you just open a pull > request? or make an issue? emails tend to get lost (specially in a weekend > and with many answers :P) > > Guille > > On Fri, Jan 13, 2017 at 11:35 PM, Alistair Grant <akgrant0710(a)gmail.com> > wrote: > > > Never mind, I just saw the "wget not found" error. > > > > Sorry for the noise, > > Alistair > > > > > > On 14 January 2017 at 09:17, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > Hi Guille, > > > > > > Thanks very much for making this available. > > > > > > I'm trying to build the snap and am getting the following error: > > > > > > # snapcraft > > > Loaded local plugin for pharo-build-plugin > > > Skipping pull pharo-sources (already ran) > > > Skipping pull pharo-vm (already ran) > > > Preparing to build pharo-sources > > > Building pharo-sources > > > Preparing to build pharo-vm > > > Building pharo-vm > > > scripts/build.sh > > > + '[' '' = -h ']' > > > + '[' '' = --help ']' > > > + '[' 0 -gt 0 ']' > > > ++ readlink scripts/build.sh > > > + SCRIPT_DIR= > > > + SCRIPT_DIR=scripts/build.sh > > > ++ dirname scripts/build.sh > > > + SCRIPT_DIR=scripts > > > + cd scripts > > > ++ pwd -P > > > + SCRIPT_DIR=/home/pharo/pharo-snapcraft/parts/pharo-vm/build/scripts > > > ++ uname > > > ++ tr '[:upper:]' '[:lower:]' > > > + TMP_OS=linux > > > + [[ {linux} = *darwin* ]] > > > + [[ {linux} = *linux* ]] > > > + OS=linux > > > + cd /home/pharo/pharo-snapcraft/parts/pharo-vm/build/scripts/../image > > > + ./newImage.sh > > > ++ readlink ./newImage.sh > > > + IMAGE_DIR= > > > + IMAGE_DIR=./newImage.sh > > > ++ dirname ./newImage.sh > > > + IMAGE_DIR=. > > > + cd . > > > ++ pwd -P > > > + IMAGE_DIR=/home/pharo/pharo-snapcraft/parts/pharo-vm/build/image > > > + wget -O- get.pharo.org/50+vm > > > + bash > > > ./newImage.sh: line 12: wget: command not found > > > + echo -e 'LOADING VM MAKER SOURCES INTO IMAGE' > > > LOADING VM MAKER SOURCES INTO IMAGE > > > + set -x > > > + ./pharo Pharo.image > > > /home/pharo/pharo-snapcraft/parts/pharo-vm/build/image/../ > > scripts/LoadVMMaker.st > > > ./newImage.sh: line 16: ./pharo: No such file or directory > > > Command '['/bin/sh', '/tmp/tmpgelke1nt', 'scripts/build.sh']' returned > > > non-zero exit status 1 > > > > > > > > > I haven't built the VM before, so it will take me a while to track > > > this down. If this is a common problem with an easy solution I'd like > > > to know :-) > > > > > > P.S. In the readme under Installing snapcraft, build-essential doesn't > > > have an "s", and git is required, e.g. > > > > > > $ sudo apt install build-essential git > > > > > > Thanks again, > > > Alistair > > > > > > > > > > > > > > > > > > On 13 January 2017 at 21:50, Guillermo Polito <guillermopolito(a)gmail.com> > > wrote: > > >> Hi all, > > >> > > >> Just wanted to share this: > > >> > > >> https://github.com/guillep/pharo-snapcraft > > >> > > >> It is basically the code to generate a snap package of the pharo-vm > > using > > >> snapcraft. Using this, the VM is generated and packaged with all > > >> dependencies. This should help in running pharo in different linux > > >> distributions. > > >> > > >> I invite you to check it, report problems and submit fixes. > > >> > > >> Cheers, > > >> Guille > > > >

Jan. 16, 2017

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

by Guillermo Polito

Hi all, First, Peter. Actually, this package is meant for those people using Snapcraft to install packages. It's like with docker, you need docker to make it work. Actually I made this not to make it the default way to distribute pharo, but just because they asked it in the university, it is the default way they want to install new packages in here... Alistair, - thanks for the typo. Maybe we can force wget as a build dependency? Like that it will not fail like that ;) - I'll fix the typos. However, next time could you just open a pull request? or make an issue? emails tend to get lost (specially in a weekend and with many answers :P) Guille On Fri, Jan 13, 2017 at 11:35 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Never mind, I just saw the "wget not found" error. > > Sorry for the noise, > Alistair > > > On 14 January 2017 at 09:17, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Guille, > > > > Thanks very much for making this available. > > > > I'm trying to build the snap and am getting the following error: > > > > # snapcraft > > Loaded local plugin for pharo-build-plugin > > Skipping pull pharo-sources (already ran) > > Skipping pull pharo-vm (already ran) > > Preparing to build pharo-sources > > Building pharo-sources > > Preparing to build pharo-vm > > Building pharo-vm > > scripts/build.sh > > + '[' '' = -h ']' > > + '[' '' = --help ']' > > + '[' 0 -gt 0 ']' > > ++ readlink scripts/build.sh > > + SCRIPT_DIR= > > + SCRIPT_DIR=scripts/build.sh > > ++ dirname scripts/build.sh > > + SCRIPT_DIR=scripts > > + cd scripts > > ++ pwd -P > > + SCRIPT_DIR=/home/pharo/pharo-snapcraft/parts/pharo-vm/build/scripts > > ++ uname > > ++ tr '[:upper:]' '[:lower:]' > > + TMP_OS=linux > > + [[ {linux} = *darwin* ]] > > + [[ {linux} = *linux* ]] > > + OS=linux > > + cd /home/pharo/pharo-snapcraft/parts/pharo-vm/build/scripts/../image > > + ./newImage.sh > > ++ readlink ./newImage.sh > > + IMAGE_DIR= > > + IMAGE_DIR=./newImage.sh > > ++ dirname ./newImage.sh > > + IMAGE_DIR=. > > + cd . > > ++ pwd -P > > + IMAGE_DIR=/home/pharo/pharo-snapcraft/parts/pharo-vm/build/image > > + wget -O- get.pharo.org/50+vm > > + bash > > ./newImage.sh: line 12: wget: command not found > > + echo -e 'LOADING VM MAKER SOURCES INTO IMAGE' > > LOADING VM MAKER SOURCES INTO IMAGE > > + set -x > > + ./pharo Pharo.image > > /home/pharo/pharo-snapcraft/parts/pharo-vm/build/image/../ > scripts/LoadVMMaker.st > > ./newImage.sh: line 16: ./pharo: No such file or directory > > Command '['/bin/sh', '/tmp/tmpgelke1nt', 'scripts/build.sh']' returned > > non-zero exit status 1 > > > > > > I haven't built the VM before, so it will take me a while to track > > this down. If this is a common problem with an easy solution I'd like > > to know :-) > > > > P.S. In the readme under Installing snapcraft, build-essential doesn't > > have an "s", and git is required, e.g. > > > > $ sudo apt install build-essential git > > > > Thanks again, > > Alistair > > > > > > > > > > > > On 13 January 2017 at 21:50, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > >> Hi all, > >> > >> Just wanted to share this: > >> > >> https://github.com/guillep/pharo-snapcraft > >> > >> It is basically the code to generate a snap package of the pharo-vm > using > >> snapcraft. Using this, the VM is generated and packaged with all > >> dependencies. This should help in running pharo in different linux > >> distributions. > >> > >> I invite you to check it, report problems and submit fixes. > >> > >> Cheers, > >> Guille > >

Jan. 16, 2017