In Pharo 6's bin/pharo script, there is the following comment:
# On some linuxes there multiple versions of the C library. If the image uses
# libc (e.g. through the FFI) then it must use the same version that the VM uses
# and so it should take precedence over /lib libc. This is done by setting
# LD_LIBRARY_PATH appropriately, based on ldd's idea of the libc use by the VM
My background story is I want to run Pharo 6, needing glibc > 2.15, in CentOS 6 that has glibc 2.12. I've built and installed 2.17 locally. (in another email thread Esteban has provided a better solution, which I haven't tried).
I'm not sure if the comment is only referring to 32-bit and 64-bit versions or different glibc versions. Is it intended for user to be able to use different C library versions, as in glibc 2.15 vs 2.17 vs. 2.19?
If it is, I claim it does not work and I'm curious if there is desire to support it. (It isn't an issue anymore for me and I can share my story how I got it to work. It isn't a clean way by any means, but hopefully it provides enough information)
--
Andreas
Locked
