Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <000501c32fae$96a497d0$78d96f83@pomello> From: "Max Bowsher" To: "Alexander Enchevich" , References: <66F336FF8FD0484B943E0CF48D923C2C053680CB AT CSCEX04> Subject: Re: AC_CYGWIN? Date: Wed, 11 Jun 2003 01:15:39 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Cam-ScannerAdmin: mail-scanner-support AT ucs DOT cam DOT ac DOT uk X-Cam-AntiVirus: Not scanned X-Cam-SpamDetails: Alexander Enchevich wrote: > Hi > > What's the proper way to check if I am compiling on a cygwin system from > within an autoconf configure.in script? From the subject, you clearly already have an idea. If you check the autoconf docs, they will tell you that that macro is obsolete, and tell you how you should be doing it. Of course, checking for a platform kind of goes against the whole feature-not-platform tests ideal of autoconf. Max. -- 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/