[Info-vax] C compiler snag

[John Reagan]

On Wednesday, May 19, 2021 at 8:50:32 AM UTC-4, John E. Malmberg wrote:
> On 5/19/2021 4:51 AM, Richard Levitte wrote: 
> > Hey folks, 
> > 
> > it's been long since I've been present here... been all busy with 
> > OpenSSL, not much time for something else.
> <snip>
> > 
> > ----- 
> > $ cc humpf.c 
> > 
> > #include "../something.h" 
> > .^ 
> > %CC-F-NOINCLFILEF, Cannot find file "../something.h" specified in #include directive. 
> > at line number 1 in file USER:[LEVITTE.TEST.CC-INCL-2.INCL]h.h;1 
> > ----- 
> > 
> > So my question is, is there any trick that I can do with the compiler 
> > to make this go through without error? i would rather not have to 
> > restructure the inclusion if I can.
> Only solution that I have found is to run a pre-build script to find and 
> re-edit the source code to change "../" to path or a logical name. 
> 
> I don't thing that is ever going to get fixed in the Alpha/IA64 compilers. 
> 
> Regards, 
> -John
I doubt the compilers are at fault.  At somepoint, we give that filespec to the CRTL's open/fopen.

Relative filespecs are controlled by various DECC$ feature logicals <insert ugly comment here>.
DECC$POSIX_COMPLIANT_PATHNAMES might help but setting that the DCL prompt before the
compilation might be too big of a hammer as some code <insert 2nd ugly comment here>.

I have the same issue with some of the files in LLVM that use relative filespecs.