From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: mec@shout.net
Cc: gdb@sources.redhat.com
Subject: Re: Where to document supported versions of binutils?
Date: Wed, 05 Feb 2003 15:32:00 -0000 [thread overview]
Message-ID: <1438-Wed05Feb2003172939+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <200302050813.h158DS731675@duracef.shout.net> (message from Michael Elizabeth Chastain on Wed, 5 Feb 2003 02:13:28 -0600)
> Date: Wed, 5 Feb 2003 02:13:28 -0600
> From: Michael Elizabeth Chastain <mec@shout.net>
>
> We've learned that, on native i686-pc-linux-gnu, gdb has bugs
> with binutils prior to binutils 2.13. I saw this happen in my
> test bed, and David Carlton also saw it happening on his system.
>
> Where do we record this knowledge so that gdb users can see it?
>
> There doesn't appear to be a obvious section in NEWS or README
> for information like this.
I think README is the place to tell this.
We could also have the configure script run "ld --version" and print
something if it doesn't like the result.
next prev parent reply other threads:[~2003-02-05 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 8:13 Michael Elizabeth Chastain
2003-02-05 15:09 ` Andrew Cagney
2003-02-05 15:32 ` Eli Zaretskii [this message]
2003-02-05 15:53 Michael Elizabeth Chastain
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=1438-Wed05Feb2003172939+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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