From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>, Roland McGrath <roland@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] Fix no-tsd.c compile on certain arches
Date: Wed, 09 Oct 2002 07:32:00 -0000 [thread overview]
Message-ID: <20021009160552.P3451@sunsite.ms.mff.cuni.cz> (raw)
Hi!
With this I succeeded to build current CVS on i386/i686/alpha/alphaev6/ia64
with make check passing everywhere but on ia64 due to the well known
miscompilation.
It did not fail in my i686 build previously, since there stdlib.h is
included from libc-tsd.h ... useldt.h.
Sorry.
2002-10-09 Jakub Jelinek <jakub@redhat.com>
* no-tsd.c: Include stdlib.h.
--- libc/linuxthreads/no-tsd.c 9 Oct 2002 10:32:32 -0000 1.1.1.5
+++ libc/linuxthreads/no-tsd.c 9 Oct 2002 12:01:31 -0000 1.2
@@ -19,6 +19,7 @@
#include <sys/cdefs.h> /* for __const */
#include <bits/libc-tsd.h>
+#include <stdlib.h>
#if !(USE_TLS && HAVE___THREAD)
Jakub
next reply other threads:[~2002-10-09 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 7:32 Jakub Jelinek [this message]
2002-10-10 4:04 ` 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=20021009160552.P3451@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@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).