From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Alberto Luaces <aluaces@udc.es>,
gdb-patches@sources.redhat.com
Subject: Re: Undefined uintptr_t with mingw
Date: Wed, 22 Dec 2010 13:12:00 -0000 [thread overview]
Message-ID: <20101222131045.GK2596@adacore.com> (raw)
Message-ID: <20101222131200.5fg0TpPa-0uVIwWXeENLblmH4Wcg2ryOmoOfwtPyCUk@z> (raw)
In-Reply-To: <201012221228.59906.pedro@codesourcery.com>
> This is fine with me as well, but note that gdb/defs.h is
> including stdint.h unconditionally, because it can rely that gdb/gnulib
> provides one if the host doesn't have such a header, or if
> it finds the system one misses features. If we go this path,
> we should also wrap it in HAVE_STDINT_H.
I thought we were configuring the gnulib directory in gdbserver
as well. That's why I thought that the unconditional include was OK.
--
Joel
next prev parent reply other threads:[~2010-12-22 13:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 16:35 Alberto Luaces
2010-12-22 4:00 ` Joel Brobecker
2010-12-22 12:29 ` Pedro Alves
2010-12-22 13:11 ` Pedro Alves
2010-12-22 14:32 ` Joel Brobecker [this message]
2010-12-22 13:12 ` Joel Brobecker
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=20101222131045.GK2596@adacore.com \
--to=brobecker@adacore.com \
--cc=aluaces@udc.es \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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