> From: Orgad Shaneh <org...@gmail.com> > Date: Fri, 16 Jun 2017 17:05:58 +0300 > Cc: "bug-make@gnu.org" <bug-make@gnu.org>, Alexey Pavlov <alex...@gmail.com> > > Ah, okay. But then the problem is not with child processes of g++, > it's with g++ itself, right? > > The child process cc1plus has the file open for writing, and g++ and make > fail to delete it.
Then what exactly do you expect Make to do about that? We cannot prevent child processes from opening files in a way that disallows deletion by Make. We could probably wait in a loop until the deletion succeeds, but I'm not sure this will work. Can you try adding such a loop to Make? My system reproduces this with too low probability, so I'm not a good candidate for this experiment. > And on my system, the file is removed after Make exits, when I use > your recipe. > > Do you run mingw make or msys make? MinGW Make, of course. The same one you found on ezwinports. _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
