From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: dsaxena@plexity.net, Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Allow kernel to build on Cygwin
Date: Sat, 24 Feb 2007 15:40:47 -0800 [thread overview]
Message-ID: <45E0CCFF.60407@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0702242354550.16527@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
> On Feb 23 2007 16:17, H. Peter Anvin wrote:
>> Deepak Saxena wrote:
>>> diff --git a/lib/gen_crc32table.c b/lib/gen_crc32table.c
>>> index bea5d97..ce447ff 100644
>>> --- a/lib/gen_crc32table.c
>>> +++ b/lib/gen_crc32table.c
>>> @@ -1,6 +1,8 @@
>>> # include <stdio.h>
>>> # include "crc32defs.h"
>>> +#ifndef __CYGWIN__
>>> #include <inttypes.h>
>>> +#endif
>>>
>>> #define ENTRIES_PER_LINE 4
>> Cygwin has <inttypes.h> just fine; what are you trying to do here?
>
> What's the benefit of inttypes.h over stdint.h?
>
<inttypes.h> is a superset of <stdint.h>; some older platforms don't
have <stdint.h> (but has all the contents thereof in <inttypes.h>) however.
In general <inttypes.h> is what you want. The utility of <stdint.h> is
relatively limited; it looks like it's intended so that <stdint.h>
contains the compiler-specific portions rather than the library-specific
portions.
-hpa
next prev parent reply other threads:[~2007-02-24 23:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 3:43 [PATCH] Allow kernel to build on Cygwin Deepak Saxena
2007-02-23 20:37 ` Matthieu CASTET
2007-02-23 23:17 ` Deepak Saxena
2007-02-24 0:17 ` H. Peter Anvin
2007-02-24 22:55 ` Jan Engelhardt
2007-02-24 23:40 ` H. Peter Anvin [this message]
2007-02-24 0:18 ` H. Peter Anvin
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=45E0CCFF.60407@zytor.com \
--to=hpa@zytor.com \
--cc=dsaxena@plexity.net \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.