sys-libs/glibc-2.4 tls/xen-support request <snip> http://wiki.xensource.com/xenwiki/XenSpecificGlibc It is possible to rebuild glibc so that it only uses segments such that there is no performance penalty. To do this, you need to apply the patch below to the glibc sources and then rebuild glibc with the -mno-tls-direct-seg-refs option. This patch is not needed for glibc-2.4. It automatically accesses the segments correctly when it detects that it is compiled with the -mno-tls-direct-seg-refs option. </snip>
Well, you can compile with -mno-tls-direct-seg-refs already in CFLAGS. I don't maintain glibc, so passing this over. As you say, you could just use glibc-2.4.
those fixes are already in glibc-2.3.5 and glibc-2.3.6 http://sourceware.org/ml/glibc-cvs/2005-q1/msg00206.html http://sources.redhat.com/bugzilla/show_bug.cgi?id=737 we arent supporting anything older than 2.3.6 now as for adding -mno-tls-direct-seg-refs to all glibc CFLAGS, the answer is no
ups - spank me - i explained the issue inadequate :( as mentioned in comment #1 we can use 'no-tls-direct' in the cflags - so what a about a einfo in the xen-ebuild howto ...
It's already mentioned in the xen gentoo wiki which you ebuild points you to.
Perhaps something like the following could be added to the glibc ebuild? if [[ -e /proc/xen ]] && ! is-flag -mno-tls-direct-seg-refs; then ewarn "You are using Xen but don't have -mno-tls-direct-seg-refs in your CFLAGS. This will result in a 50% performance penalty, which is probably not what you want."; fi Some people are obviously still tripping over this bug, maybe this would help.
post a diff
added warning to cvs
