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 i
On 6/8/2017 5:28 PM, Paul Eggert wrote: On 06/08/2017 08:40 AM, Bruno Haible wrote: Feel free to submit a patch to doc/build-automation.texi that references DEPENDENCIES ... I gave a shot at patching
Does the VMS client mount over UDP only? If so, that is probably the problem. Recent nfs-utils (as used in Fedora 25) disabled UDP support by default, as the major NFS clients have supported TCP for
Does the VMS client mount over UDP only? If so, that is probably the problem. Recent nfs-utils (as used in Fedora 25) disabled UDP support by default, as the major NFS clients have supported TCP for
I issued the command below and it failed on a Fedora/22 system with a You _do_ realize that Fedora 22 is unsupported upstream, and is probably lacking in security patches that you would otherwise ge
I am trying to set up a build robot to see if the VMS GNV packages is good enough to run to tests on GNULIB. https://www.gnu.org/software/gnulib/manual/gnulib.html#Build-robot-for-gnulib First issue
Hi John, In the relocatable-prog-wrapper situation, like in all other uses of gnulib without the 'getcwd' module, getcwd is not #defined. Therefore, as I understand, it takes 3 arguments. gnulib does
2. The replacement from gnulib causes canonicalize-lgpl.c to fail because the replacement only has 2 parameters, not three. 3. The replacement from gnulib also does not fix all the known ills in VMS
Hi, But when IN_RELOCWRAPPER is defined (i.e. when this code is used through the 'relocatable-prog-wrapper' module) we '#undef getcwd', so in this case the lines /* We want the directory in Unix synt
Summary: 1. The VMS CRTL getcwd() will not pass configure tests and will be marked for replacement from gnulib. 2. The replacement from gnulib causes canonicalize-lgpl.c to fail because the replaceme
I do not know if the pragma for the assert would be valid for anything other than __DECC compiler Ah, I see. Still, I'm leery of pragmas, as I have the sneaking suspicion that they can hurt even when
Thanks for the heads-up. I see that 8.2 came out in 2005; I guess news travels slowly from the VMS world to the Gnulib world. The Sourceforge GNV project has a backlog of things to get into shape for
Thanks for the heads-up. I see that 8.2 came out in 2005; I guess news travels slowly from the VMS world to the Gnulib world. Instead of a pragma for checking, how about if we define _USE_STD_STAT al
VMS 8.2 and later provide a 64 bit ino_t type when _USE_STD_STAT is defined on the command line. This patch makes the fallback to the old VMS behavior for only VMS 8.1 and earlier. This patch also ad
Assaf, that.is.so.cool ! Really, your work is a great help to any project striving for portability (VM setup and 'suggested command line'). You mean letting projects use the VMs as a CI service ? Tha
Hello, [...] Therefore what is more valuable for gnulib (IMO) is automated testing on 20 different platforms. Of course everybody wishes to have a CI for 20 different platform :-) For real VMs with o
Of course everybody wishes to have a CI for 20 different platform :-) But you have to start at some point, picking the low hanging fruits. And that is Gitlab CI based on Docker. You can build, test a
Although relocate() in practice does not produce memory leaks (in the sense of _repeated_ loss of memory blocks), it is sufficiently often reported by analysis tools (valgrind, coverity) that I'm now
Hi Jim, On Windows with MSVC, the 'fpending' module does not pass its test, because config.h defines In order to get this right, the expression should be ((struct { unsigned char *_ptr; unsigned char