[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GNU Make 4.1 carrying on after -f missingfile.mak
From: |
Edward Welbourne |
Subject: |
Re: GNU Make 4.1 carrying on after -f missingfile.mak |
Date: |
Wed, 24 May 2017 11:29:24 +0000 |
Jonny Grant (24 May 2017 12:27)
> In that successful case, would the "No such file or directory" message
> not be visible?
My guess is that it would be displayed, by the initial run of make; but
then make would re-invoke itself and do its job. As long as the rule to
make the missing make-file doesn't suppress printing, you'd see the
command that creates the make-file in between, which should be a
reasonable clue as to what's going on.
> BTW, I guess it is stat@() or open() rather than opendir(), if ENOENT is
> in errno, could we just output "No such file"? ENOENT is a bad, because
> it is used for directories too
My guess is that error-reporting code uses some generic routine that
reports the standard message for the errno value, which would make it
fiddly to handle this error specially, but you'd have to study make's
code to be sure.
Eddy.
Re: GNU Make 4.1 carrying on after -f missingfile.mak, Paul Smith, 2017/05/24