On 3/10/2015 20:23, Jonathan Wakely wrote: > It has just occurred to me we might want to make this change for GCC5: > > > 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 > @@ -1219,11 +1219,11 @@ AC_DEFUN([GLIBCXX_ENABLE_LIBSTDCXX_TIME], [ > ac_has_clock_realtime=yes > fi > 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 > ac_has_sched_yield=yes > ;; > > > We could make this change post-GCC5 but as the dragonfly target is new > for GCC5 it would be a shame to release it with a sub-optimal > resolution for clocks and thread sleeping. > > 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? Thanks, John