From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19004 invoked by alias); 2 Feb 2005 07:57:30 -0000 Mailing-List: contact glibc-bugs-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sources.redhat.com Received: (qmail 18890 invoked by uid 48); 2 Feb 2005 07:57:18 -0000 Date: Wed, 02 Feb 2005 07:57:00 -0000 Message-ID: <20050202075718.18889.qmail@sourceware.org> From: "nix at esperi dot org dot uk" To: glibc-bugs@sources.redhat.com In-Reply-To: <20050117073135.674.andihartmann@freenet.de> References: <20050117073135.674.andihartmann@freenet.de> Reply-To: sourceware-bugzilla@sources.redhat.com Subject: [Bug linuxthreads/674] Error compiling linuxthreads in glibc 2.3.4 X-Bugzilla-Reason: CC X-SW-Source: 2005-02/txt/msg00004.txt.bz2 List-Id: ------- Additional Comments From nix at esperi dot org dot uk 2005-02-02 07:57 ------- (In reply to comment #3) > > libc's decision is obviously correct: if __thread is available, you *should* use > > it for errno; this won't change merely because floating stacks happen to be > > available in one particular threading implementation. So something needs to > > change in linuxthreads. Yes it will: manager.c makes that quite clear. So it looks like the constraints we face are as follows: - if TLS is not available, __thread is not available, or the linuxthreads add-on is in use and FLOATING_STACKS are not supportable, then _errno and _h_errno must be compiled into libc, and a TLS cannot be used for errno. - TLS support must nonetheless be compiled into rtld, because otherwise that rtld couldn't successfully interoperate with an NPTL-enabled glibc (as I understand it: that's definitely a goal or almost every distributor will scream). The hard part is how we determine from errno.c, during libc compilation, whether the linuxthreads add-on is in use and whether floating stacks are supported... ... I really don't like mentioning linuxthreads or floating stacks in errno.c. There must be a better way. -- http://sources.redhat.com/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.