- Pharo-users - lists.pharo.org

Re: [Pharo-users] How to make pharo find sqlite?

by phil＠highoctane.be

What about LD_LIBRARY_PATH=<sqlite3place>;$LD_LIBRARYPATH ./pharo-ui some.image Phil On Thu, Sep 28, 2017 at 7:40 PM, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > Hello! > > I try to deploy UDBCSQLite-using image in a 32bit ubuntu 16.04.3. > > I do have libsqlite3: > > root@32bit-agent:~# find / -name '*libsqlite*' -type f 2>>/dev/null > /usr/lib/i386-linux-gnu/libsqlite3.so.0.8.6 > /var/lib/dpkg/info/libsqlite0.list > /var/lib/dpkg/info/libsqlite3-0:i386.postinst > /var/lib/dpkg/info/libsqlite3-0:i386.md5sums > /var/lib/dpkg/info/libsqlite3-0:i386.shlibs > /var/lib/dpkg/info/libsqlite0.postrm > /var/lib/dpkg/info/libsqlite3-0:i386.symbols > /var/lib/dpkg/info/libsqlite3-0:i386.list > /var/lib/dpkg/info/libsqlite3-0:i386.triggers > /var/cache/apt/archives/libsqlite0_2.8.17-12fakesync1_i386.deb > > but I get this in the output of the CI: > > 17:16:54.233 + ../pharo/pharo ./filmtower.image conf/run-tests.st > 17:16:54.508 pthread_setschedparam failed: Operation not permitted > 17:16:54.509 This VM uses a separate heartbeat thread to update its > internal clock > 17:16:54.509 and handle events. For best operation, this thread should > run at a > 17:16:54.509 higher priority, however the VM was unable to change the > priority. The > 17:16:54.509 effect is that heavily loaded systems may experience some > latency > 17:16:54.509 issues. If this occurs, please create the appropriate > configuration > 17:16:54.509 file in /etc/security/limits.d/ as shown below: > 17:16:54.509 > 17:16:54.509 cat <<END | sudo tee /etc/security/limits.d/pharo.conf > 17:16:54.509 * hard rtprio 2 > 17:16:54.509 * soft rtprio 2 > 17:16:54.509 END > 17:16:54.509 > 17:16:54.509 and report to the pharo mailing list whether this improves > behaviour. > 17:16:54.512 > 17:16:54.512 You will need to log out and log back in for the limits to > take effect. > 17:16:54.512 For more information please see > 17:16:54.512 https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/ > tag/r3732#linux > 17:16:54.785 > 17:16:54.786 TowergameSyncTests > 17:16:54.831 Error: External module not found > 17:16:54.832 ExternalLibraryFunction(Object)>>error: > 17:16:54.832 ExternalLibraryFunction(Object)>>externalCallFailed > 17:16:54.833 ExternalLibraryFunction(ExternalFunction)>>invokeWithArgumen > ts: > 17:16:54.833 UDBCSQLite3DatabaseExternalObject > class>>finalizeResourceData: > 17:16:54.834 FFICalloutAPI>>function:module: > 17:16:54.834 UDBCSQLite3Library(Object)>>ffiCall:module: > 17:16:54.835 UDBCSQLite3DatabaseExternalObject > class>>finalizeResourceData: > 17:16:54.836 FFIExternalResourceExecutor>>finalize > 17:16:54.836 WeakFinalizerItem>>finalizeValues > 17:16:54.845 [ each finalizeValues ] in [ :each | [ each finalizeValues ] > on: Exception fork: [ :ex | ex pass ] ] in WeakRegistry>>finalizeValues in > Block: [ each finalizeValues ] > 17:16:54.846 BlockClosure>>on:do: > 17:16:54.852 [ Processor terminateActive ] in [ :ex | > 17:16:54.852 | copy onDoCtx process handler bottom thisCtx | > 17:16:54.852 onDoCtx := thisContext. > 17:16:54.852 thisCtx := onDoCtx home. > 17:16:54.852 > 17:16:54.852 "find the context on stack for which this method's is sender" > 17:16:54.852 [ onDoCtx sender == thisCtx ] > 17:16:54.852 whileFalse: [ onDoCtx := onDoCtx sender. > 17:16:54.852 onDoCtx > 17:16:54.852 ifNil: [ "Can't find our home context. > seems like we're already forked > 17:16:54.852 and handling another exception in > new thread. In this case, just pass it through handler." ^ handlerAction > cull: ex ] ]. > 17:16:54.852 bottom := [ Processor terminateActive ] asContext. > 17:16:54.853 onDoCtx privSender: bottom. > 17:16:54.853 handler := [ handlerAction cull: ex ] asContext. > 17:16:54.853 handler privSender: thisContext sender. > 17:16:54.853 (Process forContext: handler priority: Processor > activePriority) > 17:16:54.853 resume. > 17:16:54.853 > 17:16:54.853 "cut the stack of current process" > 17:16:54.853 thisContext privSender: thisCtx. > 17:16:54.853 nil ] in BlockClosure>>on:fork: in Block: [ Processor > terminateActive ] > 17:16:54.989 > > Look like pharo was not able to find the sqlite3 lib. > > Any help? > > Thanks, Herby > > >

Sept. 28, 2017

Re: [Pharo-users] How to make pharo find sqlite?

by H. Hirzel

Try it with sqlite3-dev installed in addition --Hannes On 9/28/17, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > Hello! > > I try to deploy UDBCSQLite-using image in a 32bit ubuntu 16.04.3. > > I do have libsqlite3: > > root@32bit-agent:~# find / -name '*libsqlite*' -type f 2>>/dev/null > /usr/lib/i386-linux-gnu/libsqlite3.so.0.8.6 > /var/lib/dpkg/info/libsqlite0.list > /var/lib/dpkg/info/libsqlite3-0:i386.postinst > /var/lib/dpkg/info/libsqlite3-0:i386.md5sums > /var/lib/dpkg/info/libsqlite3-0:i386.shlibs > /var/lib/dpkg/info/libsqlite0.postrm > /var/lib/dpkg/info/libsqlite3-0:i386.symbols > /var/lib/dpkg/info/libsqlite3-0:i386.list > /var/lib/dpkg/info/libsqlite3-0:i386.triggers > /var/cache/apt/archives/libsqlite0_2.8.17-12fakesync1_i386.deb > > but I get this in the output of the CI: > > 17:16:54.233 + ../pharo/pharo ./filmtower.image conf/run-tests.st > 17:16:54.508 pthread_setschedparam failed: Operation not permitted > 17:16:54.509 This VM uses a separate heartbeat thread to update its > internal clock > 17:16:54.509 and handle events. For best operation, this thread should > run at a > 17:16:54.509 higher priority, however the VM was unable to change the > priority. The > 17:16:54.509 effect is that heavily loaded systems may experience some > latency > 17:16:54.509 issues. If this occurs, please create the appropriate > configuration > 17:16:54.509 file in /etc/security/limits.d/ as shown below: > 17:16:54.509 > 17:16:54.509 cat <<END | sudo tee /etc/security/limits.d/pharo.conf > 17:16:54.509 * hard rtprio 2 > 17:16:54.509 * soft rtprio 2 > 17:16:54.509 END > 17:16:54.509 > 17:16:54.509 and report to the pharo mailing list whether this improves > behaviour. > 17:16:54.512 > 17:16:54.512 You will need to log out and log back in for the limits to > take effect. > 17:16:54.512 For more information please see > 17:16:54.512 > https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/r3732#linux > 17:16:54.785 > 17:16:54.786 TowergameSyncTests > 17:16:54.831 Error: External module not found > 17:16:54.832 ExternalLibraryFunction(Object)>>error: > 17:16:54.832 ExternalLibraryFunction(Object)>>externalCallFailed > 17:16:54.833 > ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: > 17:16:54.833 UDBCSQLite3DatabaseExternalObject class>>finalizeResourceData: > 17:16:54.834 FFICalloutAPI>>function:module: > 17:16:54.834 UDBCSQLite3Library(Object)>>ffiCall:module: > 17:16:54.835 UDBCSQLite3DatabaseExternalObject class>>finalizeResourceData: > 17:16:54.836 FFIExternalResourceExecutor>>finalize > 17:16:54.836 WeakFinalizerItem>>finalizeValues > 17:16:54.845 [ each finalizeValues ] in [ :each | [ each finalizeValues > ] on: Exception fork: [ :ex | ex pass ] ] in > WeakRegistry>>finalizeValues in Block: [ each finalizeValues ] > 17:16:54.846 BlockClosure>>on:do: > 17:16:54.852 [ Processor terminateActive ] in [ :ex | > 17:16:54.852 | copy onDoCtx process handler bottom thisCtx | > 17:16:54.852 onDoCtx := thisContext. > 17:16:54.852 thisCtx := onDoCtx home. > 17:16:54.852 > 17:16:54.852 "find the context on stack for which this method's is sender" > 17:16:54.852 [ onDoCtx sender == thisCtx ] > 17:16:54.852 whileFalse: [ onDoCtx := onDoCtx sender. > 17:16:54.852 onDoCtx > 17:16:54.852 ifNil: [ "Can't find our home context. seems like we're > already forked > 17:16:54.852 and handling another exception in new thread. In this > case, just pass it through handler." ^ handlerAction cull: ex ] ]. > 17:16:54.852 bottom := [ Processor terminateActive ] asContext. > 17:16:54.853 onDoCtx privSender: bottom. > 17:16:54.853 handler := [ handlerAction cull: ex ] asContext. > 17:16:54.853 handler privSender: thisContext sender. > 17:16:54.853 (Process forContext: handler priority: Processor > activePriority) > 17:16:54.853 resume. > 17:16:54.853 > 17:16:54.853 "cut the stack of current process" > 17:16:54.853 thisContext privSender: thisCtx. > 17:16:54.853 nil ] in BlockClosure>>on:fork: in Block: [ Processor > terminateActive ] > 17:16:54.989 > > Look like pharo was not able to find the sqlite3 lib. > > Any help? > > Thanks, Herby > >

Sept. 28, 2017

Re: [Pharo-users] X11 options on Ubuntu VM / Athens rendering problems

by Igor Stasenko

On 28 September 2017 at 12:43, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi Igor, > > I got libsdl and libcairo 32bits installed fine on 64bits Ubuntu 17.04. > > weird.. > What is your ubuntu system? > > cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.04 DISTRIB_CODENAME=zesty DISTRIB_DESCRIPTION="Ubuntu 17.04" > Hilaire > > > > Le 28/09/2017 Ã 01:22, Igor Stasenko a Ã©crit : > >> something in my installation are in conflict with 32-bit version of >> cairo.. that's weird.. >> but unmet dependencies/dependency conflict resolution of linux .deb >> packages is not my strong side. >> So, it would be nice if someone could help how to proceed with that. >> > > -- > Dr. Geo > http://drgeo.eu > > > > -- Best regards, Igor Stasenko.

Sept. 28, 2017

How to make pharo find sqlite?

by Herby VojÄÃk

Hello! I try to deploy UDBCSQLite-using image in a 32bit ubuntu 16.04.3. I do have libsqlite3: root@32bit-agent:~# find / -name '*libsqlite*' -type f 2>>/dev/null /usr/lib/i386-linux-gnu/libsqlite3.so.0.8.6 /var/lib/dpkg/info/libsqlite0.list /var/lib/dpkg/info/libsqlite3-0:i386.postinst /var/lib/dpkg/info/libsqlite3-0:i386.md5sums /var/lib/dpkg/info/libsqlite3-0:i386.shlibs /var/lib/dpkg/info/libsqlite0.postrm /var/lib/dpkg/info/libsqlite3-0:i386.symbols /var/lib/dpkg/info/libsqlite3-0:i386.list /var/lib/dpkg/info/libsqlite3-0:i386.triggers /var/cache/apt/archives/libsqlite0_2.8.17-12fakesync1_i386.deb but I get this in the output of the CI: 17:16:54.233 + ../pharo/pharo ./filmtower.image conf/run-tests.st 17:16:54.508 pthread_setschedparam failed: Operation not permitted 17:16:54.509 This VM uses a separate heartbeat thread to update its internal clock 17:16:54.509 and handle events. For best operation, this thread should run at a 17:16:54.509 higher priority, however the VM was unable to change the priority. The 17:16:54.509 effect is that heavily loaded systems may experience some latency 17:16:54.509 issues. If this occurs, please create the appropriate configuration 17:16:54.509 file in /etc/security/limits.d/ as shown below: 17:16:54.509 17:16:54.509 cat <<END | sudo tee /etc/security/limits.d/pharo.conf 17:16:54.509 * hard rtprio 2 17:16:54.509 * soft rtprio 2 17:16:54.509 END 17:16:54.509 17:16:54.509 and report to the pharo mailing list whether this improves behaviour. 17:16:54.512 17:16:54.512 You will need to log out and log back in for the limits to take effect. 17:16:54.512 For more information please see 17:16:54.512 https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/r3732#linux 17:16:54.785 17:16:54.786 TowergameSyncTests 17:16:54.831 Error: External module not found 17:16:54.832 ExternalLibraryFunction(Object)>>error: 17:16:54.832 ExternalLibraryFunction(Object)>>externalCallFailed 17:16:54.833 ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: 17:16:54.833 UDBCSQLite3DatabaseExternalObject class>>finalizeResourceData: 17:16:54.834 FFICalloutAPI>>function:module: 17:16:54.834 UDBCSQLite3Library(Object)>>ffiCall:module: 17:16:54.835 UDBCSQLite3DatabaseExternalObject class>>finalizeResourceData: 17:16:54.836 FFIExternalResourceExecutor>>finalize 17:16:54.836 WeakFinalizerItem>>finalizeValues 17:16:54.845 [ each finalizeValues ] in [ :each | [ each finalizeValues ] on: Exception fork: [ :ex | ex pass ] ] in WeakRegistry>>finalizeValues in Block: [ each finalizeValues ] 17:16:54.846 BlockClosure>>on:do: 17:16:54.852 [ Processor terminateActive ] in [ :ex | 17:16:54.852 | copy onDoCtx process handler bottom thisCtx | 17:16:54.852 onDoCtx := thisContext. 17:16:54.852 thisCtx := onDoCtx home. 17:16:54.852 17:16:54.852 "find the context on stack for which this method's is sender" 17:16:54.852 [ onDoCtx sender == thisCtx ] 17:16:54.852 whileFalse: [ onDoCtx := onDoCtx sender. 17:16:54.852 onDoCtx 17:16:54.852 ifNil: [ "Can't find our home context. seems like we're already forked 17:16:54.852 and handling another exception in new thread. In this case, just pass it through handler." ^ handlerAction cull: ex ] ]. 17:16:54.852 bottom := [ Processor terminateActive ] asContext. 17:16:54.853 onDoCtx privSender: bottom. 17:16:54.853 handler := [ handlerAction cull: ex ] asContext. 17:16:54.853 handler privSender: thisContext sender. 17:16:54.853 (Process forContext: handler priority: Processor activePriority) 17:16:54.853 resume. 17:16:54.853 17:16:54.853 "cut the stack of current process" 17:16:54.853 thisContext privSender: thisCtx. 17:16:54.853 nil ] in BlockClosure>>on:fork: in Block: [ Processor terminateActive ] 17:16:54.989 Look like pharo was not able to find the sqlite3 lib. Any help? Thanks, Herby

Sept. 28, 2017

[Demo] Creating Bloc Widgets with Pharo

by Stephan Eggermont

Bloc is ready for your experiments. Here is my first one. Please let me know what and how to improve. Bloc allows for the creation of beautiful widgets. Here is a panel containing collapsible subpanels that can be reordered with drag-and-drop. https://vimeo.com/235934701 Stephan

Sept. 28, 2017

Re: [Pharo-users] X11 options on Ubuntu VM / Athens rendering problems

by Hilaire

Have you tried a full update cycle of your system? apt-get update apt-get dist-upgrade Hilaire Le 28/09/2017 Ã 01:22, Igor Stasenko a Ã©critÂ : > So, it would be nice if someone could help how to proceed with that. -- Dr. Geo http://drgeo.eu

Sept. 28, 2017

Re: [Pharo-users] X11 options on Ubuntu VM / Athens rendering problems

by Hilaire

Hi Igor, I got libsdl and libcairo 32bits installed fine on 64bits Ubuntu 17.04. What is your ubuntu system? Hilaire Le 28/09/2017 Ã 01:22, Igor Stasenko a Ã©critÂ : > something in my installation are in conflict with 32-bit version of > cairo.. that's weird.. > but unmet dependencies/dependency conflict resolution of linux .deb > packages is not my strong side. > So, it would be nice if someone could help how to proceed with that. -- Dr. Geo http://drgeo.eu

Sept. 28, 2017

Re: [Pharo-users] How to include DeployUtils in a Configuration?

by HernÃ¡n Morales Durand

Hi Thierry, Big thanks, with your suggestions I could install my package with the DeployUtils depdendency resolved, and all its dependencies (SystemLogger) also were loaded. I have to modify manually the baseline: method in my config because the Versionner expected a ConfigurationOf to be added as dependency. The ConfigurationOf is in the repository http://www.smalltalkhub.com/#!/~SergeStinckwich/CORMAS Cheers, HernÃ¡n 2017-09-27 4:41 GMT-03:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Hi HernÃ¡n, > > I think what is happening is you're not including completely the DeployUtils > baseline. You need to write something like: > > spec baseline: 'DeployUtils' with: [ > spec repository: 'github://fstephany/DeployUtils/repository']; > import: 'DeployUtils'. > > And have one of the packages (or groups?) of DeployUtils listed as > dependency of one of your packages. > > Regards, > > Thierry > > 2017-09-25 20:19 GMT+02:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: >> >> I am trying to include DeployUtils in a ConfigurationOf (Pharo 6.1) >> following instructions at: >> >> https://github.com/fstephany/DeployUtils >> >> If I include the dependency as suggested: >> >> spec baseline: 'DeployUtils' with: [ >> spec repository: 'github://fstephany/DeployUtils/repository']. >> >> then when I load the configuration I get: >> >> Error: Unable to resolve project package for 'DeployUtils'. It is >> likely that that the configuration referencing this project will not >> validate properly (see MetacelloToolBox >> class>>validateConfiguration:). >> >> If I include the dependency as: >> >> spec >> project: 'DeployUtils' with: [ >> spec >> className: #DeployUtils; >> versionString: 'baseline'; >> repository: >> 'github://fstephany/DeployUtils/repository' ]; >> >> Then I get DU multiple missing dependencies: >> >> This package depends on the following classes: >> StringStreamLogger >> Log >> StdoutStreamLogger >> You must resolve these dependencies before you will be able to load >> these definitions: >> DUFileLogger >> DUFileLogger>>#withFileLocator: >> DUFileLogger>>#addLogHook: >> DUFileLogger>>#defaultFormatter >> DUFileLogger>>#defaultStream >> DUFileLogger>>#fileLocator: >> DUStdoutStreamLogger >> DUStdoutStreamLogger>>#addLogHook: >> Log>>#debug:tag: >> Log>>#info:tag: >> Log>>#warning:tag: >> >> And finally a MNU with >> >> #loader: was sent to nil >> >> (also when I try to inspect I got a #gtInspectorProjectsIn: was sent to >> nil) >> Any ideas? >> Cheers, >> >> HernÃ¡n >> >

Sept. 28, 2017

Re: [Pharo-users] Roasssal not working on Windows with Pharo 6.1

by HernÃ¡n Morales Durand

I couldn't reproduce any problem installing Pharo 6.1 in Windows 8.1 from command line: wget -O- get.pharo.org/61+vm | bash - And then installing Roassal from the Catalog Browser. All the examples ran wiithout problems. Cheers HernÃ¡n 2017-09-23 5:57 GMT-03:00 kmo <voxkmp(a)gmail.com>: > Is it just me or my systems but is there a major problem with Roassal on > Pharo 6.1 on Windows? > > At work on my Windows 7 machine, Roassal installs from the catalog browser > but the examples will not run. I get an error - External module not found. > it seems to be looking for the Surface dll which is definitely present in > the pharo folder. > > On my Windows 10 netbook, Roassal will not even install from the catalog > browser. It starts to install then comes up with an unhelpful "something has > gone wrong" message. > > Roassal still works in Pharo 5. So is this just a 6.1 issue? > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Sept. 28, 2017

Re: [Pharo-users] X11 options on Ubuntu VM / Athens rendering problems

by Igor Stasenko

imo, best what could be done is to forget about 32-bit version and use 64-bit VM & libs, to avoid problems like above. but for that, i need a 64-bit VM/image pair for a start, because one that you gave me is 32-bit.. and hence drags all the trouble with all this .so dependency zoo.. -- Best regards, Igor Stasenko.

Sept. 27, 2017