public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: corsepiu@faw.uni-ulm.de
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/6310: gcc -MF vs. depcomp
Date: Mon, 15 Apr 2002 09:46:00 -0000	[thread overview]
Message-ID: <20020415163834.26468.qmail@sources.redhat.com> (raw)


>Number:         6310
>Category:       preprocessor
>Synopsis:       gcc -MF vs. depcomp
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 15 09:46:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Ralf Corsepius
>Release:        gcc-3.0.5 (20020410)
>Organization:
>Environment:
Linux i386/ELF
>Description:
automake > 1.4's depcomp uses
  "$@" -MT "$object" -MD -MP -MF "$tmpdepfile"
to compute dependencies.

This basically causes it to invoke gcc this way:
gcc -g -O2 -c hello.c -MT hello.o -MD -MP -MF .deps/hello.TPo

Which now causes warning of this kind:
gcc: unrecognized option `-MF'

This has worked for gcc-3.0.x up to 3.0.4, but has stopped working with post-3.0.4 gcc's from the gcc-3.0-branch.

AFAI understand, probably this patch below is the origin of this problem:

2002-03-24  Neil Booth  <neil@daikokuya.demon.co.uk>

	preprocessor/3951
	* gcc.c (cpp_options): Pass -MD through as -MD not -M -MF.       
>How-To-Repeat:
Compile an arbitrary C-sources with gcc-3.0.5 from CVS/gcc-3-0-branch depcomp-style:

Eg.:
gcc -g -O2 -c hello.c -MT hello.o -MD -MP -MF deps/hello.TPo

gcc: unrecognized option `-MF'
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-04-15 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15  9:46 corsepiu [this message]
2002-04-15 12:52 neil
2002-04-15 12:56 Neil Booth

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=20020415163834.26468.qmail@sources.redhat.com \
    --to=corsepiu@faw.uni-ulm.de \
    --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).