On Sat, Apr 11, 2015 at 5:31 AM, Bernardo Ezequiel Contreras <vonbecmann@gmail.com> wrote:

Peter,
��The latest vm (http://files.pharo.org/vm/pharo/linux/latest.zip) in debian wheezy gives you the already know problem

/lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /home/vonbecmann/workspaces/pharo-40/target/pharo)

��that's why you need the vm (https://swing.fit.cvut.cz/jenkins/view/Projects/job/pharo-vm-stable-swing/lastSuccessfulBuild/artifact/pharo-vm-stable-swing.zip) that requires glibc 2.13.

��

Ah, debian stable; I didn't think of that. But does the swing vm support glibc 2.13 _intentionally_ or on accident by just being half a year old? Because it doesn't say that anywhere so as a user I would have no idea of knowing. And since I have debian testing/unstable then I already have glibc 2.19+. And this is why I am that some explanation should be put there.

Peter