public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: boehme@informatik.hu-berlin.de
To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: preprocessor/7558: preprocessor option -MM has change semantic
Date: Fri, 09 Aug 2002 09:26:00 -0000	[thread overview]
Message-ID: <E17dCS9-0006Y0-00@kosh.informatik.hu-berlin.de> (raw)


>Number:         7558
>Category:       preprocessor
>Synopsis:       preprocessor option -MM has change semantic
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Aug 09 09:26:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        3.1.1 (Debian testing/unstable)
>Organization:
>Environment:
System: Linux kosh 2.4.18-k7 #1 Sun Apr 14 13:19:11 EST 2002 i686 unknown unknown GNU/Linux
Architecture: i686

	
host: i386-pc-linux-gnu
build: i386-pc-linux-gnu
target: i386-pc-linux-gnu
configured with: /mnt/data/gcc-3.1/gcc-3.1-3.1.1ds3/src/configure -v --enable-languages=c,c++,java,f77,proto,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/-3.1 --enable-shared --with-system-zlib --enable-long-long --enable-nls --without-included-gettext --enable-clocale=gnu --enable-__cxa_atexit --enable-threads=posix --enable-java-gc=boehm --enable-objc-gc i386-linux
>Description:
	In gcc 3.1, -MM prints dependencies even to files included with
	angle brackets (<foo.h>), if those are found through -I options.
	This behaviour is unintuitive and a change from earlier versions.

	It appears that the only way to suppress these files is to use the
	-isystem directive, which is quite gcc specific and hard to use
	in a makefile that needs to work across different compilers, or
	that is generated by autoconf.
>How-To-Repeat:
	Compile the file

	#include <a.h>

	int
	main()
	{
	}

	with gcc -I. -MM; this gives

	a.o: a.c a.h

	even though a.h should not have been mentioned.

>Fix:
	No real work-around is known.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-08-09 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-09  9:26 boehme [this message]
2002-08-10  4:56 Neil Booth
2002-08-10 10:16 Martin v. Loewis
2002-08-11  2:06 Neil Booth
2002-08-11  2:06 Neil Booth
2002-08-11  2:48 Martin v. Loewis
2002-08-20 12:46 neil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E17dCS9-0006Y0-00@kosh.informatik.hu-berlin.de \
    --to=boehme@informatik.hu-berlin.de \
    --cc=debian-gcc@lists.debian.org \
    --cc=gcc-gnats@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).