On 10/03/15 20:18 +0000, Jonathan Wakely wrote:
On 10/03/15 20:55 +0100, John Marino wrote:
On 3/10/2015 20:23, Jonathan Wakely wrote:
John, assuming I'm right that dragonfly supports all these features,
could you test this change? (You'll need the same change on line
19555 of the libstdc++-v3/configure script.)
Sure, I can test it. How can I tell if the result is successful?
Successful build versus failed build?
Yes, that should be enough. If any of sched_yield(), nanosleep(),
clock_gettime() etc. is missing you'll get a build failure.
I'll do a full testsuite run (bootstrap and 'make check') on dragonfly
before committing, but I'll need some time to resurrect the dragonfly
VM I was using previously.
I've done that testing and committed it to trunk now.
commit 16ed217e6b129861980c7f7c92964203708684e5
Author: Jonathan Wakely <jwak...@redhat.com>
Date: Thu Mar 12 13:20:06 2015 +0000
* acinclude.m4: Make --enable-libstdcxx-time=auto work for dragonfly.
* configure: Regenerate.
diff --git a/libstdc++-v3/acinclude.m4 b/libstdc++-v3/acinclude.m4
index 1727140..0b8c0f0 100644
--- a/libstdc++-v3/acinclude.m4
+++ b/libstdc++-v3/acinclude.m4
@@ -1221,7 +1221,7 @@ AC_DEFUN([GLIBCXX_ENABLE_LIBSTDCXX_TIME], [
ac_has_nanosleep=yes
ac_has_sched_yield=yes
;;
- freebsd*|netbsd*)
+ freebsd*|netbsd*|dragonfly*)
ac_has_clock_monotonic=yes
ac_has_clock_realtime=yes
ac_has_nanosleep=yes
diff --git a/libstdc++-v3/configure b/libstdc++-v3/configure
index acd8c60..bcdb931 100755
--- a/libstdc++-v3/configure
+++ b/libstdc++-v3/configure
@@ -19551,7 +19551,7 @@ $as_echo "$glibcxx_glibc217" >&6; }
ac_has_nanosleep=yes
ac_has_sched_yield=yes
;;
- freebsd*|netbsd*)
+ freebsd*|netbsd*|dragonfly*)
ac_has_clock_monotonic=yes
ac_has_clock_realtime=yes
ac_has_nanosleep=yes
