From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com
Subject: [rfa] PROBLEMS: i[3456]*-linux-*: warn about old binutils
Date: Wed, 05 Feb 2003 16:17:00 -0000 [thread overview]
Message-ID: <200302051617.h15GHJv04986@duracef.shout.net> (raw)
This patch warns about old versions of binutils on i[3456]86-*-linux*.
OK to apply?
Michael C
===
2003-02-05 Michael Chastain <mec@shout.net>
* PROBLEMS (i[3456]86-*-linux*): Warn about binutils
2.12.1 and earlier versions.
Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.11
diff -u -r1.11 PROBLEMS
--- PROBLEMS 10 Dec 2002 21:24:47 -0000 1.11
+++ PROBLEMS 5 Feb 2003 16:11:17 -0000
@@ -65,3 +65,12 @@
$ make CFLAGS='-O2 -D__digital__'
+
+i[3456]86-*-linux*
+------------------
+
+GNU binutils 2.12.1 and earlier versions do not work properly with gdb.
+If you use GNU binutils, upgrade to version 2.13 or later. You can
+check the version of binutils with the command:
+
+ $ ld --version
next reply other threads:[~2003-02-05 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 16:17 Michael Elizabeth Chastain [this message]
2003-02-05 17:07 ` Andrew Cagney
2003-02-05 17:37 Michael Elizabeth Chastain
2003-02-05 17:41 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=200302051617.h15GHJv04986@duracef.shout.net \
--to=mec@shout.net \
--cc=gdb-patches@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