public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebastien dot decugis at ext dot bull dot net" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/320] New: rwlock features should not be dependent on XSI extensions
Date: Wed, 11 Aug 2004 13:39:00 -0000	[thread overview]
Message-ID: <20040811133910.320.sebastien.decugis@ext.bull.net> (raw)

The following code won't compile:
------------------------------------------
#define _POSIX_C_SOURCE 200112L
#include <pthread.h>

pthread_rwlock_t rw;

int main(int argc, char * argv[])
{
   return pthread_rwlock_init(&rw, NULL);
}
-------------------------------------------

It compiles when I add:
#define _XOPEN_SOURCE 600

But this feature is part of the IEEE Std 1003.1, 2004 Edition (and not marked
with the XSI extension). I am unsure whether /include/features.h or
/nptl/sysdeps/pthread/pthread.h should be changed.

Thanks, 
Sebastien.

-- 
           Summary: rwlock features should not be dependent on XSI
                    extensions
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: minor
          Priority: P3
         Component: nptl
        AssignedTo: drepper at redhat dot com
        ReportedBy: sebastien dot decugis at ext dot bull dot net
                CC: glibc-bugs at sources dot redhat dot com


http://sources.redhat.com/bugzilla/show_bug.cgi?id=320

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2004-08-11 13:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 13:39 sebastien dot decugis at ext dot bull dot net [this message]
2004-09-12 18:49 ` [Bug nptl/320] " 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=20040811133910.320.sebastien.decugis@ext.bull.net \
    --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).