public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drow at sources dot redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug linuxthreads/674] Error compiling linuxthreads in glibc 2.3.4
Date: Wed, 26 Apr 2006 15:13:00 -0000	[thread overview]
Message-ID: <20060426151337.29805.qmail@sourceware.org> (raw)
In-Reply-To: <20050117073135.674.andihartmann@freenet.de>


------- Additional Comments From drow at sources dot redhat dot com  2006-04-26 15:13 -------
More relevant for the original report:
  http://sourceware.org/ml/libc-ports/2006-04/msg00039.html

I won't fix it, but someone else is welcome to.  You don't want to export _errno
in this case.  Rather, you want to separate the TLS bits that make LinuxThreads
use floating stacks from the TLS bits that say to get errno from libc.so using
TLS.  The pointer/stack guard stuff should also be conditioned on "really have
TLS" rather than "using floating stacks".

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=674

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2006-04-26 15:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-17  7:31 [Bug linuxthreads/674] New: " andihartmann at freenet dot de
2005-01-31 23:12 ` [Bug linuxthreads/674] " nix at esperi dot org dot uk
2005-02-01 11:20 ` nix at esperi dot org dot uk
2005-02-01 20:58 ` nix at esperi dot org dot uk
2005-02-02  7:57 ` nix at esperi dot org dot uk
2005-09-16 14:52 ` drepper at redhat dot com
2006-04-25  0:23 ` vapier at gentoo dot org
2006-04-25 23:20 ` vapier at gentoo dot org
2006-04-26 15:13 ` drow at sources dot redhat dot com [this message]
2006-04-26 15:37 ` drow at sources dot redhat dot com

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=20060426151337.29805.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).