This is what NFS specs says about it -
... to recover from an ESTALE error, an application must close the file or
directory where the error occurred, and reopen it so the NFS client can
resolve the pathname again and retrieve the new file handle.
And that is what safe_stat is doing - opening the
On Tue, 2019-12-17 at 13:17 +0530, nikhil jain wrote:
> A rule was processed and then as soon as it ends, the next dependent rule
> processed. It has to work on the object file generated by the first rule.
> But the timestamp of the file was older so the next rule did not process.
> I am on NFS.
I
Have to check with the older team mates if they have added safe_stat by
themselves. Thanks to them. It works for my case atleast.
No, I do not want to delete the object file before sending the target out.
That's not how make should work or I should make it work. It is not make
issue. It is issue w
On Tue, 2019-12-17 at 20:44 +0530, nikhil jain wrote:
> No, I do not want to delete the object file before sending the target
> out. That's not how make should work or I should make it work.
That is simply not true.
In virtually all cases rebuilding a target will involve deleting the old
one in s
Thank you Paul for the suggestions. Will think over them. Thanks for the
help.
On Tue, Dec 17, 2019 at 9:03 PM Paul Smith wrote:
> On Tue, 2019-12-17 at 20:44 +0530, nikhil jain wrote:
> > No, I do not want to delete the object file before sending the target
> > out. That's not how make should w
On Fri, 2019-12-06 at 12:57 +0900, Kiyoshi KANAZAWA wrote:
> Make tarball is distributed with gzip & bzip2 compression.
> One with gzip may be needed as basic one.
> But, how about change bzip2 to xz or lzip from next release ?
I have no problem with this idea.
