[New-bugs-announce] [issue31199] !HAVE_CLOCK_GETTIME causes problems with _PyTime_FromTimespec

[Paulo Matos]

New submission from Paulo Matos:

On a Fedora 26 system, I run configure as:
$ ../configure --with-assertions --with-lto --with-pydebug --with-address-sanitizer --disable-ipv6

My pyconfig.h contains:
/* #undef HAVE_CLOCK */

/* Define to 1 if you have the `clock_getres' function. */
/* #undef HAVE_CLOCK_GETRES */

/* Define to 1 if you have the `clock_gettime' function. */
/* #undef HAVE_CLOCK_GETTIME */

/* Define to 1 if you have the `clock_settime' function. */
/* #undef HAVE_CLOCK_SETTIME */

/* Define if the C compiler supports computed gotos. */
/* #undef HAVE_COMPUTED_GOTOS */


When this happens, __PyTime_FromTimespec is undefined in pytime.c:747.
../Python/pytime.c:747:9: error: implicit declaration of function ‘_PyTime_FromTimespec’; did 
you mean ‘_PyTime_FromTimeval’? [-Werror=implicit-function-declaration]
     if (_PyTime_FromTimespec(tp, &ts, raise) < 0)
         ^~~~~~~~~~~~~~~~~~~~
         _PyTime_FromTimeval
cc1: some warnings being treated as errors
make[2]: *** [Makefile:1553: Python/pytime.o] Error 1

----------
components: Build
messages: 300238
nosy: pmatos
priority: normal
severity: normal
status: open
title: !HAVE_CLOCK_GETTIME causes problems with _PyTime_FromTimespec
type: compile error

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue31199>
_______________________________________