From: DJ Delorie <dj@delorie.com>
To: bonzini@gnu.org
Cc: gdb@sources.redhat.com, gcc@gcc.gnu.org, binutils@sources.redhat.com
Subject: Re: (toplevel patch) Real targets for make.
Date: Thu, 28 Nov 2002 05:48:00 -0000 [thread overview]
Message-ID: <200211281348.gASDmCd06247@envy.delorie.com> (raw)
In-Reply-To: <20021128085615.GA10577@gnu.org> (message from Bonzini on Thu, 28 Nov 2002 03:56:15 -0500)
> Is it possible/planned/impossible to move the changes to Cygnus
> configure to binutils and gdb as well (and then possibly even
> autoconfiscate them at the same time, dumping Cygnus configure at
> last)?
It will happen. That patch is coming soon; most of the current
patches are to prepare for that step.
The only reason it hasn't happened in src yet is because it's being
done on a branch in gcc. If we don't mind unsync'ing src and gcc for
a while, we could start introducing the changes in src now.
> This would introduce the autogen dependency on binutils and gdb as
> well...
Autogen is never run automatically, so this should not be a problem.
Only maintainers who edit the toplevel Makefile need to run autogen.
next prev parent reply other threads:[~2002-11-28 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 0:56 Bonzini
2002-11-28 5:48 ` DJ Delorie [this message]
2002-11-29 0:12 ` Paolo Bonzini
2002-11-29 7:49 ` 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=200211281348.gASDmCd06247@envy.delorie.com \
--to=dj@delorie.com \
--cc=binutils@sources.redhat.com \
--cc=bonzini@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@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