[Info-vax] First GNULIB test results on VMS.

[John E. Malmberg]

Most GNU code uses GNULIB to compensate for differences in the C library.

I recently got GNULIB to build on VMS and run the tests.

Many of the changes to get GNULIB building have been checked in, but 
some are still local.

# TOTAL: 1146
# PASS:  874
# SKIP:  99
# XFAIL: 0
# FAIL:  173
# XPASS: 0
# ERROR: 0

The test-readtokens apparently hangs.  Watched it consume no CPU at 
least 1/2 hour before killing that test.

Any test that uses fork(), exec(), or system() is pretty much expected 
to fail on OpenVMS at this point.

I am seeing clusters of failures in Unicode, I/O, and floating point tests.

I have not yet started to debug these failures.

Some OpenVMS C library behavior is controlled by feature settings.  A 
minimal set of features such as report filenames in Unix format were set.

The total time from running the running the tests from the gnulib-tool 
to the make check completing seems to be somewhere around 24 hours.

The gnulib-tool run time is about 45 minutes on a 2.1 Ghz PC running 
Fedora/25.  Gnulib-tool is the script that does a selection of what part 
of gnulib is to be built.  It runs the autoconfig steps.

The build system is an OpenVMS 8.4 HP RX-2600 1.6 Ghz CPUs, (Itanium).

The source files are NFS served over a 100 Mb dedicated ethernet link 
from the Fedora/25 PC.

Regards,
-John
wb8tyw at qsl.net_work