[Pharo-project] [Pharo-users] Pharo on Fedora 15_64

bblochl at arcor.de bblochl at arcor.de
Mon Jun 13 11:03:31 EDT 2011


 


----- Original Nachricht ----
Von:     Toon Verwaest <toon.verwaest at gmail.com>
An:      pharo-project at lists.gforge.inria.fr
Datum:   13.06.2011 16:33
Betreff: Re: [Pharo-project] [Pharo-users] Pharo on Fedora 15_64

> ls appears to be
> alias ls="ls --color=auto"
> :)
> 
> Now I'm just guessing: you probably didn't install 32-bit support for 
> you machine, so ld-linux.so.2 isn't around; and that's the "interpreter" 
> that's suppose to setup a memory image based on an ELF image (basically 
> unpack the binary into memory so that it can be executed). This is 
> different from 32-bit ELFs than for 64bit ELFs; and since you probably 
> DO have the interpreter for 64 bit, I'm guessing this is the interpreter 
> for 32 bit... on which COG runs anyway ;)
> 
> So in short: find out what the 32bit libs are on fedora and install them.
> 
> A random google search gave me the following. Didn't test it though...
> 
> yum install ld-linux.so.2
> 
> And I don't know why you are trying to run readelf ... but you'll 
> probably have to install that too if you want it ;)
> 
> cheers,
> Toon
> 
> Why are you doing ldd `which ls` anyway?
> 
> On 06/11/2011 10:42 PM, Mariano Martinez Peck wrote:
> >
> >
> > On Sat, Jun 11, 2011 at 10:13 PM, <bblochl at arcor.de 
> > <mailto:bblochl at 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 at 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 at 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 at localhost Pharo-1.2.1-CogOneClick.app]$ readelf -l a.out
> >     bash: readelf: command not found...
> >     [bb at localhost Pharo-1.2.1-CogOneClick.app]$
> >
> >     What to do now??
> >
> >     Regards
> >
> >     B. Blochl
> >
> >
> >
> >
> > -- 
> > Mariano
> > http://marianopeck.wordpress.com
> >
> 
> 


Thanks for answering, Toon!

The problem is already solved. (See my mail from 12.06.2011 22:00)

I argue, that ld-linux.so.2 is not the only missing 32bit lib. But if you can make this shure, it is an interesting result.

Concerning your question: "Why are you doing ldd `which ls` anyway?"
I did not do it, this will be done by the launch of Pharo.sh.

Regards

B. Blochl





More information about the Pharo-dev mailing list