[Bug libstdc++/93325] libstdc++ wrongly uses direct clock_gettime syscall on non-glibc, breaks time64

[cvs-commit at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93325

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <r...@gcc.gnu.org>:

https://gcc.gnu.org/g:759812fddc81c0c131d4633b2a7f56412ce8dbed

commit r10-6287-g759812fddc81c0c131d4633b2a7f56412ce8dbed
Author: Jonathan Wakely <jwak...@redhat.com>
Date:   Tue Jan 28 13:24:09 2020 +0000

    libstdc++: Replace glibc-specific check for clock_gettime (PR 93325)

    It's wrong to assume that clock_gettime is unavailable on any *-*-linux*
    target that doesn't have glibc 2.17 or later. Use a generic test instead
    of using __GLIBC_PREREQ. Only do that test when is_hosted=yes so that we
    don't get an error for cross targets without a working linker.

    This ensures that C library's clock_gettime will be used on non-glibc
    targets, instead of an incorrect syscall to SYS_clock_gettime.

        PR libstdc++/93325
        * acinclude.m4 (GLIBCXX_ENABLE_LIBSTDCXX_TIME): Use AC_SEARCH_LIBS for
        clock_gettime instead of explicit glibc version check.
        * configure: Regenerate.