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

[John E. Malmberg]

Joerg Schilling wrote:

<snip>
> On EISNER with VMS 8.3, the compiler returns a correct exit code 
> but the problem now is the "bash" binary that seems to have problems with
> I/O redirection (in the current case, so-called "here documents").
> 
> calling "bash somescript"
> 
> with "somescript" containing:
> 
> cat > x.c << EOF
> main()
> {
> printf("test\n");
> }
> EOF

> creates an empty file "x.c" and a file $HOME/sh869670
> that has the content expected for x.c, the small C program from above.

I just replaced the bash/sh programs with the ones that I use instead of 
the ones in the kit.  Those fixes were suppose to be in HP kit that I 
installed on Eisner, but apparently are not.

It does not fix the issue of $HOME/sh* files being left behind.  That is 
being looked at by someone else, along with getting more improvements 
into bash.

The gnu make program leaves $HOME/make* files behind.

So periodically outside of bash, issue the DCL command below as there 
are multiple versions of the files created.

$ DELETE SYS$LOGIN:SH*.;*
$ DELETE SYS$LOGIN:MAKE*.;*

> As "bash" also from time to time hangs while exeuting similar code
> as mentioned above, this I/O redirection problem currently seems to be 
> the only problem for getting "configure" to work.

This may also solve that problem.  There are still some intermittant 
hangs that I have not found the causes for.

As someone else has pointed out, the issue with gnu tar not unpacking 
the files with multiple dots was from you using an ODS-2 volume, not an 
ODS-5 volume.

-John
wb8tyw at qsl.network
Personal Opinion Only