[Top][All Lists]

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

[bug #42447] Fix exporting symbols for recursive make on VMS.

From: John Malmberg
Subject: [bug #42447] Fix exporting symbols for recursive make on VMS.
Date: Sat, 14 Jun 2014 16:47:10 +0000
User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0

Follow-up Comment #1, bug #42447 (project make):

Uploaded replacement patch:

* Updated the Git description to match format in git logs.
* Added vms_exit.c missing from previous patch needed for this to be applied
against master.
* Found that when make was reading DCL symbols and logical names as
environment variables, it was doubling the "$" characters found.  This means
that the export routine has to remove the duplicate "$" characters before
creating the symbol.

This patch also includes the fix for exit decoding that has been discussed on
the bug-make list.

The program name is created as the equivalent of a shell alias instead of
using the alternate "MCR make-name" syntax so that when the macro is expanded,
no spaces are present.  While it is not known that having a space there would
cause a problem, I feel that there is a high risk of that.

The DCL symbol export is used instead of putting the symbols in the helper
command procedure and always using a command procedure to try to have the
program use as similar program flows to make to get the tests working.

It also seems to me to be more efficient to try to avoid using the helper
command procedure as much as possible.

I am expecting that changes will be needed in the VMS specific command
launching to support multiple jobs, One shell, and the issue of using the
command file or a pool of subprocesses can be addressed them.

Copyright assignment papers are on file with fsf.org.

(file #31546)

Additional Item Attachment:

File name: 0001-vms_export_symbol_fix_pass2.patch Size:46 KB


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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