Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com, mec@shout.net
Subject: Re: [rfa] PROBLEMS (i[3456]86-*-linux*): Require glibc 2.1.3 or later
Date: Tue, 25 Feb 2003 22:01:00 -0000	[thread overview]
Message-ID: <200302252201.h1PM1ml11952@duracef.shout.net> (raw)

Committed, after private approval from Andrew C.

I am working on a followup patch to teach 'configure' about uintptr_t,
and then I can make gdb_threads.h emit a more informative error
message.

One PR part-way down.  640 more after that.

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.


             reply	other threads:[~2003-02-25 22:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25 22:01 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-25 20:08 Michael Elizabeth Chastain
2003-02-25 18:13 Michael Elizabeth Chastain
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 15:49 Michael Elizabeth Chastain
2003-02-25 16:33 ` Andrew Cagney

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=200302252201.h1PM1ml11952@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