I committed your change with modifications: - This definition was at the wrong place. You put it in the middle of a declaration. - The style in this file is to avoid parentheses after '#if defined'.
I applied it, with this ChangeLog entry. The "tiny change" marker means that we don't need a copyright assignment for this change. 2008-03-03 John E. Malmberg <address@hidden> (tiny change) Update VM
Hello John, * John E. Malmberg wrote on Mon, Mar 03, 2008 at 07:01:46AM CET: Can you do something like a VPATH build on VMS? Because then, then testsuite script should live in the source tree, and th
I have TAR passing the pipe test, so I though it would be a good point to pass the source changes I needed so far. TODO: I still have to add the vfork/exec/pipe code from the VMS bash port so that th
Hello again, The lib/getcwd replacement algorithm does not work on VMS. I am still trying to figure out exactly why it is failing. On VMS, the directory specification /foo/bar/baz can actually be mul
I am trying to get gnu tar to build on VMS. I have run into a problem: GNU TAR now requires that the open() call support O_DIRECTORY. You may find some useful resources at https://savannah.gnu.org/pr
The open() would have to open or dup a file descriptor to the /dev/null device to reserve a unique file descriptor, and then something needs to map that file descriptor back to the pointer to the *DI
According to John E. Malmberg on 2/20/2008 6:23 PM: Then you weren't looking in the right place. POSIX 2001 (with TC amendments to 2004) is available at no cost by joining the Austin Group (http://ww
POSIX:2001 is the same as the "OpenGroup Base Specification Issue 6" and also known as "SUSv3". You find it on the web at http://www.opengroup.org/susv3/ Do you need a pointer to the DIR structure, o
According to John E. Malmberg on 2/18/2008 8:46 PM: Tar is using O_DIRECTORY to close a security hole, and not to directly read the directory contents. And POSIX requires that a directory be openable
According to John E. Malmberg on 2/18/2008 8:46 PM: Tar is using O_DIRECTORY to close a security hole, and not to directly read the directory contents. And POSIX requires that a directory be openable
Hello, I am trying to get gnu tar to build on VMS. I have run into a problem: GNU TAR now requires that the open() call support O_DIRECTORY. On the VMS platform, this support is not available. Using
The quick patch that I can do is to move where the #undef of the _GL_JUST_INCLUDE_SYSTEM_DIRECTORY_H is. Yes, thanks, that sounds like a reasonable fix. I installed the patch below: does it work for
I'm trying to convert m4 to transparently handle embedded NUL. In the process, I need to move from strstr to memmem (if m4 were fully i18n already, I would instead be moving from mbsstr to the length
Yes, thanks, that sounds like a reasonable fix. I installed the patch below: does it work for you? That would mean we'd have to rewrite all our source code that includes <stdint.h>. We'd rather not d
Hello, I am attempting to build tar-1.19 on VMS. I am getting an error assert from inttypes.h: "This file assumes that 'int' has exactly 32 bits. Please report your platform and compiler to <bug-gnul
Martin Lambers wrote on 2007-11-28: Thanks. The first part is undoubtably the right thing to do; so I'm applying that first (with HAVE_OS_H and HAVE_SYS_PARAM_H being AC_SUBSTed - the reason is that
Hi Jim, Our QNX peer person has verified that this modified patch passes on QNX: PASS: test-fpending.sh therefore I'm applying it: 2007-11-06 Bruno Haible <address@hidden> * m4/fpending.m4 (gl_FUNC_F