From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com
Subject: [rfa] PROBLEMS (i[3456]86-*-linux*): Require glibc 2.1.3 or later
Date: Tue, 25 Feb 2003 15:49:00 -0000 [thread overview]
Message-ID: <200302251549.h1PFnQS05835@duracef.shout.net> (raw)
This patch documents a problem when building gdb with old libc or glibc.
The problem is a missing definition of 'uintptr_t'. This is PR gdb/660,
and I have also seen this problem reported on bug-gdb. We have so many
users that we see amazing version skew in the field.
I don't think we should fix this problem; I would rather just add a
requirement that people upgrade their glibc (or their libc5). Then we
can point to the requirement in the PROBLEMS file and close PR's.
If somebody (perhaps the thread people) says that we need to jack up
the requirement from 2.1.3 to whatever, I'm open to that. I just want
to document an actual requirement.
Testing: I haven't actually built with glibc 2.1.3, but I did check
the glibc source code and found the 'uintptr_t' definition in there.
OK to commit?
Michael C
2003-02-25 Michael Chastain <mec@shout.net>
* PROBLEMS (i[3456]86-*-linux*): Require glibc 2.1.3 or later
to avoid uintptr_t definition problems.
Index: PROBLEMS
===================================================================
RCS file: /cvs/src/src/gdb/PROBLEMS,v
retrieving revision 1.12
diff -u -r1.12 PROBLEMS
--- PROBLEMS 5 Feb 2003 17:45:14 -0000 1.12
+++ PROBLEMS 25 Feb 2003 15:40:19 -0000
@@ -69,6 +69,10 @@
i[3456]86-*-linux*
------------------
+gdb/660: gdb does not build with linux libc5. The symptom is a parse
+error before `uintptr_t'. Upgrade to glibc 2.1.3 or later, which
+defines uintptr_t.
+
gdb/1030: 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:
next reply other threads:[~2003-02-25 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 15:49 Michael Elizabeth Chastain [this message]
2003-02-25 16:33 ` Andrew Cagney
2003-02-25 17:10 Michael Elizabeth Chastain
2003-02-25 18:10 ` Joel Brobecker
2003-02-25 19:43 ` Andrew Cagney
2003-02-25 18:13 Michael Elizabeth Chastain
2003-02-25 20:08 Michael Elizabeth Chastain
2003-02-25 22:01 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=200302251549.h1PFnQS05835@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