From: Michael Long <nikarul@gmail.com>
To: Nils Toedtmann <xen-devel@nils.toedtmann.net>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: glibc patch for TLS?
Date: Tue, 26 Apr 2005 09:53:12 -0500 [thread overview]
Message-ID: <95cbc489050426075336fc328b@mail.gmail.com> (raw)
In-Reply-To: <1114500495.11017.6.camel@tpol.nils.toedtmann.net>
On 4/26/05, Nils Toedtmann <xen-devel@nils.toedtmann.net> wrote:
> Am Montag, den 25.04.2005, 21:57 +0100 schrieb Ian Pratt:
> >
> > > 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.
>
> Now it's really cool to run a source distro like gentoo. I wonder if you
> can bootstrap it with that CFLAGS?
I don't see why not. I was able to build the base system packages
(using 'emerge system') on my build system without any apparent
problems. Glibc strips out unknown CFLAGS though, so you have to have
a modified ebuild that makes sure it uses it (bootstrapping or not).
-Michael
next prev parent reply other threads:[~2005-04-26 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 20:57 glibc patch for TLS? 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-24 9:07 Ian Pratt
2005-04-25 16:47 ` Michael Long
2005-04-26 2:01 ` Edward Middleton
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=95cbc489050426075336fc328b@mail.gmail.com \
--to=nikarul@gmail.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.