From: Andrew STUBBS <andrew.stubbs@st.com>
To: gdb@sourceware.org
Subject: Re: Automatic dependency tracking
Date: Thu, 26 Jun 2008 09:48:00 -0000 [thread overview]
Message-ID: <486365E5.50601@st.com> (raw)
In-Reply-To: <20080625182858.GA25575@caradoc.them.org>
Daniel Jacobowitz wrote:
> Option two: we could require GNU make. GCC has done this for years,
> but binutils does not; it may be premature.
> Option three: we could manually list dependencies on generated files,
> and support dependencies on source files only on systems with GNU
> make. This effectively means GNU make is a requirement if you are
> hacking on GDB, but not to build GDB from a clean tree.
As I understand it, dependencies on generated files must always be hard
coded - otherwise the autogeneration build would fail (potentially, with
parallel make being worse), so these two options are the same.
There is no need to require GNU make for build purposes. It would only
be required for dependency tracking. The configure script can be made to
disable dependency tracking on incompatible make variants.
BTW, which are the GNU make specific features in question?
Andrew
next prev parent reply other threads:[~2008-06-26 9:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806152203.14626.pedro@codesourcery.com>
[not found] ` <u3anel69s.fsf@gnu.org>
[not found] ` <20080616012617.GA8944@caradoc.them.org>
[not found] ` <g35201$2uf$2@ger.gmane.org>
[not found] ` <m33an413yx.fsf@fleche.redhat.com>
2008-06-25 18:29 ` Daniel Jacobowitz
2008-06-25 19:30 ` Andreas Schwab
2008-06-25 21:35 ` Stan Shebs
2008-06-26 0:08 ` Tom Tromey
2008-06-26 1:47 ` Joel Brobecker
2008-06-26 9:48 ` Andrew STUBBS [this message]
2008-06-26 17:30 ` Tom Tromey
2008-06-27 10:23 ` Andrew STUBBS
2008-06-27 14:03 ` Daniel Jacobowitz
2008-06-27 16:09 ` Andrew STUBBS
2008-06-27 14:30 ` Tom Tromey
2008-06-28 19:20 ` Mark Kettenis
2008-06-28 19:31 ` Tom Tromey
2008-06-29 14:47 ` Daniel Jacobowitz
2008-06-29 15:36 ` Tom Tromey
2008-06-29 16:26 ` Tom Tromey
2008-06-29 14:42 ` Daniel Jacobowitz
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=486365E5.50601@st.com \
--to=andrew.stubbs@st.com \
--cc=gdb@sourceware.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: 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