Re: gnutar 1.19 - lib/getcwd algorithm does not work on VMS

[Jim Meyering]

"John E. Malmberg" <address@hidden> wrote:

> 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
> multiple overlayed directory trees, such as /sys_foo/bar/baz and
> /usr_foo/bar/baz.
>
> And on my test setup, I have /prj_root/tar-1.19/tests which actually
> maps to /src_root/tar-1.19/tests and lcl_root/tar-1.19/tests.
>
> I am suspecting that while if you opendir('prj_root/tar-1.19/tests')
> the readdir() calls will return the contents of the tests directory in
> src_root, and then lcl_root.  But if you opendir('..') you only get
> one of the paths, because of the way that the UNIX file specification
> is translated by the lower levels into a native VMS specification.
>
> It looks like the quick fix for me is to convince configure that the
> VMS getcwd is either working or partially working.

If you're talking about the test in getcwd-path-max.m4,
this sets the cache variable to do that:

  gl_cv_func_getcwd_path_max=yes ./configure