From: Doug Evans <dje@transmeta.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: law@redhat.com, tim@hollebeek.com,
Nathanael Nerode <neroden@doctormoo.dyndns.org>,
gcc@gcc.gnu.org, gdb@sources.redhat.com,
binutils@sources.redhat.com
Subject: Re: Top Level Autoconfiscation Status
Date: Wed, 10 Jul 2002 15:49:00 -0000 [thread overview]
Message-ID: <15660.47528.411836.22536@casey.transmeta.com> (raw)
In-Reply-To: <3D2CB4C8.2090005@ges.redhat.com>
Andrew Cagney writes:
> > >I believe that both BFD and READLINE (in src) are currently broken in
> > >this regard (DJE reported problems). There was a somewhat underwelming
> > >response (see binutils) when it was suggested that developers should be
> > >responsible for ensuring that this obscure functionality continues to work.
Obscure?! Underwhelming?!
Has there been some email I missed? [I was on vacation for awhile.]
I only found two problems. The readline one seemed trivially
fixable. Haven't put much thought into the other one
(top level configure specifying full path for --with-gcc-version-trigger
or some such, not bfd).
If this feature is removed (by the fact that bugs when found won't
be fixed) that'd be a great shame!
next prev parent reply other threads:[~2002-07-10 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-30 18:43 Nathanael Nerode
2002-06-30 19:43 ` Tim Hollebeek
2002-07-01 9:00 ` Jeff Law
2002-07-01 9:21 ` Andrew Cagney
2002-07-01 10:22 ` Jeff Law
2002-07-10 15:27 ` Andrew Cagney
2002-07-10 15:49 ` Doug Evans [this message]
2002-06-30 19:44 ` Daniel Jacobowitz
2002-06-30 21:19 ` Tom Tromey
2002-07-01 3:41 ` Andrea 'Fyre Wyzard' Bocci
2002-07-01 7:42 ` Ben Elliston
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=15660.47528.411836.22536@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=ac131313@ges.redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=law@redhat.com \
--cc=neroden@doctormoo.dyndns.org \
--cc=tim@hollebeek.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