make: execvp: awk: no such file or directory

[ciju john]

Hi group,

OpenVMS VMS 0 V8.2 AlphaServer_ES40 Alpha

I am experiencing problems with GNV make. Heres what I am seeing:

I have a makefile called GNUmakefile.portableserver which I have been using
as follows:

% make -f GNUmakefile.portableserver

After making some code changes make started failing with message "popen: bad file or name". The only thing of significance before this is the fact that I killed the previous make using Ctr-C. I have done that in the past without
any problems. I looked around to see if I may have some error or compiler state files and cleaned some generated files. This didn't help either. I then took the extreme step of rebooting the system. Now make comes back
with the message:

make: execvp: awk: no such file or directory

I have tried make with other makefiles in different directories with the same result. I am the only one around working on the system, so am sure no system files have been changed.

I am fairly new to OpenVMS, so any advice/help will be appreciated.

thanks,
Ciju

[Kris Clippeleyr]

Ciju,


I then took the extreme step of rebooting the system.

Indeed extreme.


make: execvp: awk: no such file or directory

Having no experience with "awk", I can see that "make" is looking for "awk". Are the command procedures that set up the environment for "awk" properly executed after reboot? Does the system know the verb "awk"?
Could you investigate?
Greetz,
Kris (aka Qkcl)

[Karl Rohwedder]

Has the GNV$STARTUP been executed during startup?

regards Kalle

[ciju john]

Hi Kris & Kalle,

Thanks for your input. I wasn't myself aware of a relationship between make and awk, but since awk is one of the most prevalent text processing lang, I am not surprised at where it pops up.

Anyway my solution was to comment out the C RTL logicals

$! DEFINE DECC$EFS_CASE_PRESERVE ENABLE
$! SET PROCESS/CASE_LOOKUP=SENSITIVE

Apparently 'make' couldn't find the case specific 'awk' it was searching for and the solution was to turn off case sensitivity.

It confounds me however why this problem arose when 10 minutes ago, the same terminal was doing builds just fine. Voodooo

thanks all,

Ciju