Hi, First of all, you are going to the old site (as noticed in the first page), you should be going to pharo.org The problem is not 64 or 32 bit there, is that Debian is still based in an old version of libc. I’m preparing a slave specially for that, but for now, you need to use this VM: http://files.pharo.org/vm/pharo/linux/old-libc/pharovm-ubuntu804.tar.gz Is not the latest one, but will work fine.
cheers, Esteban On 20 May 2014, at 05:50, Ralph Boland <[email protected]> wrote: > I just tried installing pharo 3.0 on Linux Debian wheezy and failed. > > I first went to http://www.pharo-project.org/pharo-download > and downloaded the Linux version. > I unzipped it and attempted to run pharo. > I got the error: > > ralph@m31:~/Pharo$ ./pharo > /home/ralph/Pharo/bin/pharo: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version > `GLIBC_2.15' not found (required by /home/ralph/Pharo/bin/pharo) > > I assume the problem is Pharo is expecting me to have the 64 bit version of > a library and i have the 32 bit version of the > library but I am not sure of that. > > So I tried installing the Ubuntu version (from the same web page) > following the instructions I ran: > > sudo add-apt-repository ppa:pharo/stable > sudo apt-get update > > On the second command I got the errors: > > ... > Hit ftp://ftp.debian.org stable/contrib Translation-en > Hit ftp://ftp.debian.org stable/main Translation-en > Hit ftp://ftp.debian.org stable/non-free Translation-en > Err http://ppa.launchpad.net wheezy/main Sources > 404 Not Found > Err http://ppa.launchpad.net wheezy/main i386 Packages > 404 Not Found > Ign http://ppa.launchpad.net wheezy/main Translation-en_CA > Ign http://ppa.launchpad.net wheezy/main Translation-en > Fetched 129 kB in 4s (30.7 kB/s) > W: Failed to fetch > http://ppa.launchpad.net/pharo/stable/ubuntu/dists/wheezy/main/source/Sources > 404 Not Found > > W: Failed to fetch > http://ppa.launchpad.net/pharo/stable/ubuntu/dists/wheezy/main/binary-i386/Packages > 404 Not Found > > E: Some index files failed to download. They have been ignored, or old ones > used instead. > > The solution is probably obvious to many of you. > If I could be enlightened as to what to do that would be great. > > Thanks > > Ralph Boland > >
