summaryrefslogtreecommitdiff
path: root/configure.com
diff options
context:
space:
mode:
authorCraig A. Berry <craigberry@mac.com>2018-01-14 13:42:05 -0600
committerCraig A. Berry <craigberry@mac.com>2018-01-15 07:00:40 -0600
commit669d6ad81497efd33243c692e6f057f97c6c1567 (patch)
treee207b7f5dd9c5e606e5999c8941447597edac7a5 /configure.com
parentd75174cd2be6a6a63099d496f8f3efc6995f933d (diff)
downloadperl-669d6ad81497efd33243c692e6f057f97c6c1567.tar.gz
VMS does have fchmod and fchown.
The test for fchmod in t/io/fs.t does, however, reveal a wrinkle that is also true of chmod on VMS: a mode argument of zero does not mean turn off all permisions but rather set permissions to the user's default. This is probably an ancient behavior from pre-standard days. For now, just skip the affected test and document what's different.
Diffstat (limited to 'configure.com')
-rw-r--r--configure.com9
1 files changed, 7 insertions, 2 deletions
diff --git a/configure.com b/configure.com
index e060f455ab..8cb8afe68f 100644
--- a/configure.com
+++ b/configure.com
@@ -6021,9 +6021,14 @@ $ WC "d_erfc='" + d_erfc + "'"
$ WC "d_eunice='undef'"
$ WC "d_exp2='" + d_exp2 + "'"
$ WC "d_expm1='" + d_expm1 + "'"
-$ WC "d_fchmod='undef'"
+$ IF ("''F$EXTRACT(1,3, F$GETSYI(""VERSION""))'".GES."8.3")
+$ THEN
+$ WC "d_fchmod='define'"
+$ ELSE
+$ WC "d_fchmod='undef'"
+$ ENDIF
$ WC "d_fchdir='undef'"
-$ WC "d_fchown='undef'"
+$ WC "d_fchown='define'"
$ WC "d_fcntl='" + d_fcntl + "'"
$ WC "d_fcntl_can_lock='" + d_fcntl_can_lock + "'"
$ WC "d_fd_set='" + d_fd_set + "'"