From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14198 invoked by alias); 8 Oct 2012 20:42:40 -0000 Received: (qmail 13721 invoked by uid 48); 8 Oct 2012 20:42:23 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/54847] --enable-libstdcxx-time=yes doesn't find the function nanosleep() on darwin Date: Mon, 08 Oct 2012 20:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-10/txt/msg00733.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54847 --- Comment #44 from Jonathan Wakely 2012-10-08 20:42:22 UTC --- (In reply to comment #42) > You want to find an test such that: > > (your test) <=> (nanosleep is the one you want) That's why I was asking about other feature test macros that would allow us to detect systems supporting the POSIX.1b-1993 Realtime Extensions, but not the later Timers option, or the POSIX-2008 Base. > Ok, what about just using _POSIX_TIMERS > 0 || defined(__APPLE__)? That may > miss some other OSs in the same boat, but they can always add similar checks. Because we generally try to avoid littering acinclude.m4 with such checks. The other OSs can add defines to their own os_defines.h files if needed. (In reply to comment #43) > will effectively default darwin to --enable-libstdcxx-time=yes and eliminates a > configure option. That's a *good* thing. If the platform unconditionally supports the feature and doesn't need a configure check why would you want to prevent using it? All that achieves is an incomplete libstdc++ with missing functionality.