X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-Trace: 97218024/mk-filter-4.mail.uk.tiscali.com/B2C/$b2c-THROTTLED-DYNAMIC/b2c-CUSTOMER-DYNAMIC-IP/79.66.2.206/None/johne53 AT tiscali DOT co DOT uk X-SBRS: None X-RemoteIP: 79.66.2.206 X-IP-MAIL-FROM: johne53 AT tiscali DOT co DOT uk X-MUA: Microsoft Outlook Express 6.00.2900.2180Produced By Microsoft MimeOLE V6.00.2900.2180 X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqwEACObCklPQgLO/2dsb2JhbACEG1XJBYNR X-IronPort-AV: E=Sophos;i="4.33,522,1220223600"; d="scan'208";a="97218024" Message-ID: <007401c93b56$ebcfa510$4001a8c0@mycomputer> From: "John Emmas" To: References: <000201c93ac7$38265930$4001a8c0 AT mycomputer> <490A30C8 DOT 5000107 AT sh DOT cvut DOT cz> <001601c93b31$a961b940$4001a8c0 AT mycomputer> <003e01c93b42$e92a17a0$4001a8c0 AT mycomputer> <490AE8A0 DOT 8090009 AT sh DOT cvut DOT cz> <001a01c93b4d$617de150$4001a8c0 AT mycomputer> <490AF1E3 DOT 3020308 AT sh DOT cvut DOT cz> Subject: Re: cygwin g++ strictness Date: Fri, 31 Oct 2008 12:48:06 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 8bit X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 ----- Original Message ----- From: "Václav Haisman" Sent: 31 October 2008 11:54 Subject: Re: cygwin g++ strictness > > Try getting preprocessed source to see where int32_t get defined to > anything else than typedef of int. > I quite like this idea because I can see that this situation is going to cause me lots of problems - in fact, it's ALREADY causing me lots of problems... :-) Can you expand on that suggestion please? Where is the preprocessed source available? If you mean searching through Cygwin's normal header files it would be very difficult to track this down (although I agree with you - int32_t must be getting defined differently, somewhere). John -- 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/