bug-make
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

VAX/VMS 7.3 and build from copy of master.


From: John E. Malmberg
Subject: VAX/VMS 7.3 and build from copy of master.
Date: Thu, 20 Feb 2014 00:34:51 -0600
User-agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3

[bcc Hartmut Becker per request of Paul Smith]

The attach patch allows VMS to build from a clone of the master branch of the GNU make repository.

The config.h-vms.template was using macros that were not predefined by the compiler. The macros that were in use are only defined after a VMS header file is included, so were preventing the GNU Make 4.0 from building on VMS older than 7.3-2.

The config_h_from_vms_template.com converts the config.h-vms.template to a config.h-vms file It is reading the version string from NEWS. as that is the only place that I found it. If there is a better place to read the version, I can adjust the file.

The gmk_default_h.com is used to generate the gmk-default.h file, that the makefile.vms is expecting. It appears that the guile module is currently not using that header file when built on VMS.

The makefile.com and makefile.vms were adjusted to build from master as well as a release.

I tried to get the GNU make 4.0 tarball to build on VAX/VMS 7.3. It failed because of the header macro bug in the config.h-vms file, and the then requirement of vsnprintf(). After bringing over the vsnprintf() from the gawk project. This got gnu make building with almost no output on VAX/VMS 7.3

The lack of output was caused by a buffer allocation bug in output.c. That buffer allocation bug does not exist in the output.c in master and master does not need the vsnprintf() routine.

This patch was tested against master on VAX/VMS 7.3 and IA64/VMS 8.4.

I am now looking at what it will take to get the perl scripts for testing to run on VMS.

Regards,
-John

Attachment: 0001-VAX-VMS-7.3-and-build-from-master.patch.gz
Description: application/gzip


reply via email to

[Prev in Thread] Current Thread [Next in Thread]