Follow-up Comment #1, bug #66424 (group make): The problem is that this build recreates the file */home/cendio/cenbuild/repo/rpmbuild/BUILD/glibc-2.12.2/build/bits/stdio_lim.st*, and that cause the file */home/cendio/cenbuild/repo/rpmbuild/BUILD/glibc-2.12.2/build/bits/stdio_lim.h* to be considered out of date.
But when make tries to rebuild that file, the recipe is a no-op:
Makerules:1305: update target
'/home/cendio/cenbuild/repo/rpmbuild/BUILD/glibc-2.12.2/build/bits/stdio_lim.h'
due to:
/home/cendio/cenbuild/repo/rpmbuild/BUILD/glibc-2.12.2/build/bits/stdio_lim.st
:
Successfully remade target file
'/home/cendio/cenbuild/repo/rpmbuild/BUILD/glibc-2.12.2/build/bits/stdio_lim.h'.
The targhet file stdio_lim.h is a prerequisite
Note how the recipe to rebuild stdio_lim.h is just *:* which is the shell's
no-op operator. That means the timestamp for stdio_lim.h is not updated and
it's still considered out of date the next time we look at it.
This is very definitely not the same thing at all as bug #66037
I didn't get to the bottom of this and it's surely a mystery as to why it
works for most builds but not all. glibc 2.12.2 is over 15 years old and its
makefiles could very well have some issue when used with the latest version of
GNU Make.
It would be interesting to get the debug output when using GNU Make 4.4 to see
if we can norrow down where it was introduced a little bit more. Also
interesting would be to verify if it still happens with the latest Git version
(but there's no source tarball for this).
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66424>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
