This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: top level: make more dependencies explicit
- From: Nathanael Nerode <neroden at doctormoo dot dyndns dot org>
- To: Andrew Cagney <ac131313 at redhat dot com>
- Cc: gdb-patches at sources dot redhat dot com, binutils at sources dot redhat dot com,gcc-patches at gcc dot gnu dot org
- Date: Sun, 29 Sep 2002 13:26:08 -0400
- Subject: Re: top level: make more dependencies explicit
- References: <20020929165232.GA27545@doctormoo.dyndns.org> <3D9733C2.2010405@redhat.com>
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. :-)
1. Is there a simple way to stop doing this, by generating a proper
Makefile?
2. If not, how about generating an alternate file 'Makefile.in.for.taz'
(better names solicited) for these rules to use, so that the ordinary
Makefile.in can keep progressing? Would that do? I think that's pretty
easy.
--Nathanael