https://gcc.gnu.org/bugzilla/show_bug.cgi?id=74755
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |SUSPENDED CC| |nathan at gcc dot gnu.org, | |tschwinge at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |tschwinge at gcc dot gnu.org --- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- Nathan applied a workaround in trunk r239836, <https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01993.html>. (For the record, at least with a "combined" source tree, you don't explicitly have to configure --with-newlib to make this work, as --with-newlib will be passed by the build system.) I still think this should really be fixed in newlib, and that the configure auto-detection should be re-enabled then. Nathan's trunk r239836 caused the following changes in [build]/nvptx-none/libgfortran/config.h: /* Define to 1 if you have the `gmtime_r' function. */ -/* #undef HAVE_GMTIME_R */ +#define HAVE_GMTIME_R 1 /* Define to 1 if you have the `localtime_r' function. */ -/* #undef HAVE_LOCALTIME_R */ +#define HAVE_LOCALTIME_R 1 /* Define to 1 if you have the `mkstemp' function. */ -/* #undef HAVE_MKSTEMP */ +#define HAVE_MKSTEMP 1 /* Define to 1 if you have the `strtold' function. */ -#define HAVE_STRTOLD 1 +/* #undef HAVE_STRTOLD */ ..., accompanied by a few test case regressions, because some of these hardwired routines are not actually available in the nvptx newlib port.