From: Tom Tromey <tromey@cygnus.com>
To: egcs@egcs.cygnus.com
Subject: Re: -MD behavior does not match documentation
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <87g10ez91q.fsf@cygnus.com> (raw)
Message-ID: <19990930180200.u5M2wPFaRnRr_MNGRiYeTnXwBsjoEMKvpYWbgAR-Lmg@z> (raw)
In-Reply-To: <19990916225821.E20920@pcep-jamie.cern.ch>
Jamie> This is why I use the SUNPRO_DEPENDENCIES environment variable.
Jamie> Sadly It's not documented, but it's the only way to get
Jamie> dependencies to do the right thing when the -o name is
Jamie> different to the source name. For example, when compiling one
Jamie> source file to multiple target objects, with different -D
Jamie> settings. DEPENDENCIES_OUTPUT doesn't work for this.
I'd eventually like to change the dependency generation "UI".
Automake in particular wants a few things not provided by gcc:
* It wants to pick the name of the resulting dependency file. I
propose a new "-MF FILE" option to do this.
* It wants to pick the name of the target put into the dependency
file. I propose a new "-MT STRING" option. (Sometimes having gcc
guess the answer can't be right: for instance when automake is
generating libtool objects, we want both the ".o" and the ".lo" forms
to be named.)
* It wants to have gcc generate a phony target for each header
mentioned in the result. E.g., if gcc generates "foo.o: foo.h", it
should also add "foo.h:" to the file. This is a fix for the "deleted
header file" problem that plagues most automatic dependency tracking
schemes. I propose a new "-MA" (A for "Automake" -- no imagination
here) option.
Right now automake goes through some rather ugly gyrations
("-Wp,-MD,..." followed by hairy sed invocations) to get what it
wants. The other solutions are, for various reasons, not acceptable.
I don't recall why SUNPRO_DEPENDENCIES isn't acceptable. Perhaps it
doesn't let me pick the output file's name. Or perhaps, like the
DEPENDENCIES_OUTPUT macro, it acts like -MM and not -M.
I'd also like all the front ends to agree to work the same way in this
area.
I've been meaning to do this for a long time, but I rarely have
hacking time that isn't already allocated. Bummer.
Tom
next prev parent reply other threads:[~1999-09-30 18:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-16 7:24 I Lee Hetherington
1999-09-16 8:03 ` Richard Hadsell
1999-09-16 8:16 ` I Lee Hetherington
1999-09-30 18:02 ` I Lee Hetherington
1999-09-30 18:02 ` Richard Hadsell
1999-09-16 13:58 ` Jamie Lokier
1999-09-16 17:15 ` Tom Tromey [this message]
1999-09-30 18:02 ` Tom Tromey
1999-11-27 18:46 ` Tom Tromey
1999-11-30 23:37 ` Tom Tromey
1999-12-03 14:02 ` Need Help pogde prashant
1999-12-03 15:34 ` Joern Rennecke
1999-12-31 23:54 ` Joern Rennecke
1999-12-31 23:54 ` pogde prashant
1999-09-30 18:02 ` -MD behavior does not match documentation Jamie Lokier
1999-09-30 18:02 ` I Lee Hetherington
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=87g10ez91q.fsf@cygnus.com \
--to=tromey@cygnus.com \
--cc=egcs@egcs.cygnus.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).