June 2011 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo on Fedora 15_64

by Alan Rodas

I dont know exactly if this may be the reason, but, are you running a 64bit version of Fedora right? I had some trouble in the past with pharo and Ubuntu 64bits. I needed the 32 bit libraries to run it. If that is your case try installing the 32 bit libraries. Just in case you are not quite familiar with installing libraries in Fedora, here is a guide http://beginlinux.com/blog/2009/09/installing-32-bit-support-into-64-bit-fe… Hope it helps Cheers -- Alan Rodas Bonjour

June 11, 2011

Re: [Pharo-users] Pharo on Fedora 15_64

by Mariano Martinez Peck

On Sat, Jun 11, 2011 at 10:13 PM, <bblochl(a)arcor.de> wrote: > I actually installed Fedora 15 with GNOME 3 on a AMD-64 a couple of days > back and tried to run Pharo, latest stable version and ran into some > problem: > > [bb@localhost Pharo-1.2.1-CogOneClick.app]$ ./Pharo.sh > ./Pharo.sh: > /home/bb/Pharo/Pharo-1.2.1-CogOneClick.app/Contents/Linux/squeakvm: > /lib/ld-linux.so.2: bad ELF interpreter: Datei oder Verzeichnis nicht > gefunden > ./Pharo.sh: Zeile 16: > /home/bb/Pharo/Pharo-1.2.1-CogOneClick.app/Contents/Linux/squeakvm: Erfolg > [bb@localhost Pharo-1.2.1-CogOneClick.app]$ ldd `which ls` > alias: > ldd: ./alias: Datei oder Verzeichnis nicht gefunden > ls='ls: > ldd: ./ls='ls: Datei oder Verzeichnis nicht gefunden > --color=auto': > ldd: ./--color=auto': Datei oder Verzeichnis nicht gefunden > /bin/ls: > linux-vdso.so.1 => (0x00007fffc7bc8000) > libselinux.so.1 => /lib64/libselinux.so.1 (0x0000003761400000) > librt.so.1 => /lib64/librt.so.1 (0x00007f5c7914b000) > libcap.so.2 => /lib64/libcap.so.2 (0x0000003764400000) > libacl.so.1 => /lib64/libacl.so.1 (0x000000376e800000) > libc.so.6 => /lib64/libc.so.6 (0x00007f5c78db1000) > libdl.so.2 => /lib64/libdl.so.2 (0x00007f5c78bac000) > /lib64/ld-linux-x86-64.so.2 (0x00007f5c79367000) > libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f5c78991000) > libattr.so.1 => /lib64/libattr.so.1 (0x000000376a800000) > [bb@localhost Pharo-1.2.1-CogOneClick.app]$ readelf -l a.out > bash: readelf: command not found... > [bb@localhost Pharo-1.2.1-CogOneClick.app]$ > > What to do now?? > > Regards > > B. Blochl > > -- Mariano http://marianopeck.wordpress.com

June 11, 2011

Re: [Pharo-users] Pharo on Fedora 15_64

by StÃ©phane Ducasse

Hi B. Thanks for trying Pharo and welcome even if the start could be better :) I will let the linuxish pharoers asnwer your question. Stef On Jun 11, 2011, at 10:13 PM, bblochl(a)arcor.de wrote: > I actually installed Fedora 15 with GNOME 3 on a AMD-64 a couple of days back and tried to run Pharo, latest stable version and ran into some problem: > > [bb@localhost Pharo-1.2.1-CogOneClick.app]$ ./Pharo.sh > ./Pharo.sh: /home/bb/Pharo/Pharo-1.2.1-CogOneClick.app/Contents/Linux/squeakvm: /lib/ld-linux.so.2: bad ELF interpreter: Datei oder Verzeichnis nicht gefunden > ./Pharo.sh: Zeile 16: /home/bb/Pharo/Pharo-1.2.1-CogOneClick.app/Contents/Linux/squeakvm: Erfolg > [bb@localhost Pharo-1.2.1-CogOneClick.app]$ ldd `which ls` > alias: > ldd: ./alias: Datei oder Verzeichnis nicht gefunden > ls='ls: > ldd: ./ls='ls: Datei oder Verzeichnis nicht gefunden > --color=auto': > ldd: ./--color=auto': Datei oder Verzeichnis nicht gefunden > /bin/ls: > linux-vdso.so.1 => (0x00007fffc7bc8000) > libselinux.so.1 => /lib64/libselinux.so.1 (0x0000003761400000) > librt.so.1 => /lib64/librt.so.1 (0x00007f5c7914b000) > libcap.so.2 => /lib64/libcap.so.2 (0x0000003764400000) > libacl.so.1 => /lib64/libacl.so.1 (0x000000376e800000) > libc.so.6 => /lib64/libc.so.6 (0x00007f5c78db1000) > libdl.so.2 => /lib64/libdl.so.2 (0x00007f5c78bac000) > /lib64/ld-linux-x86-64.so.2 (0x00007f5c79367000) > libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f5c78991000) > libattr.so.1 => /lib64/libattr.so.1 (0x000000376a800000) > [bb@localhost Pharo-1.2.1-CogOneClick.app]$ readelf -l a.out > bash: readelf: command not found... > [bb@localhost Pharo-1.2.1-CogOneClick.app]$ > > What to do now?? > > Regards > > B. Blochl >

June 11, 2011

Pharo on Fedora 15_64

by bblochl＠arcor.de

I actually installed Fedora 15 with GNOME 3 on a AMD-64 a couple of days back and tried to run Pharo, latest stable version and ran into some problem: [bb@localhost Pharo-1.2.1-CogOneClick.app]$ ./Pharo.sh ./Pharo.sh: /home/bb/Pharo/Pharo-1.2.1-CogOneClick.app/Contents/Linux/squeakvm: /lib/ld-linux.so.2: bad ELF interpreter: Datei oder Verzeichnis nicht gefunden ./Pharo.sh: Zeile 16: /home/bb/Pharo/Pharo-1.2.1-CogOneClick.app/Contents/Linux/squeakvm: Erfolg [bb@localhost Pharo-1.2.1-CogOneClick.app]$ ldd `which ls` alias: ldd: ./alias: Datei oder Verzeichnis nicht gefunden ls='ls: ldd: ./ls='ls: Datei oder Verzeichnis nicht gefunden --color=auto': ldd: ./--color=auto': Datei oder Verzeichnis nicht gefunden /bin/ls: linux-vdso.so.1 => (0x00007fffc7bc8000) libselinux.so.1 => /lib64/libselinux.so.1 (0x0000003761400000) librt.so.1 => /lib64/librt.so.1 (0x00007f5c7914b000) libcap.so.2 => /lib64/libcap.so.2 (0x0000003764400000) libacl.so.1 => /lib64/libacl.so.1 (0x000000376e800000) libc.so.6 => /lib64/libc.so.6 (0x00007f5c78db1000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f5c78bac000) /lib64/ld-linux-x86-64.so.2 (0x00007f5c79367000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f5c78991000) libattr.so.1 => /lib64/libattr.so.1 (0x000000376a800000) [bb@localhost Pharo-1.2.1-CogOneClick.app]$ readelf -l a.out bash: readelf: command not found... [bb@localhost Pharo-1.2.1-CogOneClick.app]$ What to do now?? Regards B. Blochl

June 11, 2011

Re: [Pharo-users] Change an existing method from another project

by laurent laffont

On Sat, Jun 11, 2011 at 6:33 PM, Miguel Moquillon < miguel.moquillon(a)gmail.com> wrote: > Hi, > > I'm going to provide a new way to write unit tests without having prefixed > test methods with the word 'test'. As I don't want to write another unit > test framework, I need to change some methods of SUnit (as well of > Autotest). > Cool Miguel ! Will you use a pragma like <test> <before> <after> ? I want it :) For Autotest don't hesitate to commit directly in Autotest repository. Laurent > Is there any way to do that from an external project without creating a > specific fork of theses projects? > Mig > >

June 11, 2011

Re: [Pharo-users] Change an existing method from another project

by StÃ©phane Ducasse

Miguel please do the following: - Fork and copy and past SUnit and extend it - In the past I modified SUnit and after people complained that it was not the right version and my extensions got lost when we reloaded the latest version of SUnit. So let us invent some new way to write tests :). Stef > Hi, > > I'm going to provide a new way to write unit tests without having prefixed test methods with the word 'test'. As I don't want to write another unit test framework, I need to change some methods of SUnit (as well of Autotest). > Is there any way to do that from an external project without creating a specific fork of theses projects? > > Mig >

June 11, 2011

Change an existing method from another project

by Miguel Moquillon

Hi, I'm going to provide a new way to write unit tests without having prefixed test methods with the word 'test'. As I don't want to write another unit test framework, I need to change some methods of SUnit (as well of Autotest). Is there any way to do that from an external project without creating a specific fork of theses projects? Mig

June 11, 2011

Re: [Pharo-users] Problem installing Magma

by Mariano Martinez Peck

ConfigurationOfOSProcess (used by Magma) was wrong: version440: spec <version: '4.4.2' imports: #('4.4-baseline' )> spec for: #'common' do: [ spec blessing: #'release'. spec description: 'Version 4.4.2'. spec author: 'MiguelCoba'. spec timestamp: '5/29/2011 12:34'. spec package: 'OSProcess' with: 'OSProcess-dtl.61'; package: 'OSProcess-Tests' with: 'OSProcess-Tests-dtl.4'. ]. Now it seems to be fixed: Name: ConfigurationOfOSProcess-mt.16 Author: mt Time: 9 June 2011, 1:28:23.772 pm UUID: 7155a747-e91a-194e-9030-8e211f37b1a9 Ancestors: ConfigurationOfOSProcess-AdrienBarreau.15 - recovered 4.4.0 - added 4.4.2 as stable (like it was in AdrienBarreau.15 in modified #version440) reason: to not break dependent projects assumptions (i.e., version 4.4.0 could not be found anymore) On Fri, Jun 10, 2011 at 5:26 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Nope, the typo is in the ConfigurationOfMagma class, which is looking for a > version 4.4.0 of OSProcess, which actually does not exist :/. > I'll see if I can fix it in a while. > > Guille > > > On Fri, Jun 10, 2011 at 12:19 PM, Alan Rodas <alanrodas(a)gmail.com> wrote: > >> Sorry Mariano, didn't catch you there. >> Do you mean a typo in this sentence? >> >> ((Smalltalk at: #ConfigurationOfMagma) project latestVersion) load >> >> beacause even if I try to use the stable version, it still does not work. >> So >> >> ((Smalltalk at: #ConfigurationOfMagma) project version: #stable) load >> >> gives the same result. >> >> So I don't get where the typo is, although you may be refering to a typo >> somewhere else. >> >> Cheers >> -- >> Alan Rodas Bonjour >> >> > -- Mariano http://marianopeck.wordpress.com

June 10, 2011

Re: [Pharo-users] Problem installing Magma

by Guillermo Polito

Nope, the typo is in the ConfigurationOfMagma class, which is looking for a version 4.4.0 of OSProcess, which actually does not exist :/. I'll see if I can fix it in a while. Guille On Fri, Jun 10, 2011 at 12:19 PM, Alan Rodas <alanrodas(a)gmail.com> wrote: > Sorry Mariano, didn't catch you there. > Do you mean a typo in this sentence? > > ((Smalltalk at: #ConfigurationOfMagma) project latestVersion) load > > beacause even if I try to use the stable version, it still does not work. > So > > ((Smalltalk at: #ConfigurationOfMagma) project version: #stable) load > > gives the same result. > > So I don't get where the typo is, although you may be refering to a typo > somewhere else. > > Cheers > -- > Alan Rodas Bonjour > >

June 10, 2011

Re: [Pharo-users] Problem installing Magma

by Alan Rodas

Sorry Mariano, didn't catch you there. Do you mean a typo in this sentence? ((Smalltalk at: #ConfigurationOfMagma) project latestVersion) load beacause even if I try to use the stable version, it still does not work. So ((Smalltalk at: #ConfigurationOfMagma) project version: #stable) load gives the same result. So I don't get where the typo is, although you may be refering to a typo somewhere else. Cheers -- Alan Rodas Bonjour

June 10, 2011