Re: [bug #41758] VMS Make incorrectly reports archives support present.

[John E. Malmberg]

On 5/31/2014 7:45 AM, h.becker wrote:
> On 05/15/2014 05:51 AM, John Malmberg wrote:
> > Follow-up Comment #4, bug #41758 (project make):
>
> One more comment on (obecjt) module names in a VMS (obejct) library. At
> least for I64 there can be lowercase module names in an object library.
> I didn't check on Alpha. On VAX I couldn't convince the C compiler to
> generate a lowercase module name. That is, I don't know and didn't try
> to find out, whether this is a feature of Librarian for I64 or a feature
> of the "language processors" to write a lowercase module name into the
> object module.

While I have not checked on VAX, on both Alpha and Itanium the module 
name can have both upper and lower case in it.  This will mainly show up 
when the source module is on an ODS-5 volume.

Right now, ODS-5 support is broken because the vmsify() routines are not 
only assuming ODS-2, they are also not converting Unix format file 
specifications correctly when the first path component is a logical 
name.  I am assuming that the unixify routines are in just as bad state 
and have a bug open on them.

After the other issues are fixed, I plan to write a test for proper 
handling of ODS-2 and ODS-5 pathnames, and use it to validate fixed 
vmsify and unixify routines.  GNU Make can detect when the DECC feature 
to use ODS-5 names is active, and it can also detect if the process has 
been set to case sensitive mode.

Until then, I am not going to worry about ODS-5 issues, except to mark 
them in the code.

Also, currently neither MMS or MMK properly handle the case of library 
module names.  A fix is in the queue for MMK and a bug report has been 
filed with MMS.  No eta on either, but this causes all modules to be 
reinserted into the library each time.

Regards,
-John