[Info-vax] Looking into C-include files on VMS

[Wilm Boerhout]

Bob Eager mentioned  on 30-10-2009 21:32:
> On Fri, 30 Oct 2009 19:55:35 +0000, Joerg Schilling wrote:
> 
>> In article <4aeb35dc$0$271$14726298 at news.sunsite.dk>, Graham Burley
>> <burley+news at encompasserve.org> wrote:
>>
>>> You need to use the ODS-5 disk area, e.g.
>>>
>>> $ @gnv$gnu:[lib]gnv_setup.com
>>> $ bash
>>> bash$ pwd
>>> /disk_support/decuserve_support/burley bash$ echo > a.b.c
>>> bash.exe.1: a.b.c: i/o error
>>> bash$ cd /usr_ods5/burley
>>> bash$ echo > a.b.c
>> Thank you! this was a very important information.
>>
>> I am now able to have more than one dot in filenames.
>>
>> If I find a solution for the hangs in "configure" and if I find a
>> solution for the "cc always exits with 0" problem that leads to wrong
>> configure results, a make/configure controlled compilation seems to be
>> close.
> 
> VMS exit status is essentially a 32 bit value. The low order bit is 1 for 
> success, zero for failure.

But, open source and or "foreign" programs ported to VMS may not always 
exit with a VMS exit status value.

Both DEC C ($CC) and and HP C++ ($CXX) compilers exit with even status 
values on compilation errors.

/Wilm