From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: 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: <404CBCE4.6070401@gnu.org> (raw)
In-Reply-To: <20040308181142.GA23441@nevyn.them.org>
>>>So what about using the output of gcc -MM (or one of the other -M
>>>> >options?) to generate dependencies in the source directory, like BFD
>>>> >does?
>>
>>>
>>> How is embedding this stuff in the source directory better?
>
>
> Because it doesn't need to rely on assumptions about the GDB coding
> style, and it doesn't require parsing all the source files when we
> configure?
Er, that's a postive - the dependency list is guarenteed to always match
the shipped source.
> It's like regenerating configure; we try not to run
> autoconf during the build process, and not just because autoconf is so
> finicky.
Andrew
WARNING: multiple messages have this Message-ID
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: Eli Zaretskii <eliz@elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Generate makefile dependencies
Date: Mon, 08 Mar 2004 18:35:00 -0000 [thread overview]
Message-ID: <404CBCE4.6070401@gnu.org> (raw)
Message-ID: <20040308183500.ntcdR8t4sJoc40zwPapuPrY5XKF5MPpC2sdOn2ECmr8@z> (raw)
In-Reply-To: <20040308181142.GA23441@nevyn.them.org>
>>>So what about using the output of gcc -MM (or one of the other -M
>>>> >options?) to generate dependencies in the source directory, like BFD
>>>> >does?
>>
>>>
>>> How is embedding this stuff in the source directory better?
>
>
> Because it doesn't need to rely on assumptions about the GDB coding
> style, and it doesn't require parsing all the source files when we
> configure?
Er, that's a postive - the dependency list is guarenteed to always match
the shipped source.
> It's like regenerating configure; we try not to run
> autoconf during the build process, and not just because autoconf is so
> finicky.
Andrew
next prev parent reply other threads:[~2004-03-08 18:35 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 [this message]
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
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 ` 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=404CBCE4.6070401@gnu.org \
--to=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