[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU Make 4.1 carrying on after -f missingfile.mak

From: Jonny Grant
Subject: Re: GNU Make 4.1 carrying on after -f missingfile.mak
Date: Wed, 24 May 2017 22:27:45 +1200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1

On 24/05/17 21:25, Edward Welbourne wrote:
Jonny Grant (24 May 2017 10:15)
So if missingfile.mak was generated? Would make then read it in and
process it?

Yes, it would - if it can find a rule that lets it make the file it was
told to use, it'll exercise that rule and then restart itself.  On this
restart, it would find the file exists and get on with using it.

I guess I thought it would just be better for make to halt and exit
after that line
make: missingfile.mak: No such file or directory

When there *is* a way for it to generate the missing file, generating it
and restarting (after producing this warning) is surely a better
response - it lets make succeed in doing what the user asked for,


Hi Eddy
In that successful case, would the "No such file or directory" message not be visible?

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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]