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

[Richard B. Gilbert]

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.
> 
> 

Are you using the DEC/Compaq/HP C compiler?  That should NOT exit with 
"0".  Gnu or other flavors of CC may exit with 0 or almost anything 
else.  Most well written VMS software will exit with "1" for success and 
with a status value that can be decoded.  ISTR that the three or four 
low order bits were a return status code with 1 for success 2 for 
"Warning" and 4 for "Fatal error".  The remaining bits are a pointer 
into a system message file which should provide some detail as to what 
the problem was.  The system will display the appropriate message for 
the status code.  You can check for particular status values and take 
corrrective action if you wish.