public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schnake at composition dot de" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/359] PTHREAD_[...]_INITIALIZER_NP macros from pthread.h break GNU C++ compilation
Date: Tue, 31 Aug 2004 08:08:00 -0000 [thread overview]
Message-ID: <20040831080846.15858.qmail@sourceware.org> (raw)
In-Reply-To: <20040831075233.359.schnake@composition.de>
------- Additional Comments From schnake at composition dot de 2004-08-31 08:08 -------
Created an attachment (id=180)
--> (http://sources.redhat.com/bugzilla/attachment.cgi?id=180&action=view)
Changes the PTHREAD_[...]_INITITALIZER_NP macros to use no designated
initializer
This patch applies only a formal change to pthread.h to make it useable with
current GCC specs (that simply and explicitly do not support that initalizer
style, see URL in comment #1). I dont know about implications with other
compilers, but I think the patched initializer style should be the common one
(as the GCC refers to the current one as "designated initializer *extension*"
;-)
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=359
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2004-08-31 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 7:52 [Bug libc/359] New: PTHREAD_*_ schnake at composition dot de
2004-08-31 8:02 ` [Bug libc/359] PTHREAD_[...]_INITIALIZER_NP macros from pthread.h break GNU C++ compilation schnake at composition dot de
2004-08-31 8:08 ` schnake at composition dot de [this message]
2004-09-06 14:17 ` ed at catmur dot co dot uk
2004-09-06 14:40 ` schnake at composition dot de
2004-09-08 7:31 ` solar at gentoo dot org
2004-09-12 5:50 ` drepper at 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=20040831080846.15858.qmail@sourceware.org \
--to=sourceware-bugzilla@sources.redhat.com \
--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).