From: Alexandre Oliva <aoliva@redhat.com>
To: DJ Delorie <dj@delorie.com>
Cc: neroden@doctormoo.dyndns.org, gcc-patches@gcc.gnu.org,
binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: toplevel Makefile.in: autogenerate more
Date: Tue, 24 Sep 2002 19:44:00 -0000 [thread overview]
Message-ID: <orvg4ueqjq.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <200209242346.g8ONkL702524@envy.delorie.com>
On Sep 24, 2002, DJ Delorie <dj@delorie.com> wrote:
> As much as I like automation, this rule is bad. Not everyone has
> autogen, and those who don't shouldn't get penalized if they happen to
> get the timestamps rearranged.
If they use the recommended script, contrib/gcc_update, they'll get it
right.
If the rule is not to be activated, I'd rather have it in Makefile.in,
even if commented out, than not at all. How about:
Makefile.in: # Makefile.tpl Makefile.def # srcdir omitted for clarity
...
so, if one removes Makefile.in, we try to rebuild it, otherwise it
won't be modified just because you touched one of the other files, but
the deps are still documented.
Then, when we get --enable-maintainer-mode in the top level, we'll
just have to replace the `#' with @MAINT@.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2002-09-25 2:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 16:41 Nathanael Nerode
2002-09-24 16:46 ` DJ Delorie
2002-09-24 19:44 ` Alexandre Oliva [this message]
2002-09-25 2:26 ` Richard Earnshaw
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=orvg4ueqjq.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dj@delorie.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@doctormoo.dyndns.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