From: Andreas Schwab <schwab@suse.de>
To: libc-hacker@sources.redhat.com
Subject: Use of dl-tls.h
Date: Sun, 07 Mar 2004 15:53:00 -0000 [thread overview]
Message-ID: <m3llmcfybj.fsf@whitebox.m5r.de> (raw)
dl-tls.h should only be included when USE_TLS.
Andreas.
2004-03-07 Andreas Schwab <schwab@suse.de>
* elf/dl-sym.c: Include <dl-tls.h> only when USE_TLS.
--- elf/dl-sym.c.~1.19.~ 2004-03-07 15:25:31.000000000 +0100
+++ elf/dl-sym.c 2004-03-07 16:51:14.836143432 +0100
@@ -24,7 +24,9 @@
#include <dlfcn.h>
#include <ldsodefs.h>
#include <dl-hash.h>
-#include <dl-tls.h>
+#ifdef USE_TLS
+# include <dl-tls.h>
+#endif
#if defined USE_TLS && defined SHARED
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next reply other threads:[~2004-03-07 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 15:53 Andreas Schwab [this message]
2004-03-07 19:32 ` Ulrich Drepper
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=m3llmcfybj.fsf@whitebox.m5r.de \
--to=schwab@suse.de \
--cc=libc-hacker@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).