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

[Joerg Schilling]

In article <OgLGm.108497$5n1.85640 at attbi_s21>,
John E. Malmberg <wb8tyw at qsl.network> wrote:

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

This version of the shell indeed fix the problems with the non-working
"here documents". It did however introduce a new problem:

configure calls test -r somefile (using a well known file name for "somefile")
in order to verify that it was called from the right directory. While
the old bash version did work correctly with this test, the current bash
returns exit code 1 for the built in command "test" in this case.
I found a workaround for this problem: after I called "chmod a+r *",
test -r somefile again returns exit code 0 for the existing files
that are owned by me. It seems that the current bash version looks for the
wrong "r" bit in the stat.st_mode field.

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

I did this many files already ;-) If I did not do it, there have been
hundreds of such files.

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

This currently seems to be only problem that cannot be worked around by me.
I am using one configure script for all my software (330000 lines / 8 MB
of code), so I have 650 different tests in configure. As there is no way to 
restart a configure run, I would need to be able to completely finish
all test without a hang. 

Maybe this helps: After I retried to call configure several times, I get 
this error:

bash$ CC=cc CONFIG_NOFAIL=TRUE sh ./configure
./configure: Can't make pipes for command substitution!
configure: error: can not find sources in  or ..

restarting the current interactive bash temporarily fixes the problem.

In case that bash hangs, there are commands from "confiure" keeping hanging
around (e.g. grep) that go away if I finish the current interactive shell.


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

I did already understand this.

-- 
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
      js at cs.tu-berlin.de		(uni)  
      joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily