Re: VMS can not include "float+.h"

2017-06-14 Thread Paul Eggert
On 06/14/2017 05:08 PM, John E. Malmberg wrote: The make step fails at c-vasnprintf.c because the VMS C compiler can not handle the "float+.h" filename Perhaps Gnulib source files should be renamed to use just the characters in the POSIX Portable Filename Character Set

VMS can not include "float+.h"

2017-06-14 Thread John E. Malmberg
I seem to have coerced configure into running on NFS served files created by on VMS using GNV updated kits. rm -rf ${GNU_MIRRORS}/gnulib/gnulib ./gnulib-tool --create-testdir --with-tests --dir=${GNU_MIRRORS}/gnulib/gnulib # Work around some issue with NFS timestamps. pushd ${GNU_MIRRORS}/gnu

Re: Is there someway to get make to skip checking if autoconf/automake need running?

2017-06-14 Thread Bruno Haible
Hi John, > I seem to have found an issue with how timestamps from an NFS served > volume are showing up on VMS. > > I see the correct timestamps on the Linux system, but the wrong > timestamps on the VMS system which is causing make to try to run > autoconf or automake, which I do not yet have

Is there someway to get make to skip checking if autoconf/automake need running?

2017-06-14 Thread John E. Malmberg
I seem to have found an issue with how timestamps from an NFS served volume are showing up on VMS. I see the correct timestamps on the Linux system, but the wrong timestamps on the VMS system which is causing make to try to run autoconf or automake, which I do not yet have available. So far