On Wed, 2013-05-22 at 09:14 +0100, Jonathan Wakely wrote:
> This alters the configure script to enable C++11 thread library
> features based on targets that are known to support the features,
> rather than based on link tests which are disabled by default. With
> Glibc 2.17 this enables a nanosecond resolution std::system_clock in
> the default configuration, yay!
>
> I've tested this on two versions of Fedora and Debian, but would be
> grateful for test results on Solaris, Cygwin and BSD targets, and for
> cross-compilers to any of those targets.
>
> * acinclude.m4 (GLIBCXX_ENABLE_LIBSTDCXX_TIME): Add KIND=auto to
> enable features if target OS is known to support them.
> * configure.ac (GLIBCXX_ENABLE_LIBSTDCXX_TIME): Default to 'auto'.
> * configure: Regenerate.
>
>
> Tested x86_64-linux, committed to trunk.
Jonathan,
This has broken the mips-mti-elf build for me, this target uses newlib
and I am building with the latest newlib sources as well as the latest
GCC sources. I don't know if this is related to the problem that others
have had or not. I saw emails about test failures but not about build
failures. The problem I get when building a x86 to mips cross compiler
is:
/local/home/sellcey/nightly2/src/gcc/libstdc++-v3/src/c++11/compatibility-chrono.cc:
In static member function 'static std::chrono::system_clock::time_point
std::chrono::system_clock::now()':
/local/home/sellcey/nightly2/src/gcc/libstdc++-v3/src/c++11/compatibility-chrono.cc:81:14:
error: 'from_time_t' is not a member of 'std::chrono::system_clock'
return system_clock::from_time_t(__sec);
^
/local/home/sellcey/nightly2/src/gcc/libstdc++-v3/src/c++11/compatibility-chrono.cc:83:5:
warning: control reaches end of non-void function [-Wreturn-type]
}
I will dig around some more but I thought I would see if you had any
ideas on what the problem was and how to fix it.
Steve Ellcey
[email protected]
