On 6/15/2017 2:26 PM, Paul Eggert wrote:
On 06/15/2017 07:05 AM, John E. Malmberg wrote:
It should only be include files VMS has issues with.
If that's the problem, then it shouldn't be much trouble to have a
separate script that rewrites the file names and source code to follow
the POSIX portable filename rules. We could include that script as a
separate file in Gnulib, or perhaps as a gnulib-tool option. This would
avoid the need to change existing code, and I assume Bruno would be OK
with something along those lines.
I already have a VMS specific edit script that can update the 7 modules
in gnulib that include float++ that I can run as part of a prebuild script.
At the time I made that reply, my only Internet access was a small cell
phone screen, so it was both hard to type or read other pages.
For this pass, I am mainly trying to get everything to compile with a
minimum amount of VMS specific changes and support files.
That being said, wouldn't it be simpler for you to switch your VMS
development host's file system to ODS-5? That way, you should be able to
use these file names as-is, and you'll be less likely to run into
similar problems with programs other than Gnulib.
The development host system is ODS-5 on Alpha/IA64.
The not handling of #include "float++" is a bug in the compiler that was
recently discovered when I updated the GNV Coreutils package.
The compiler also sometimes has problems with #include "../xxxx.h",
which need similar edits to work around.
Regards,
-John