From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] Fix linuxthreads build on ia64
Date: Fri, 06 Aug 2004 14:57:00 -0000 [thread overview]
Message-ID: <20040806124036.GK30497@sunsite.ms.mff.cuni.cz> (raw)
Hi!
As __res_initstamp is attribute_hidden and libc_lite.so doesn't link
in res_libc.c but links in res_init.c, its link was failing on IA-64.
Fixed thusly.
2004-08-06 Jakub Jelinek <jakub@redhat.com>
* libc-tsd.c (__res_initstamp): New variable.
--- libc/linuxthreads/libc-tsd.c.jj 2002-11-15 04:37:07.000000000 +0100
+++ libc/linuxthreads/libc-tsd.c 2004-08-06 16:20:00.576739679 +0200
@@ -1,5 +1,5 @@
/* Special hack used to build link-time libc.so object for linking libpthread.
- Copyright (C) 2002 Free Software Foundation, Inc.
+ Copyright (C) 2002, 2004 Free Software Foundation, Inc.
This file is part of the GNU C Library.
The GNU C Library is free software; you can redistribute it and/or
@@ -32,3 +32,5 @@ int _h_errno;
struct __res_state _res;
#endif
+
+unsigned long long int __res_initstamp;
Jakub
reply other threads:[~2004-08-06 14:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040806124036.GK30497@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--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).