script may be broken for 64bits. I need to take a look… you can still start the binary directly, as a workaround.
Esteban > On 3 Apr 2017, at 15:35, John Brant <[email protected]> wrote: > > I'm unable to start a linked vm file (ln). I have several vm's, and I link to > the one that I want to use. However, it appears that this no longer works. > With the April 3rd threaded vm on > http://files.pharo.org/vm/pharo-spur64/linux/, I get the following error when > it tries to start: > > ldd: ./lib/pharo/5.0-201704030814/pharo: No such file or directory > Error. Could not determine platform's libc path for VM. > Try forcing $PLATFORMLIBDIR in ./pharo, based on LIBC_SO. > Please report what works to pharo [vm-dev] mail list. > LIBC_SO= > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=16.04 > DISTRIB_CODENAME=xenial > DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" > NAME="Ubuntu" > VERSION="16.04.2 LTS (Xenial Xerus)" > ID=ubuntu > ID_LIKE=debian > PRETTY_NAME="Ubuntu 16.04.2 LTS" > VERSION_ID="16.04" > VERSION_CODENAME=xenial > UBUNTU_CODENAME=xenial > UNAME=Linux p5810.refactoryworkers.com 4.4.0-71-generic #92-Ubuntu SMP Fri > Mar 24 12:59:01 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux > System seems to be 64 bit. You may need to (re)install the 32-bit libraries. > > This worked for the March 10th vm. > > > John Brant >
