Hard link support for VMS (part 2)

John Malmberg · *nix forums addict Joined: 15 Jul 2005 Posts: 64

This configure.com tests to see if hard links are enabled on the build
disk, and if so enables hard link support in the build.
This test is only done on 8.2 even though hard links have been available
since 7.3-1.

1. I only have been able to test with 8.2 and later at this time.

2. The dcl lexical function to test if hard links are enabled on a
volume were implemented with 8.2 so a different test would be needed or
the dependency removed.

If someone needs hard link support for 7.3-1 or 7.3-2 it should not be
too hard to add it.

The MAKE now defaults to MMK if both MMK and MMS are present for the
build as MMS currently has a problem with case preserved file types.

If VMS is a 64 bit variant of 8.2 or later, many of the CRTL routines
added in 7.3-2 are configured. This test could be brought back to
7.3-2, if someone were to do the testing.

If VMS is a 64 bit variant of 8.2 or later, many of the CRTL routines
added in 8.2 are now configured.

If the uselargefiles option is selected and the realpath() routine
exists in the CRTL, then support for symbolic links will be configured.

The realpath() routine is in the RMS symbolic links SDK and is on the
roadmap to be in a future version of VMS.

Perl_setup.com is optionally built such that it defines perl_root based
on the directory it currently resides in, as a step toward being able to
build a binary distribution kit that does not require editing it.

A number of patches from Craig and all for enabling builds on an ODS-5
volume with extra dots present.

A number of fixes because of symbol conflicts when the symbol "link" may
have been present before running the procedure.

Latent support may be present for using the 8.2 standard stat() call. I
had to back that out because VMS Perl is dependent on one field only
provided by the existing non-standard stat() call. Once the resolution
of a change for future VMS is more finalized, I hope to put that back in.

Perl and the CRTL were incorrectly translating "foo:[000000]" to be
"/foo/000000/" instead of "/foo". In order to get the UNIX mode to
work, I had to fix this in the C source code. This also required
configure.com to not add the "000000/ to UNIX names that it created.

-John
wb8tyw@qsl.net
Personal Opinion Only

Google