On 3/10/2015 23:04, John Marino wrote: > On 3/10/2015 21:18, 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. > > Hi Jonathan, > gcc 5 built fine on DragonFly with your patch: > http://muscles.dragonflybsd.org/bulk/bleeding-edge-potential/20150310_142205/logs/gcc5-5.0.s20150308.log >
Hi Jonathan, Today I build gcc5 and looked at the config.h contained in libstdc++-v3's build directory and none of those variables are enabled. The code that is patched doesn't seem to do anything. I grepped the entire build directory for "libstdcxx_time" and got no results. I don't have "--enable-libstdcxx-time" set as a configure argument. So I am thinking somehow this configuration check got skipped completely. John
