From: Kai Tietz <ktietz70@googlemail.com>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: Ian Lance Taylor <iant@google.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Binutils <binutils@sourceware.org>, gdb <gdb@sourceware.org>
Subject: Re: [patch libiberty's include]: Fixes PR 39064 and partial PR 54620
Date: Wed, 30 Jan 2013 15:03:00 -0000 [thread overview]
Message-ID: <CAEwic4a2oPmfOasSmc1pOdWo337CO9upDcBWBnGs59Wa_ET7rQ@mail.gmail.com> (raw)
In-Reply-To: <ydd38xi67ot.fsf@lokon.CeBiTec.Uni-Bielefeld.DE>
Hmm, I see ... so we need an new condition.
Is it ok to apply?
Thanks,
Kai
Index: md5.h
===================================================================
--- md5.h (Revision 195572)
+++ md5.h (Arbeitskopie)
@@ -40,6 +40,11 @@
# include <sys/types.h>
typedef u_int32_t md5_uint32;
typedef uintptr_t md5_uintptr;
+#elif defined (HAVE_SYS_TYPES_H) && defined (HAVE_STDINT_H)
+#include <stdint.h>
+#include <sys/types.h>
+typedef uint32_t md5_uint32;
+typedef uintptr_t md5_uintptr;
#else
# define INT_MAX_32_BITS 2147483647
Index: sha1.h
===================================================================
--- sha1.h (Revision 195572)
+++ sha1.h (Arbeitskopie)
@@ -39,6 +39,11 @@
# include <sys/types.h>
typedef u_int32_t sha1_uint32;
typedef uintptr_t sha1_uintptr;
+#elif defined (HAVE_SYS_TYPES_H) && defined (HAVE_STDINT_H)
+#include <stdint.h>
+#include <sys/types.h>
+typedef uint32_t sha1_uint32;
+typedef uintptr_t sha1_uintptr;
#else
# define INT_MAX_32_BITS 2147483647
next prev parent reply other threads:[~2013-01-30 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 10:53 Kai Tietz
2013-01-30 14:31 ` Ian Lance Taylor
2013-01-30 14:48 ` Kai Tietz
2013-01-30 14:56 ` Rainer Orth
2013-01-30 15:03 ` Kai Tietz [this message]
2013-01-30 15:44 ` Ian Lance Taylor
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=CAEwic4a2oPmfOasSmc1pOdWo337CO9upDcBWBnGs59Wa_ET7rQ@mail.gmail.com \
--to=ktietz70@googlemail.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=iant@google.com \
--cc=ro@cebitec.uni-bielefeld.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).