September 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [About Documentation] Teach, Don't Tell / Steve Losh

by Camillo Bruni

I really liked it! thanks for the link :) On 2013-09-04, at 06:34, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Pretty well written piece about real documentation: > > http://stevelosh.com/blog/2013/09/teach-dont-tell/ > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > >

Sept. 4, 2013

Re: [Pharo-dev] OSProcess for Pharo3.0

by David T. Lewis

On Tue, Sep 03, 2013 at 10:51:33PM -0400, David T. Lewis wrote: > On Tue, Sep 03, 2013 at 01:48:46PM +0200, Goubier Thierry wrote: > > > > Le 03/09/2013 13:36, David T. Lewis a ?crit : > > > > > >Can you post the method here first? I'd like to check it on some Squeak > > >images > > >before it goes into the repository. > > > > Here it is (at least an example): > > > > in OSProcess class > > > > isPharo3AndLater > > "Test if we are on Pharo 3.0" > > > > ^ (Smalltalk classNamed: 'SystemVersion') > > ifNil: [ false ] > > ifNotNil: [ :v | v current type = 'Pharo' and: [ v current > > major >= 3 ] ] > > The idea is right, but the details can be a PITA ;-) > > - In Squeak trunk, class SystemVersion exists. But it does not understand #type, so this fails at runtime. > > - There are no implementors of #major in Squeak (but this can be rewritten using #perform:). > > - In Squeak 3.8, #ifNil:ifNotNil: requires a block with no arguments. > > I did not check the other Pharo versions. > > Something like this might work: > > isPharo3AndLater > Smalltalk > at: #SystemVersion > ifPresent: [:cls | ((cls canUnderstand: #type) and: [ cls canUnderstand: #major ]) > ifTrue: [^ cls current type = 'Pharo' and: [ cls current major >= 3 ]]]. > ^false > I am also checking the platform subtype implementation (OSProcess platformSubtype). In Pharo: Smalltalk os subtype ==> 'i686' This reflects the processor type, not the os subtype (it should be 'x86_64' on my PC). Is this intentional? Dave

Sept. 4, 2013

Re: [Pharo-dev] Sound on Ubuntu Problems

by J.F. Rick

Well. I'm not that familiar with these C dependency things. It seems like the i386 ones were not installed. I did "sudo apt-get install libasound2:i386" and "sudo apt-get install libasound2-dev:i386" and "sudo apt-get install libasound2-plugins:i386" to install it. While that seems to have worked to install it, ldd still reports the same dependencies for the *.so files. How do I get it to point to the i386 version? Cheers, Jeff On Wed, Sep 4, 2013 at 1:41 PM, Guillermo Polito <guillermopolito(a)gmail.com>wrote: > Do you have libasound installed for i386? cause the one that outputs ldd > looks like in folder for x86_64 > > > On Wed, Sep 4, 2013 at 1:06 PM, J.F. Rick <self(a)je77.com> wrote: > >> Indeed. Yet the Squeak version does not load either. >> >> Cheers, >> >> Jeff >> >> >> On Wed, Sep 4, 2013 at 12:49 PM, Guillermo Polito < >> guillermopolito(a)gmail.com> wrote: >> >>> I'd say it's pretty strange that the vm-sound-ALSA needs almost >>> nothing... From the code I'd think It'd need to bind against asound [1], as >>> the squeak vm says in >>> >>> libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2 >>> (0x00007f3c507ba000) >>> >>> >>> [1] >>> https://github.com/pharo-project/pharovm/blob/master/platforms/unix/vm-soun… >>> >>> >>> On Wed, Sep 4, 2013 at 12:37 PM, J.F. Rick <self(a)je77.com> wrote: >>> >>>> Thanks. When trying to load the ALSA sound, stderr just reports "could >>>> not find module vm-sound-ALSA". >>>> >>>> Doing an ldd on the vm-sound-ALSA.so included with the Pharo VM, I get: >>>> linux-gate.so.1 => (0xf76e9000) >>>> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7515000) >>>> /lib/ld-linux.so.2 (0xf76ea000) >>>> Doing an ldd on the vm-sound-ALSA.so included with the Squeak VM, I get: >>>> linux-vdso.so.1 => (0x00007fffbdbfe000) >>>> libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2 >>>> (0x00007f3c507ba000) >>>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 >>>> (0x00007f3c503f3000) >>>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 >>>> (0x00007f3c500ee000) >>>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 >>>> (0x00007f3c4feea000) >>>> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 >>>> (0x00007f3c4fccd000) >>>> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 >>>> (0x00007f3c4fac4000) >>>> /lib64/ld-linux-x86-64.so.2 (0x00007f3c50cca000) >>>> There doesn't seem to be anything clearly missing. >>>> >>>> Doing an ldd on the vm-sound-pulse.so included with the Squeak VM, I >>>> get: >>>> linux-gate.so.1 => (0xf7721000) >>>> libpulse-simple.so.0 => not found >>>> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf754f000) >>>> /lib/ld-linux.so.2 (0xf7722000) >>>> >>>> I did try to install the libpulse package (apt-get install >>>> libpulse-dev) but that file is still missing. >>>> >>>> Weirdly enough, doing an ldd on the vm-sound-null.so included with >>>> Pharo, I get: >>>> linux-gate.so.1 => (0xf774c000) >>>> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf757c000) >>>> /lib/ld-linux.so.2 (0xf774d000) >>>> which is the exact same thing as for vm-sound-ALSA.so. So, I would >>>> imagine that if the one worked than the other would. >>>> >>>> Cheers, >>>> >>>> Jeff >>>> >>>> >>>> >>>> On Wed, Sep 4, 2013 at 11:48 AM, Guillermo Polito < >>>> guillermopolito(a)gmail.com> wrote: >>>> >>>>> Hi! >>>>> >>>>> If the modules are not printed, that probably means that they cannot >>>>> be loaded :). (Bah, I assume that by looking at the vm code that does that >>>>> [1]). >>>>> So, first thing you can do is to see the output of stderr. Second, you >>>>> can try to do an ldd [2] to the vm-sound-ALSA.so library to check the >>>>> dependencies and try to get them installed via ap-tget. >>>>> >>>>> Keep us informed :) >>>>> >>>>> Cheers, >>>>> Guille >>>>> >>>>> [1] >>>>> https://github.com/pharo-project/pharovm/blob/e4ccdb38e01578e3569c9c42d2199… >>>>> [2] http://man.yolinux.com/cgi-bin/man2html?cgi_command=ldd >>>>> >>>>> >>>>> On Wed, Sep 4, 2013 at 11:32 AM, Marcus Denker <marcus.denker(a)inria.fr >>>>> > wrote: >>>>> >>>>>> >>>>>> On Sep 4, 2013, at 11:22 AM, J.F. Rick <self(a)je77.com> wrote: >>>>>> >>>>>> Hmm. Did this get sent or was it filtered? It doesn't seem to be in >>>>>> my inbox for the pharo-dev list. >>>>>> >>>>>> >>>>>> It arrivedâ¦ >>>>>> >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Jeff >>>>>> >>>>>> >>>>>> On Tue, Sep 3, 2013 at 5:03 PM, J.F. Rick <self(a)je77.com> wrote: >>>>>> >>>>>>> I'm using Pharo 2.0 on Ubuntu 13.10 and I can't seem to get sound >>>>>>> working. Getting sound to work on Linux seems to be a common problem. While >>>>>>> I've checked the archive for solutions, none of them work for me. I've >>>>>>> investigated a bit and here's what I've found: >>>>>>> >>>>>>> Inside of the /usr/lib/pharo-vm directory, I see the following: >>>>>>> vm-sound-ALSA.so >>>>>>> vm-sound-null.so >>>>>>> vm-sound-pulse.so (I added that based on an archive post that this >>>>>>> would work) >>>>>>> >>>>>>> When I do "pharo -vm-sound-null pharo.image", it works correctly. >>>>>>> When I do "pharo -vm-sound-ALSA pharo.image", it gives me an error >>>>>>> that "could not find module vm-sound-ALSA". >>>>>>> >>>>>>> When I do "pharo-help", I find that the only sound driver available >>>>>>> is "vm-sound-null", though the others are clearly there in the directory. >>>>>>> Is there anything I can do to make the VM acknowledge that the other files >>>>>>> are there? >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Jeff >>>>>>> >>>>>>> -- >>>>>>> Jochen "Jeff" Rick, Ph.D. >>>>>>> http://www.je77.com/ >>>>>>> Skype ID: jochenrick >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Jochen "Jeff" Rick, Ph.D. >>>>>> http://www.je77.com/ >>>>>> Skype ID: jochenrick >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Jochen "Jeff" Rick, Ph.D. >>>> http://www.je77.com/ >>>> Skype ID: jochenrick >>>> >>> >>> >> >> >> -- >> Jochen "Jeff" Rick, Ph.D. >> http://www.je77.com/ >> Skype ID: jochenrick >> > > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

Sept. 4, 2013

Re: [Pharo-dev] Sound on Ubuntu Problems

by Guillermo Polito

Do you have libasound installed for i386? cause the one that outputs ldd looks like in folder for x86_64 On Wed, Sep 4, 2013 at 1:06 PM, J.F. Rick <self(a)je77.com> wrote: > Indeed. Yet the Squeak version does not load either. > > Cheers, > > Jeff > > > On Wed, Sep 4, 2013 at 12:49 PM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> I'd say it's pretty strange that the vm-sound-ALSA needs almost >> nothing... From the code I'd think It'd need to bind against asound [1], as >> the squeak vm says in >> >> libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2 >> (0x00007f3c507ba000) >> >> >> [1] >> https://github.com/pharo-project/pharovm/blob/master/platforms/unix/vm-soun… >> >> >> On Wed, Sep 4, 2013 at 12:37 PM, J.F. Rick <self(a)je77.com> wrote: >> >>> Thanks. When trying to load the ALSA sound, stderr just reports "could >>> not find module vm-sound-ALSA". >>> >>> Doing an ldd on the vm-sound-ALSA.so included with the Pharo VM, I get: >>> linux-gate.so.1 => (0xf76e9000) >>> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7515000) >>> /lib/ld-linux.so.2 (0xf76ea000) >>> Doing an ldd on the vm-sound-ALSA.so included with the Squeak VM, I get: >>> linux-vdso.so.1 => (0x00007fffbdbfe000) >>> libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2 >>> (0x00007f3c507ba000) >>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f3c503f3000) >>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f3c500ee000) >>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 >>> (0x00007f3c4feea000) >>> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 >>> (0x00007f3c4fccd000) >>> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 >>> (0x00007f3c4fac4000) >>> /lib64/ld-linux-x86-64.so.2 (0x00007f3c50cca000) >>> There doesn't seem to be anything clearly missing. >>> >>> Doing an ldd on the vm-sound-pulse.so included with the Squeak VM, I get: >>> linux-gate.so.1 => (0xf7721000) >>> libpulse-simple.so.0 => not found >>> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf754f000) >>> /lib/ld-linux.so.2 (0xf7722000) >>> >>> I did try to install the libpulse package (apt-get install libpulse-dev) >>> but that file is still missing. >>> >>> Weirdly enough, doing an ldd on the vm-sound-null.so included with >>> Pharo, I get: >>> linux-gate.so.1 => (0xf774c000) >>> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf757c000) >>> /lib/ld-linux.so.2 (0xf774d000) >>> which is the exact same thing as for vm-sound-ALSA.so. So, I would >>> imagine that if the one worked than the other would. >>> >>> Cheers, >>> >>> Jeff >>> >>> >>> >>> On Wed, Sep 4, 2013 at 11:48 AM, Guillermo Polito < >>> guillermopolito(a)gmail.com> wrote: >>> >>>> Hi! >>>> >>>> If the modules are not printed, that probably means that they cannot be >>>> loaded :). (Bah, I assume that by looking at the vm code that does that >>>> [1]). >>>> So, first thing you can do is to see the output of stderr. Second, you >>>> can try to do an ldd [2] to the vm-sound-ALSA.so library to check the >>>> dependencies and try to get them installed via ap-tget. >>>> >>>> Keep us informed :) >>>> >>>> Cheers, >>>> Guille >>>> >>>> [1] >>>> https://github.com/pharo-project/pharovm/blob/e4ccdb38e01578e3569c9c42d2199… >>>> [2] http://man.yolinux.com/cgi-bin/man2html?cgi_command=ldd >>>> >>>> >>>> On Wed, Sep 4, 2013 at 11:32 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: >>>> >>>>> >>>>> On Sep 4, 2013, at 11:22 AM, J.F. Rick <self(a)je77.com> wrote: >>>>> >>>>> Hmm. Did this get sent or was it filtered? It doesn't seem to be in my >>>>> inbox for the pharo-dev list. >>>>> >>>>> >>>>> It arrivedâ¦ >>>>> >>>>> >>>>> Cheers, >>>>> >>>>> Jeff >>>>> >>>>> >>>>> On Tue, Sep 3, 2013 at 5:03 PM, J.F. Rick <self(a)je77.com> wrote: >>>>> >>>>>> I'm using Pharo 2.0 on Ubuntu 13.10 and I can't seem to get sound >>>>>> working. Getting sound to work on Linux seems to be a common problem. While >>>>>> I've checked the archive for solutions, none of them work for me. I've >>>>>> investigated a bit and here's what I've found: >>>>>> >>>>>> Inside of the /usr/lib/pharo-vm directory, I see the following: >>>>>> vm-sound-ALSA.so >>>>>> vm-sound-null.so >>>>>> vm-sound-pulse.so (I added that based on an archive post that this >>>>>> would work) >>>>>> >>>>>> When I do "pharo -vm-sound-null pharo.image", it works correctly. >>>>>> When I do "pharo -vm-sound-ALSA pharo.image", it gives me an error >>>>>> that "could not find module vm-sound-ALSA". >>>>>> >>>>>> When I do "pharo-help", I find that the only sound driver available >>>>>> is "vm-sound-null", though the others are clearly there in the directory. >>>>>> Is there anything I can do to make the VM acknowledge that the other files >>>>>> are there? >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Jeff >>>>>> >>>>>> -- >>>>>> Jochen "Jeff" Rick, Ph.D. >>>>>> http://www.je77.com/ >>>>>> Skype ID: jochenrick >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Jochen "Jeff" Rick, Ph.D. >>>>> http://www.je77.com/ >>>>> Skype ID: jochenrick >>>>> >>>>> >>>>> >>>> >>> >>> >>> -- >>> Jochen "Jeff" Rick, Ph.D. >>> http://www.je77.com/ >>> Skype ID: jochenrick >>> >> >> > > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick >

Sept. 4, 2013

Re: [Pharo-dev] Interesting regression on 30366

by Stephan Eggermont

'NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Sep 3 2013 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Sep 3 2013 git@github.com:pharo-project/pharovm.git Commit: 581a11414063fec0e53f047ca90de5e1b6d3b188 Date: 2013-08-28 15:11:08 +0200 By: GuillePolito <guillermopolito(a)gmail.com> Jenkins build #14636 ' Does it different Open test browser, run selected tests: 11287 run, 11258 passes, 12 skipped, 26 expected failures, 3 failures, 0 errors, 0 unexpected passes Failures: ReleaseTest>>#testUnknownProcesses NetNameResolverTest>>#testLocalHostName ProcessTest>>#testHighPriorityOverridesWaitTime Errors: After save-and-quit rerun: 11287 run, 11254 passes, 12 skipped, 26 expected failures, 7 failures, 0 errors, 0 unexpected passes Failures: DelayTest>>#testSemaphore ReleaseTest>>#testUnknownProcesses DelayTest>>#testMultiProcessWaitOnSameDelay NetNameResolverTest>>#testLocalHostName ReleaseTest>>#testObsoleteBehaviors ReleaseTest>>#testObsoleteClasses ProcessTest>>#testHighPriorityOverridesWaitTime Errors:

Sept. 4, 2013

Re: [Pharo-dev] OSProcess for Pharo3.0

by Goubier Thierry

Thanks Henry for the correction. Should I prepare an OSProcess version with all the changes necessary for Pharo3 ? Thierry Le 04/09/2013 04:51, David T. Lewis a Ã©crit : > On Tue, Sep 03, 2013 at 01:48:46PM +0200, Goubier Thierry wrote: >> >> Le 03/09/2013 13:36, David T. Lewis a ?crit : >>> >>> Can you post the method here first? I'd like to check it on some Squeak >>> images >>> before it goes into the repository. >> >> Here it is (at least an example): >> >> in OSProcess class >> >> isPharo3AndLater >> "Test if we are on Pharo 3.0" >> >> ^ (Smalltalk classNamed: 'SystemVersion') >> ifNil: [ false ] >> ifNotNil: [ :v | v current type = 'Pharo' and: [ v current >> major >= 3 ] ] > > The idea is right, but the details can be a PITA ;-) > > - In Squeak trunk, class SystemVersion exists. But it does not understand #type, so this fails at runtime. > > - There are no implementors of #major in Squeak (but this can be rewritten using #perform:). > > - In Squeak 3.8, #ifNil:ifNotNil: requires a block with no arguments. > > I did not check the other Pharo versions. > > Something like this might work: > > isPharo3AndLater > Smalltalk > at: #SystemVersion > ifPresent: [:cls | ((cls canUnderstand: #type) and: [ cls canUnderstand: #major ]) > ifTrue: [^ cls current type = 'Pharo' and: [ cls current major >= 3 ]]]. > ^false > > > Dave > > > > >> >> platformName >> "After Squeak version 3.6, #platformName was moved to SmalltalkImage >> Some >> versions of Pharo move this to OSPlatform and issue deprecation >> warnings >> about the other usages. Then Pharo moved away from OSPlatform and >> deprecated >> its use." >> >> "self platformName" >> >> self isPharo3AndLater >> ifTrue: [ ^ Smalltalk os name ]. >> ^ (((Smalltalk hasClassNamed: #OSPlatform) >> and: [(Smalltalk at: #OSPlatform) >> respondsTo: #platformName]) >> ifTrue: [Smalltalk at: #OSPlatform] >> ifFalse: [((Smalltalk classNamed: 'SmalltalkImage') >> ifNil: [^ Smalltalk osVersion]) current]) >> platformName >> >>> Thanks! >>> Dave >>> >>>> >>>>> Dave >>>>> >>>>> >>>>> >>>>> >>>> >>>> -- >>>> Thierry Goubier >>>> CEA list >>>> Laboratoire des Fondations des Syst?mes Temps R?el Embarqu?s >>>> 91191 Gif sur Yvette Cedex >>>> France >>>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>> >>> >>> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des Syst?mes Temps R?el Embarqu?s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 4, 2013

Re: [Pharo-dev] OSProcess for Pharo3.0

by Goubier Thierry

Le 04/09/2013 11:52, Igor Stasenko a Ã©crit : > I don't understand where the tragedy is.. > you want your production code to work in Pharo 2.0? > Write it to work well in 2.0, don't care about 3.0 or any other future > possible changes. > Want your code to work on bleeding-edge 3.0 image? > Refactor/do the changes to make it work.. leave 2.0 behind. It's very tempting to do that, effectively. Want SmaCC on 3.0? Sorry, I'm only using 2.0, so you're on your own :( Want smart suggestions in Nautilus in 2.0? Sorry, not implemented. > You want both? So, keep 2 separate versions for each version of system. And appreciate how the attitude makes it more complex than it has to be. > You just have to accept that there is no code which will magically stay > compatible with all old and all possible future versions > without any changes. Yes, and its hard enough for people to appreciate any effort made in helping smooth out the transition. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 4, 2013

Re: [Pharo-dev] Sound on Ubuntu Problems

by J.F. Rick

Indeed. Yet the Squeak version does not load either. Cheers, Jeff On Wed, Sep 4, 2013 at 12:49 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > I'd say it's pretty strange that the vm-sound-ALSA needs almost nothing... > From the code I'd think It'd need to bind against asound [1], as the squeak > vm says in > > libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2 > (0x00007f3c507ba000) > > > [1] > https://github.com/pharo-project/pharovm/blob/master/platforms/unix/vm-soun… > > > On Wed, Sep 4, 2013 at 12:37 PM, J.F. Rick <self(a)je77.com> wrote: > >> Thanks. When trying to load the ALSA sound, stderr just reports "could >> not find module vm-sound-ALSA". >> >> Doing an ldd on the vm-sound-ALSA.so included with the Pharo VM, I get: >> linux-gate.so.1 => (0xf76e9000) >> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7515000) >> /lib/ld-linux.so.2 (0xf76ea000) >> Doing an ldd on the vm-sound-ALSA.so included with the Squeak VM, I get: >> linux-vdso.so.1 => (0x00007fffbdbfe000) >> libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2 >> (0x00007f3c507ba000) >> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f3c503f3000) >> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f3c500ee000) >> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 >> (0x00007f3c4feea000) >> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 >> (0x00007f3c4fccd000) >> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 >> (0x00007f3c4fac4000) >> /lib64/ld-linux-x86-64.so.2 (0x00007f3c50cca000) >> There doesn't seem to be anything clearly missing. >> >> Doing an ldd on the vm-sound-pulse.so included with the Squeak VM, I get: >> linux-gate.so.1 => (0xf7721000) >> libpulse-simple.so.0 => not found >> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf754f000) >> /lib/ld-linux.so.2 (0xf7722000) >> >> I did try to install the libpulse package (apt-get install libpulse-dev) >> but that file is still missing. >> >> Weirdly enough, doing an ldd on the vm-sound-null.so included with Pharo, >> I get: >> linux-gate.so.1 => (0xf774c000) >> libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf757c000) >> /lib/ld-linux.so.2 (0xf774d000) >> which is the exact same thing as for vm-sound-ALSA.so. So, I would >> imagine that if the one worked than the other would. >> >> Cheers, >> >> Jeff >> >> >> >> On Wed, Sep 4, 2013 at 11:48 AM, Guillermo Polito < >> guillermopolito(a)gmail.com> wrote: >> >>> Hi! >>> >>> If the modules are not printed, that probably means that they cannot be >>> loaded :). (Bah, I assume that by looking at the vm code that does that >>> [1]). >>> So, first thing you can do is to see the output of stderr. Second, you >>> can try to do an ldd [2] to the vm-sound-ALSA.so library to check the >>> dependencies and try to get them installed via ap-tget. >>> >>> Keep us informed :) >>> >>> Cheers, >>> Guille >>> >>> [1] >>> https://github.com/pharo-project/pharovm/blob/e4ccdb38e01578e3569c9c42d2199… >>> [2] http://man.yolinux.com/cgi-bin/man2html?cgi_command=ldd >>> >>> >>> On Wed, Sep 4, 2013 at 11:32 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: >>> >>>> >>>> On Sep 4, 2013, at 11:22 AM, J.F. Rick <self(a)je77.com> wrote: >>>> >>>> Hmm. Did this get sent or was it filtered? It doesn't seem to be in my >>>> inbox for the pharo-dev list. >>>> >>>> >>>> It arrivedâ¦ >>>> >>>> >>>> Cheers, >>>> >>>> Jeff >>>> >>>> >>>> On Tue, Sep 3, 2013 at 5:03 PM, J.F. Rick <self(a)je77.com> wrote: >>>> >>>>> I'm using Pharo 2.0 on Ubuntu 13.10 and I can't seem to get sound >>>>> working. Getting sound to work on Linux seems to be a common problem. While >>>>> I've checked the archive for solutions, none of them work for me. I've >>>>> investigated a bit and here's what I've found: >>>>> >>>>> Inside of the /usr/lib/pharo-vm directory, I see the following: >>>>> vm-sound-ALSA.so >>>>> vm-sound-null.so >>>>> vm-sound-pulse.so (I added that based on an archive post that this >>>>> would work) >>>>> >>>>> When I do "pharo -vm-sound-null pharo.image", it works correctly. >>>>> When I do "pharo -vm-sound-ALSA pharo.image", it gives me an error >>>>> that "could not find module vm-sound-ALSA". >>>>> >>>>> When I do "pharo-help", I find that the only sound driver available is >>>>> "vm-sound-null", though the others are clearly there in the directory. Is >>>>> there anything I can do to make the VM acknowledge that the other files are >>>>> there? >>>>> >>>>> Cheers, >>>>> >>>>> Jeff >>>>> >>>>> -- >>>>> Jochen "Jeff" Rick, Ph.D. >>>>> http://www.je77.com/ >>>>> Skype ID: jochenrick >>>>> >>>> >>>> >>>> >>>> -- >>>> Jochen "Jeff" Rick, Ph.D. >>>> http://www.je77.com/ >>>> Skype ID: jochenrick >>>> >>>> >>>> >>> >> >> >> -- >> Jochen "Jeff" Rick, Ph.D. >> http://www.je77.com/ >> Skype ID: jochenrick >> > > -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

Sept. 4, 2013

Re: [Pharo-dev] Sound on Ubuntu Problems

by Guillermo Polito

I'd say it's pretty strange that the vm-sound-ALSA needs almost nothing... >From the code I'd think It'd need to bind against asound [1], as the squeak vm says in libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2 (0x00007f3c507ba000) [1] https://github.com/pharo-project/pharovm/blob/master/platforms/unix/vm-soun… On Wed, Sep 4, 2013 at 12:37 PM, J.F. Rick <self(a)je77.com> wrote: > Thanks. When trying to load the ALSA sound, stderr just reports "could not > find module vm-sound-ALSA". > > Doing an ldd on the vm-sound-ALSA.so included with the Pharo VM, I get: > linux-gate.so.1 => (0xf76e9000) > libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7515000) > /lib/ld-linux.so.2 (0xf76ea000) > Doing an ldd on the vm-sound-ALSA.so included with the Squeak VM, I get: > linux-vdso.so.1 => (0x00007fffbdbfe000) > libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2 > (0x00007f3c507ba000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f3c503f3000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f3c500ee000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f3c4feea000) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x00007f3c4fccd000) > librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f3c4fac4000) > /lib64/ld-linux-x86-64.so.2 (0x00007f3c50cca000) > There doesn't seem to be anything clearly missing. > > Doing an ldd on the vm-sound-pulse.so included with the Squeak VM, I get: > linux-gate.so.1 => (0xf7721000) > libpulse-simple.so.0 => not found > libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf754f000) > /lib/ld-linux.so.2 (0xf7722000) > > I did try to install the libpulse package (apt-get install libpulse-dev) > but that file is still missing. > > Weirdly enough, doing an ldd on the vm-sound-null.so included with Pharo, > I get: > linux-gate.so.1 => (0xf774c000) > libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf757c000) > /lib/ld-linux.so.2 (0xf774d000) > which is the exact same thing as for vm-sound-ALSA.so. So, I would imagine > that if the one worked than the other would. > > Cheers, > > Jeff > > > > On Wed, Sep 4, 2013 at 11:48 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Hi! >> >> If the modules are not printed, that probably means that they cannot be >> loaded :). (Bah, I assume that by looking at the vm code that does that >> [1]). >> So, first thing you can do is to see the output of stderr. Second, you >> can try to do an ldd [2] to the vm-sound-ALSA.so library to check the >> dependencies and try to get them installed via ap-tget. >> >> Keep us informed :) >> >> Cheers, >> Guille >> >> [1] >> https://github.com/pharo-project/pharovm/blob/e4ccdb38e01578e3569c9c42d2199… >> [2] http://man.yolinux.com/cgi-bin/man2html?cgi_command=ldd >> >> >> On Wed, Sep 4, 2013 at 11:32 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: >> >>> >>> On Sep 4, 2013, at 11:22 AM, J.F. Rick <self(a)je77.com> wrote: >>> >>> Hmm. Did this get sent or was it filtered? It doesn't seem to be in my >>> inbox for the pharo-dev list. >>> >>> >>> It arrivedâ¦ >>> >>> >>> Cheers, >>> >>> Jeff >>> >>> >>> On Tue, Sep 3, 2013 at 5:03 PM, J.F. Rick <self(a)je77.com> wrote: >>> >>>> I'm using Pharo 2.0 on Ubuntu 13.10 and I can't seem to get sound >>>> working. Getting sound to work on Linux seems to be a common problem. While >>>> I've checked the archive for solutions, none of them work for me. I've >>>> investigated a bit and here's what I've found: >>>> >>>> Inside of the /usr/lib/pharo-vm directory, I see the following: >>>> vm-sound-ALSA.so >>>> vm-sound-null.so >>>> vm-sound-pulse.so (I added that based on an archive post that this >>>> would work) >>>> >>>> When I do "pharo -vm-sound-null pharo.image", it works correctly. >>>> When I do "pharo -vm-sound-ALSA pharo.image", it gives me an error that >>>> "could not find module vm-sound-ALSA". >>>> >>>> When I do "pharo-help", I find that the only sound driver available is >>>> "vm-sound-null", though the others are clearly there in the directory. Is >>>> there anything I can do to make the VM acknowledge that the other files are >>>> there? >>>> >>>> Cheers, >>>> >>>> Jeff >>>> >>>> -- >>>> Jochen "Jeff" Rick, Ph.D. >>>> http://www.je77.com/ >>>> Skype ID: jochenrick >>>> >>> >>> >>> >>> -- >>> Jochen "Jeff" Rick, Ph.D. >>> http://www.je77.com/ >>> Skype ID: jochenrick >>> >>> >>> >> > > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick >

Sept. 4, 2013

Re: [Pharo-dev] specialSelectors

by Nicolas Cellier

In JIT, it makes sense because there are special handling for well known special selectors (#+ #at: #< etc...). 2013/9/4 Igor Stasenko <siguctua(a)gmail.com> > i think you can feel the difference while running interpreter. > With JIT it makes little sense to have special selectors imo. > > > On 4 September 2013 12:31, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > >> Agree, >> My point was to ensure there was no speedup, so it's only a space >> optimization (1 slot saved from literals, times 5000 senders or so per >> selector plus maybe a byte for the send bytecode ?). >> However the arithmetic ops, comparisons, bit ops, at: at:put:, == and >> class special selectors still have some specific speed up, especially in >> COG, so we cannot get rid of specialSelectors alltogether... >> >> >> 2013/9/4 Marcus Denker <marcus.denker(a)inria.fr> >> >>> >>> On Sep 4, 2013, at 12:08 AM, Nicolas Cellier < >>> nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> >>> > I note that #class was removed from specialSelectors (nilled entry) so >>> as to not use the VM hack which fetches the class without sending a message. >>> > Pharo prefers the regular message send. >>> > But next to that entry, there is #blockCopy: which was formerly used >>> for blue book BlockContext. >>> > BlockContext was removed from Pharo... >>> > So that makes two available slots for optimizing most used (sent) >>> messages... >>> > We might choose some candidates and test on some macro benchmark if >>> ever that really makes a difference. >>> >>> I am not sure if optimizations on that level make senseâ¦ >>> >>> Marcus >>> >> >> > > > -- > Best regards, > Igor Stasenko. >

Sept. 4, 2013