public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/4000] <argp.h> has a buggy __NTH macro definition Date: Mon, 12 Feb 2007 12:37:00 -0000 [thread overview] Message-ID: <20070212123704.29767.qmail@sourceware.org> (raw) In-Reply-To: <20070207235817.4000.madcoder@debian.org> ------- Additional Comments From jakub at redhat dot com 2007-02-12 12:37 ------- sys/cdefs.h is already included when you include argp.h (stdio.h includes features.h which includes sys/cdefs.h), the define is there just for the case where argp.h is used standalone as part of gnulib on non-glibc system. Your patch only makes things worse, no header should ever undef these macros. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4000 ------- 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:[~2007-02-12 12:37 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-07 23:58 [Bug libc/4000] New: " madcoder at debian dot org 2007-02-07 23:59 ` [Bug libc/4000] " madcoder at debian dot org 2007-02-12 12:37 ` jakub at redhat dot com [this message] 2007-02-12 14:42 ` madcoder at debian dot org
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=20070212123704.29767.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --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: linkBe 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).