At 11:40 PM -0500 3/3/05, John E. Malmberg wrote: >At this time, I can only test it on v8.2, and v8.2 is the earliest that DCL >can easily check to see if hard links are available. The lexical function to >check if hard links are enabled on the hard drive starts with v8.2. For prior >versions, either the output of $SHOW DEVICE/FULL would need to be parsed, or a >temporary program written to do the test.
Building an on-the-fly program, usually called try.c, is the standard way to go. There are quite a few examples in configure.com. There is no reason to even run the test on VAX or on non-VAX prior to v7.3-1. >What do you need for a patch to be submitted? GNU unified diffs of any files that have changed would be ideal. It's not clear to me to what extent the various changes you have in progress can be separated out, but I'm willing to help with the separating if you have something we can go ahead and get into bleadperl. I'm assuming configure.com, [.vms]vmsish.h, and [.vms]descrip_mms.template at a minimum are involved. > >>>I am also only enabling SYMLINK support if the operating system supports >>>it and the uselargefiles option is also active. >> >>It may be counterintuitive that one has to enable large file support >>in order to also get symlink support. But I don't have a better >>suggestion at the moment. > >Actually there really should not be any reason not to enable large file >support when it is available. I think it's slower, and also we try to track whatever defaults the unix builds use. >There is a lot of work to get the symlink stuff working, because it also >requires getting Perl to honor the DECC$FILENAME_UNIX_ONLY and >DECC$FILENAME_UNIX_REPORT logical names every where it returns a filename. Yup. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
