From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Nick Clifton <nickc@redhat.com>,
binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: [Patch] ld config bits for i860 coff target
Date: Fri, 15 Aug 2003 16:00:00 -0000 [thread overview]
Message-ID: <3F3D039C.2070803@redhat.com> (raw)
In-Reply-To: <20030815152059.GA30887@nevyn.them.org>
> On Fri, Aug 15, 2003 at 10:58:26AM -0400, Andrew Cagney wrote:
>
>> How quickly people forget :-(
>>
>> The developer tools came to use specific generated versions of those
>> files because people encountered host dependant problems with the
>> generators. Guarenteed that the generated files being run, were
>> identical across all fronts.
>
>
> I didn't forget. If we re-encounter such problems then we can go back
> to having blessed tarballs. Your "idealistic" goal is a lot more
> realistic than you seem to think; the autotools have matured a great
> deal.
Note also that any GCC developer's opinions need to be heavily, if not
totally discounted when it comes to GDB. Its GDB, and not GCC that will
get to sort out GDB's mess.
I'd like to see hard evidence that the proposal works before considering
an implementation.
Andrew
next prev parent reply other threads:[~2003-08-15 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3he4wgjwt.fsf@redhat.com>
[not found] ` <Pine.GSO.4.33.0308051154230.29414-100000@forest.owlnet.rice.edu>
[not found] ` <20030806014541.GY27145@bubble.sa.bigpond.net.au>
[not found] ` <20030806025553.GA14245@nevyn.them.org>
[not found] ` <20030806040345.GB27145@bubble.sa.bigpond.net.au>
[not found] ` <m365lbgobb.fsf@redhat.com>
[not found] ` <20030814045151.GA28747@nevyn.them.org>
[not found] ` <20030814052535.GU27145@bubble.sa.bigpond.net.au>
[not found] ` <m3y8xwjh68.fsf@redhat.com>
2003-08-15 15:19 ` Andrew Cagney
2003-08-15 15:21 ` Daniel Jacobowitz
2003-08-15 16:00 ` Andrew Cagney [this message]
2003-08-15 21:27 ` Daniel Jacobowitz
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=3F3D039C.2070803@redhat.com \
--to=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=nickc@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