This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/54847] --enable-libstdcxx-time=yes non-functional on darwin
- From: "jeremyhu at macports dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 07 Oct 2012 17:39:52 +0000
- Subject: [Bug libstdc++/54847] --enable-libstdcxx-time=yes non-functional on darwin
- Auto-submitted: auto-generated
- References: <bug-54847-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54847
Jeremy Huddleston Sequoia <jeremyhu at macports dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeremyhu at macports dot
| |org
--- Comment #2 from Jeremy Huddleston Sequoia <jeremyhu at macports dot org> 2012-10-07 17:39:52 UTC ---
I think Jack is confused regarding --enable-libstdcxx-timer. From emailing me,
he seems to be under the impression that '--enable-libstdcxx-timer' is
equivalent to '--enable-libstdcxx-timer=no' ... if that is the case, then
something is certainly wrong since --enable-libstdcxx-timer should be
equivalent to '--enable-libstdcxx-timer=yes' ...
As for darwin ... we have sched_yield and nanosleep. We don't have
clock_gettime.
Why are you testing for posix timer support in your checks for sched_yield and
nanosleep?