All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Long <nikarul@gmail.com>
Cc: Nils Toedtmann <xen-devel@nils.toedtmann.net>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: glibc patch for TLS?
Date: Mon, 25 Apr 2005 11:47:30 -0500	[thread overview]
Message-ID: <95cbc489050425094750817c69@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3D25@liverpoolst.ad.cl.cam.ac.uk>

Nope, that's what I forgot.  I recompiled the patched glibc with that
flag and everything seems to be working fine.  I can post the ebuild
if people are interested.  It's pretty straightforward, just adding
the patch and making for the CFLAGS get set properly.

I'm now compiling all my packages with -mno-tls-direct-seg-refs.  Is
this necessary/recommended?  I know some ebuild strip out CFLAGS it's
unsure of, so if it's necessary other packages may need to be
modified.

On 4/24/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> 
> 
> > I pulled out the glibc-xen-tls.patch file and applied it to
> > Gentoo's glibc-2.3.5.  It compiled and installed, but when I
> > reboot into Xen, I still get the emulation warning.  Should
> > it autodetect that the patch is there, or is there something
> > I need to do to disable the check in Xen in order to test the patch?
> 
> Did you remember to build glibc with "-mno-tls-direct-seg-refs" ?
> 
> Ian
>

  reply	other threads:[~2005-04-25 16:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-24  9:07 glibc patch for TLS? Ian Pratt
2005-04-25 16:47 ` Michael Long [this message]
2005-04-26  2:01   ` Edward Middleton
  -- strict thread matches above, loose matches on Subject: below --
2005-04-25 20:57 Ian Pratt
2005-04-25 23:51 ` Michael Long
2005-04-26 11:32   ` Måns Rullgård
2005-04-26  7:28 ` Nils Toedtmann
2005-04-26 14:53   ` Michael Long
2005-04-21  5:28 Michael Long
2005-04-21 11:31 ` Nils Toedtmann
2005-04-24  3:33   ` Michael Long

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=95cbc489050425094750817c69@mail.gmail.com \
    --to=nikarul@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-devel@nils.toedtmann.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.