On Mon, Mar 04, 2013 at 01:27:11PM +0100, Damien Cassou wrote: > > I have no idea if it can work, but search for GLIBC_2.15, 2.15, or > GLIBC in the VM source files and replace that with the version of > GLIBC in your system. For example, replace all references of > GLIBC_2.15 by GLIBC_2.11 (the version in Ubuntu 10.04 LTS Lucid).
E.g. if your code is using fallocate64, depending on which version of glibc you linked against it might be linked against fallocate64@@GLIBC_2.11 or fallocate64@@GLIBC_2.15. The decision of which version of the symbol one is using is done at link time. If you want your application to be usable on older versions you will either need to avoid the symbol/method, you link on the oldest system you want support or you are using the lsb-gcc to link binaries that should work on all LSB systems. holger
