From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: Ian Lance Taylor <ian@wasabisystems.com>,
Eli Zaretskii <eliz@elta.co.il>,
gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Generate makefile dependencies
Date: Mon, 08 Mar 2004 19:16:00 -0000 [thread overview]
Message-ID: <20040308191607.GA26243@nevyn.them.org> (raw)
Message-ID: <20040308191600.eH696ekXQaEmUN5Ntl4y9Aqcs8Ne2nce2_HB1ErMj5g@z> (raw)
In-Reply-To: <404CC47A.4090207@gnu.org>
On Mon, Mar 08, 2004 at 02:07:38PM -0500, Andrew Cagney wrote:
> For what its worth, I know of three ways to maintain a dependency list:
>
> - update at compile time
>
> - update at configure time
>
> - update at release time
>
> For someone grabbing random sources, the first is most likely correct,
> the last is most likley out-of-date. The middle is a compromise, at
> least correct at the start of each build.
Should we look at using automake's depcomp script instead, which does
the first? For more than just GCC.
But hey, I've got no objection to the sed magic.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-08 19:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 0:36 Andrew Cagney
2004-03-08 6:09 ` Eli Zaretskii
2004-03-19 0:09 ` Andrew Cagney
2004-03-08 16:24 ` Andrew Cagney
2004-03-08 17:24 ` Eli Zaretskii
2004-03-08 17:58 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Eli Zaretskii
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-08 17:29 ` Daniel Jacobowitz
2004-03-08 17:50 ` Ian Lance Taylor
2004-03-19 0:09 ` Ian Lance Taylor
2004-03-19 0:09 ` Andrew Cagney
2004-03-08 18:06 ` Andrew Cagney
2004-03-08 18:11 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Andrew Cagney
2004-03-08 18:35 ` Andrew Cagney
2004-03-08 23:13 ` Michael Snyder
2004-03-11 17:23 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Michael Snyder
2004-03-08 18:16 ` Ian Lance Taylor
2004-03-19 0:09 ` Ian Lance Taylor
2004-03-19 0:09 ` Andrew Cagney
2004-03-08 19:07 ` Andrew Cagney
2004-03-08 19:26 ` Ian Lance Taylor
2004-03-19 0:09 ` Ian Lance Taylor
2004-03-19 0:09 ` Daniel Jacobowitz [this message]
2004-03-08 19:16 ` Daniel Jacobowitz
2004-03-19 0:09 ` Eli Zaretskii
2004-03-15 18:21 ` Andrew Cagney
2004-03-19 0:09 ` Ian Lance Taylor
2004-03-15 18:53 ` Ian Lance Taylor
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
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=20040308191607.GA26243@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=eliz@elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=ian@wasabisystems.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