https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
--- Comment #13 from Allan W. Macdonald ---
Ahhh, so, "to get back the old behaviour" (as @ Richard Biener put it), this
seems to work (at least with my project):
%.d: %.c
gcc -MM -MD -dumpbase '' $<
Not obvious in the gcc 11.3.0 manua
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
--- Comment #11 from Allan W. Macdonald ---
The makefiles I've been maintaining contain a mechanism to make sure that any
change in a locally-included file will cause the c file that includes it to be
compiled again, like so:
### Extract of mak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
--- Comment #8 from Allan W. Macdonald ---
(In reply to Andrew Pinski from comment #7)
> Does using -c instead help?
Why would we want to compile the file without FIRST checking for dependencies?
The .d file needs to be up to date so that an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
--- Comment #6 from Allan W. Macdonald ---
(In reply to Allan W. Macdonald from comment #5)
> Here is a workaround:
or just
gcc -E -MMD test.c > /dev/null
if gcc-11 is default gcc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
Allan W. Macdonald changed:
What|Removed |Added
CC||allan.w.macdonald at gmail dot
com
