I use EISNER and whatever version of GNV is installed on it (without privs I have no idea to find out what it really is).
>>>
bash$ make -f GNU_a.mms
make: Nothing to be done for all'.
<<<
Try a 'make -dnf GNU_a.mms >x.x'
and look for
grep -A5 "Considering target file \`P2C_LTVT_MODUL.OBJ'." x.x
You will see that the GNV make uses a stem `P2C_LTVT_MODUL.OBJ' and will
never be able to match your implicit rule with that stem.
Try a 'make -dnf DESCRIP.MMS >y.y'
and look for
grep -A5 "Considering target file \`P2C_LTVT_MODUL.o'." y.y
You will see that the GNV make uses a stem `P2C_LTVT_MODUL' and it will find a match for your implicit rule with the source `P2C_LTVT_MODUL.OBJ.c', which actually is P2C_LTVT_MODUL.C.
Are you surprised? And in the previous note you even had .c.o for the rule and .c source files (this confused me and I hope I comment on the right, last version).
Anyway, try this:
bash-4.2$ diff -ub GNU_a.mms a.mms
--- GNU_a.mms Sat Feb 16 05:44:14 2013
+++ a.mms Sat Feb 16 07:59:03 2013
@@ -1,6 +1,9 @@
SHELL=/bin/dcl
CC=cc
+.SUFFIXES:
+.SUFFIXES: .c .OBJ
+
all: P2C_LTVT_MODUL.OBJ P2C_LTVLEIPL_MODUL.OBJ
.c.OBJ:
bash-4.2$ make -nf a.mms
/bin/dcl cc P2C_LTVT_MODUL.C
/bin/dcl cc P2C_LTVLEIPL_MODUL.C
bash-4.2$
Sure enough, a VMS version of GNU make should have .OBJ in the suffixes by default. However, in GNV GNU make only has the .o in the suffixes, see below.
>>>
So it does not seem to be a filename casing problem using my version of GNV make. Also can you run GNV make under a bash shell ? As you can notice it from the bash$ dcl show proc/all, I run with Parse Style: Extended. Also the above and the previous run makes me think since when something which pretends to be Unix compatible is filename case insensitive ?!!?
<<<
From the sources I know that GNU make for VMS does some UPPER- or lowercasing before hashing all the filenames read from a directory. So I would not bet that this would not cause problems.
I expect make's behavior to be the same, no matter whether it is invoked from the bash or from DCL. It's not obvious but that's the case:
$ mc gnv$gnu:[bin]bash -c "make -nf DESCRIP.MMS"
cc -c -o P2C_LTVT_MODUL.o P2C_LTVT_MODUL.c
cc -c -o P2C_LTVLEIPL_MODUL.o P2C_LTVLEIPL_MODUL.c
$
$ mc gnv$gnu:[bin]make. -nf DESCRIP.MMS
/EISNER$LDA1/VMS$COMMON/gnv/bin/make.: Nothing to be done for all'.
$
$ SHELL="bash
$ mc gnv$gnu:[bin]make. -nf DESCRIP.MMS
cc -c -o P2C_LTVT_MODUL.o P2C_LTVT_MODUL.C
cc -c -o P2C_LTVLEIPL_MODUL.o P2C_LTVLEIPL_MODUL.C
$
So SHELL="bash" triggers other default suffixes. Makes sense, or?
What is "Unix compatible"? GNV is not even Posix compliant. If I would need "Unix compatibility" I would run Tru64 or Linux on my Alpha. :-)
With "Case Lookup: Blind" I would not expect case sensitivity. As far as I know, setting the lookup to be case sensitive is not recommended for GNV. As you probably know, VMS was not designed to be case sensitive and all the changes for it so far are not guaranteed to always work as expected.
