[racket] segmentation fault while compiling mzscheme 4.2.5 on Xen environment

> Google turns up Xen-related advice about changing "/lib/tls" to
> "/lib/tls.disabled", other pages about how you shouldn't have to do
> that anymore, and so on. For now, I don't have any explanation for the
> behavior that you're seeing other than the possibility that something
> about thread-local storage doesn't work right at the Xen/OS level.
> Advice from anyone who knows more would be welcome.
>

Supposedly using a xen friendly glibc works better for TLS.
http://wiki.xensource.com/xenwiki/XenSpecificGlibc