This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug preprocessor/15220] [3.3/3.4/4.0 regression] "gcc -E -MM -MG" reports missing system headers in source directory
- From: "prj-bugzilla-gcc at multivac dot cwru dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 Dec 2004 19:10:23 -0000
- Subject: [Bug preprocessor/15220] [3.3/3.4/4.0 regression] "gcc -E -MM -MG" reports missing system headers in source directory
- References: <20040430055232.15220.prj-bugzilla-gcc@multivac.cwru.edu>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From prj-bugzilla-gcc at multivac dot cwru dot edu 2004-12-13 19:10 -------
Ok, bug preprocessor/6521 looks like it had the same symptom I see now with 3.4.
Neil and Zack didn't think it was worth fixing at first, but it did get fixed,
and managed to stay fixed through 3.3.
I agree with the comments that it's not very important how -MG handles <>
headers, but what does matter to me is that they are not made to look like ""
headers. I use "gcc -E -MM -MG foo.c 2> /dev/null" and parse the output to find
out which "" headers would need to be generated in order to compile this file.
If <> headers are included in that list, I get unnecessary build failures, since
some headers that I can't provide appear to be needed (but actually aren't). It
would be ok with me if <> headers were ignored entirely for -MG. As it is, they
are ignored only if they exist - otherwise, 3.4 gives misleading output, 3.3 is
silent, and earlier versions warn.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15220