X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <001901c929f3$030ee7b0$4001a8c0 AT mycomputer> Subject: RE: __CYGWIN_USE_BIG_TYPES__ Date: Thu, 9 Oct 2008 11:37:56 +0100 Message-ID: <042101c929fb$1a61d8c0$9601a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <001901c929f3$030ee7b0$4001a8c0@mycomputer> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com John Emmas wrote on 09 October 2008 10:40: > which appears in /usr/include/cygwin/types.h ^^^^^^^^^^^^^^^^^^^ Do not directly include files from this subdir, if that's what you've been doing. It is private. > In other words, should I #define it to 0 for a 32-bit platform? Nope. Don't define it any way at all, it's private. > If not, > what do I need to #include in order to get a valid type for _off64_t ? #include should give you a valid "off_t". Whether it does that using an internal private definition of "_off64_t" or not should not need to bother your code - the leading "_" indicates implementation-private namespace in the C standard. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/