[Pharo-dev] Recent VM for Pharo 2 on Ubuntu 8.04
jan.vrany at fit.cvut.cz
Wed Aug 28 06:41:32 EDT 2013
we had similar problems. After a bit of a research, I concluded that
there are basically two options for this sort of GLIBC a problem:
1) Workaround: recompile the VM on the target system, i.e., on
2) Solution: find symbols that introduces that dependency and then
simply not use them in the VM code. This means that you may have
to provide your own implementation of certain C functions
(memset, stat, things like that)
To do so, nm and objdump is your friend.
If I were you, I would go for a workaround.
On 28/08/13 11:25, Sven Van Caekenberghe wrote:
> I asked this question before
> and yes I know that Ubuntu 8.04 is old, but I am really stuck.
> I need to deploy a Pharo #20619 image and I need a VM that works on Ubuntu 8.04 _and_ that is not 'too old' (like Eliot's most recent CogVM where I am getting lots of NB errors as well).
> The problem seems to be the dependency on the glibc 2.11.
> Has anyone successfully solved this issue ?
More information about the Pharo-dev