From: "H. J. Lu" <hjl@lucon.org>
To: Andrew Cagney <ac131313@redhat.com>,
Nathanael Nerode <neroden@doctormoo.dyndns.org>,
gdb-patches@sources.redhat.com, binutils@sources.redhat.com,
gcc-patches@gcc.gnu.org
Subject: Re: top level: make more dependencies explicit
Date: Sun, 29 Sep 2002 12:58:00 -0000 [thread overview]
Message-ID: <20020929125845.A8761@lucon.org> (raw)
In-Reply-To: <20020929195118.GA5786@nevyn.them.org>; from drow@mvista.com on Sun, Sep 29, 2002 at 03:51:18PM -0400
On Sun, Sep 29, 2002 at 03:51:18PM -0400, Daniel Jacobowitz wrote:
> On Sun, Sep 29, 2002 at 01:45:40PM -0400, Andrew Cagney wrote:
> > >On Sun, Sep 29, 2002 at 01:09:22PM -0400, Andrew Cagney wrote:
> > >
> > >>Nathanael,
> > >>
> > >>FYI, I'm about to revert this change:
> > >>
> > >>2002-09-25 Nathanael Nerode <neroden@gcc.gnu.org>
> > >>
> > >> * Makefile.tpl: Make subsituted variables more autoconfy.
> > >> * Makefile.in: Regenerate.
> > >> * configure: Make seds more autoconfy.
> > >>
> > >>It breaks both the GDB and BINUITLS snapshot processes. Details to
> > >>follow, however, suggest a short pause.
> > >
> > >Uh... yuck.
> > >
> > >Are there some details on the GDB and BINUTILS snapshot processes so that
> > >I can fix *them*? This change is going to happen eventually, even if
> > >it's reverted for now; the Makefile changes will be necessary for
> > >autoonfiscation.
> > >
> > >Wait, let me look at Makefile.in...
> > >
> > >Ewwwww. The taz rules use Makefile.in *as a Makefile*.
> > >That's the root of the problem, isn't it? Incidentally, that's
> > >disgusting. :-)
> >
> > Well I think ``SHELL = @config_shell@'' is ugly :-) Why can't the
> > configury code edit ``s/^SHELL =.*/SHELL = $.../''.
>
> Because that's disgusting? Having something which doesn't look like a
> configury-overridden variable be edited in configure is very fragile.
>
> > The mechanism is very old (it pre-dates me as GDB release engineer).
> > Changing it is going to involve updates to many things - snapshot
> > scripts, release process doco, .... so won't happen overnight.
>
> GCC has had a separate script to make releases for years and years.
> It's time GDB and Binutils did the same.
FWIW, I like the current GDB release scheme a lot. It is very useful in
my envrionment.
H.J.
next prev parent reply other threads:[~2002-09-29 19:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 9:56 Nathanael Nerode
2002-09-29 10:09 ` Andrew Cagney
2002-09-29 10:30 ` Nathanael Nerode
2002-09-29 10:45 ` Andrew Cagney
2002-09-29 12:51 ` Daniel Jacobowitz
2002-09-29 12:58 ` H. J. Lu [this message]
[not found] ` <20020929174544.GA30373@doctormoo.dyndns.org>
[not found] ` <3D974828.4050009@redhat.com>
[not found] ` <20020929190100.GA31652@doctormoo.dyndns.org>
[not found] ` <3D9764F8.7000100@redhat.com>
2002-09-29 14:50 ` Top level: Separate src release scripts from Makefile Nathanael Nerode
2002-09-29 15:13 ` DJ Delorie
2002-09-29 15:23 ` Nathanael Nerode
2002-09-30 11:47 ` Alexandre Oliva
2002-09-30 9:49 ` top level: make more dependencies explicit DJ Delorie
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=20020929125845.A8761@lucon.org \
--to=hjl@lucon.org \
--cc=ac131313@redhat.com \
--cc=binutils@sources.redhat.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