%% Hua Yu <[EMAIL PROTECTED]> writes:
hy> Well, I also noticed that gmake produces a different message in
hy> this case, comparing to when it gets a non-existent target. If
hy> target names are strings, the "No rule to make target ..." message
hy> is much clearer and easier for me to debu
BTW, the problem seems to be more pronounced with a complex makefile.
> gmake "obj.sun4_solaris/JanusLib.a(../JanusLib/obj.sun4_solaris/codebook.o)"
> > gmake "obj.sun4_solaris/JanusLib.a(codebook.o)"
> gmake "obj.sun4_solaris/JanusLib.a(obj.sun4_solaris/codebook.o)"
are all giving different resul
In message <[EMAIL PROTECTED]>, "Paul D
. Smith" writes:
>%% [EMAIL PROTECTED] writes:
>
> h> I'm not sure whether it's a bug or a feature. But it's annoying
> h> to me at the very least. Targets in a makefile are filenames,
> h> in most cases.
>
>They may be filenames in most cases, but make
