Re: Test harness patch for VMS.

[h.becker]

On 03/31/2014 01:53 AM, John E. Malmberg wrote:
> This is the first cut at the patches for running the test harness on
> VMS.  The test_make.com sets up the environment and runs the test.
> As it makes persistent changes to the logged in session, I recommend
> dedicating a logged in session to running tests.
> 
> The "-help" option to test_make.com explains the usage for VMS.
> 
> The updates to the individual test scripts will follow as separate patches.
> 
> This has some temporary hacks in it to get around some known issues with
> VMS that affects multiple tests that will need to be removed as the
> issues are resolved.
> 
> The test harness on VMS requires:
> 
>   Perl 5.18 or later.
>   PCSI kits available from
>      http://sourceforge.net/projects/vmsperlkit/files/
> 
>   GNV 2.1.3 or later.  GNV 3.0.1 has not tested with this script.
>   Bash 4.2.47 or later.
>   Coreutils 8.21 or later.
>     http://sourceforge.net/projects/gnv/files/
>   Read before installing:
>      http://sourceforge.net/p/gnv/wiki/InstallingGNVPackages/

I appreciate your work on the tests with/for/on VMS. This wasn't done
before and the tests obviously exhibit problems, features and
limitations. (To me they also indicate that there isn't much or heavy
usage of GNU make on VMS.) I tried the test_make.com but it failed. As
far as I can see it checks whether the required components are present.
And they seem to be available. Maybe I missed something, but it fails with:

$   perl run_make_tests.pl -verbose
%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
 \-C\
%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
 \-C\
%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
 \-C\
------------------------------------------------------------------------------
                      Running tests for GNU make on VMS
                               GNU Make 4.0.90
------------------------------------------------------------------------------

Also, with all the dependencies on GNV I wonder whether it makes sense
to run this in/from DCL at all. With GNV and Bash etc. required,
wouldn't it be better (and require less VMS specifc perl code?) to run
it from bash? And, because it depends on all of this, I think the test
driver should be named with a prefix "gnv".