Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] configure: new variable HAVE_UINTPTR_T
Date: Wed, 26 Feb 2003 14:59:00 -0000	[thread overview]
Message-ID: <20030226145935.GA10129@nevyn.them.org> (raw)
In-Reply-To: <200302261445.h1QEjkq25333@duracef.shout.net>

On Wed, Feb 26, 2003 at 08:45:46AM -0600, Michael Elizabeth Chastain wrote:
> Draft #3.  Following Daniel J's advice, I use AC_CACHE_CHECK and the
> multi-argument form of AC_DEFINE.  I re-tested with and without
> uintptr_t in /usr/include/stdint.h to hit both paths.
> 
> I also learned that config.in is a regenerated file, not a hand-edited
> file.  And by using multi-argument AC_DEFINE I dropped the change to
> 
> I don't show diffs for regenerated 'configure' and 'config.in'.  I
> regenerated with stock autoconf 2.13 and autoheader 2.13 from
> ftp.gnu.org.
> 
> Again, this is so that the gdb build can do something better when
> it needs uintptr_t and doesn't have it (pr gdb/660).  My notion of
> 'something better' is going to be to spit out a better error message,
> not to actually work.  Somebody has to have a really old libc
> (more than 3 years old) to get this message, but with millions of
> users, some people do.
> 
> OK to commit?

Yes, thank you.

> 2003-02-26  Michael Chastain  <mec@shout.net>
> 
> 	* configure.in: New variable HAVE_UINTPTR_T.
> 	* configure, config.in: Regenerated.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-26 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26 14:45 Michael Elizabeth Chastain
2003-02-26 14:59 ` Daniel Jacobowitz [this message]
2003-02-26 15:12 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=20030226145935.GA10129@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@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