At 8:26 AM -0600 3/3/05, John E. Malmberg wrote:
It turns out though, that I will only have one define, as _USE_STD_STAT implies _LARGEFILE and 32 bit GIDs, and symlinks will require _USE_STD_STAT.
Based on your other post, I am modifying my copy of CONFIGURE.COM to enabling hardlinks if support is detected for them on the build disk, not as a build option.
Excellent. I look forward to your patch. I suppose there's no reason to do the check unless we're on v7.3-1 or later.
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.
What do you need for a patch to be submitted?
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.
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.
-John [EMAIL PROTECTED] Personal Opinion Only
