Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933598AbXBXXlB (ORCPT ); Sat, 24 Feb 2007 18:41:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933600AbXBXXlB (ORCPT ); Sat, 24 Feb 2007 18:41:01 -0500 Received: from terminus.zytor.com ([192.83.249.54]:47474 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933598AbXBXXlA (ORCPT ); Sat, 24 Feb 2007 18:41:00 -0500 Message-ID: <45E0CCFF.60407@zytor.com> Date: Sat, 24 Feb 2007 15:40:47 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 1.5.0.9 (X11/20061219) MIME-Version: 1.0 To: Jan Engelhardt CC: dsaxena@plexity.net, Linus Torvalds , linux-kernel@vger.kernel.org Subject: Re: [PATCH] Allow kernel to build on Cygwin References: <20070223034343.GA3320@plexity.net> <45DF842F.9000302@zytor.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1168 Lines: 34 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 >>> # include "crc32defs.h" >>> +#ifndef __CYGWIN__ >>> #include >>> +#endif >>> >>> #define ENTRIES_PER_LINE 4 >> Cygwin has just fine; what are you trying to do here? > > What's the benefit of inttypes.h over stdint.h? > is a superset of ; some older platforms don't have (but has all the contents thereof in ) however. In general is what you want. The utility of is relatively limited; it looks like it's intended so that contains the compiler-specific portions rather than the library-specific portions. -hpa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/