public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/6521: -MG creates dependency with wrong path Date: Wed, 08 May 2002 13:16:00 -0000 [thread overview] Message-ID: <20020508201604.24309.qmail@sources.redhat.com> (raw) The following reply was made to PR preprocessor/6521; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: Neil Booth <neil@daikokuya.demon.co.uk> Cc: Robert Spier <rspier@pobox.com>, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: preprocessor/6521: -MG creates dependency with wrong path Date: Wed, 8 May 2002 13:09:43 -0700 On Wed, May 08, 2002 at 06:31:05PM +0100, Neil Booth wrote: > > Good point, I'd not thought of that. I tend to think, though, that > -MG should never really be being used with <>, so whatever we do > isn't that important. That makes me like Robert's patch as it > deletes code, and does what is documented after all. This is true. And we have one registered complaint about the current behavior. We can always put it back later. Robert, would you be willing to clarify the documentation? > > ... perhaps -Mx <path> puts all the > > dependencies on generated files in <path>. (Where 'x' is some > > appropriate letter; I am too tired to think of a good one right now.) > > Hmm, I guess. We have too many options, really. It's a shame -MG > can't die. Fancy doing it with your "closing same file twice" patch? > 8-) FYI, I'm not likely to get to that issue until next week. If you want to fix it first, feel free. As for -MG with/without argument, I'm planning to look at it anyway when I move cpplib to its own directory (which will give us the leverage we need to do automatic dependency generation for the gcc directory). Let's not worry about it now. zw
next reply other threads:[~2002-05-08 20:16 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-08 13:16 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-08 14:36 Robert Spier 2002-05-08 14:33 neil 2002-05-08 14:26 Neil Booth 2002-05-08 13:56 Zack Weinberg 2002-05-08 13:26 Neil Booth 2002-05-08 10:36 Neil Booth 2002-05-08 9:36 Tom Tromey 2002-05-08 0:06 Zack Weinberg 2002-05-07 23:56 Roland McGrath 2002-05-07 23:46 Neil Booth 2002-05-07 23:36 Neil Booth 2002-05-07 23:16 Robert Spier 2002-05-04 1:16 Neil Booth 2002-05-03 13:06 Robert Spier 2002-05-03 9:56 Zack Weinberg 2002-05-03 5:56 Neil Booth 2002-04-30 13:36 rspier
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=20020508201604.24309.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).