public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rjflory@hiwaay.net
To: gcc-gnats@gcc.gnu.org
Cc: ron.flory@adtran.com
Subject: c/3500: location of output .d (dependancy file from -MMR switch) has changed from previous releases
Date: Sat, 30 Jun 2001 14:46:00 -0000	[thread overview]
Message-ID: <20010630214116.31557.qmail@sourceware.cygnus.com> (raw)

>Number:         3500
>Category:       c
>Synopsis:       location of output .d (dependancy file from -MMR switch) has changed from previous releases
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 30 14:46:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     ron flory rjflory@hiwaay.net
>Release:        gcc 2.96 and gcc 2.96
>Organization:
>Environment:
RedHat Linux (x86) 7.1 on several x86 (intel/amd) systems.

 Problem present in stock RedHay 7.1 as well as recent gcc
RPM updates (early june 2001).
>Description:
 The -MMR compiler switch generates an output file 
containing a 'rule' suitable for direct inport into GNU 
'make'.  Many projects use this for auto dependancy
generation.

 Typical use: gcc -MMR -c -o obj/xyz.o xyz.cpp

 Until recently, the output dependancy file was placed in
the 'current' directory, however with gcc 2.95 and 2.96
the dependancy file '*.d' is placed in the path specified
in the compiler '-o' directive.  If the user places the 
object in a different directory than the current directory,
the dependancy file now appears to be placed in the 
directory specified to hold the object file.

 This breaks a great many existing project makefiles because
the expected '*.d' dependancy file is no longer in the
'current' directory, but in the 'objects' directory
instead.
>How-To-Repeat:
for any single C/C++ source file including files in addition
to 'syatem' headers:

 gcc -MMR -c -o obj/xyz.o xyz.cpp

 the dependancy file xyx.d is now placed in obj/xyz.d
 instead of the current directory, as it used to be.
>Fix:
Recent compiler changes have probably forgotten to strip
path information from the output filename when creating 
the '.d' dependancy output file.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="non necessary."
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="non necessary."


                 reply	other threads:[~2001-06-30 14:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010630214116.31557.qmail@sourceware.cygnus.com \
    --to=rjflory@hiwaay.net \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=ron.flory@adtran.com \
    /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).