From: Ian Lance Taylor <ian@wasabisystems.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: Daniel Jacobowitz <drow@false.org>,
Eli Zaretskii <eliz@elta.co.il>,
gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Generate makefile dependencies
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <m3fzcjqk51.fsf@gossamer.airs.com> (raw)
Message-ID: <20040319000900.dPrAYLFOXfz-TYzyFF2dtSoBDDz9hshii5Qdfb4mfFY@z> (raw)
In-Reply-To: <404CB609.4070609@gnu.org>
Andrew Cagney <cagney@gnu.org> writes:
> > BTW, your comment about running automake to update deps in BFD is
> > actually incorrect. You run 'make dep-am', which IIRC seds Makefile.am
> > and maye regenerates Makefile.in; the dependencies aren't managed by
> > automake. Recent versions of automake do have top-notch dependency
> > support though.
>
> It appears to eventually run "gcc -MM" ... :-(
Assuming you are talking about 'make dep-am' in the binutils, that is
irrelevant.
'make dep-am' is run by a binutils maintainer, not by an ordinary
user. It does happen to run gcc -MM, so the binutils maintainer is
required to have gcc installed. However, the result is the correct
dependencies for any compiler, and those dependencies are then present
in the Makefile for any user, regardless of what compiler they use.
Ian
next prev parent reply other threads:[~2004-03-08 18: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 [this message]
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
2004-03-08 19:16 ` Daniel Jacobowitz
2004-03-19 0:09 ` Ian Lance Taylor
2004-03-19 0:09 ` Eli Zaretskii
2004-03-15 18:21 ` Andrew Cagney
2004-03-19 0:09 ` 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
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=m3fzcjqk51.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=eliz@elta.co.il \
--cc=gdb-patches@sources.redhat.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