Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Tue, 27 Jul 2004 11:02:50 -0400
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: INT32: jmorecfg.h
Message-ID: <20040727150250.GC16364@trixie.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <4105AB1C.8060006@nycap.rr.com> <NUTMEG6PQsqRje8toOH00000aa3@NUTMEG.CAM.ARTIMI.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NUTMEG6PQsqRje8toOH00000aa3@NUTMEG.CAM.ARTIMI.COM>
User-Agent: Mutt/1.4.1i

On Tue, Jul 27, 2004 at 10:01:08AM +0100, Dave Korn wrote:
>I remember hitting this problem with a cygwin build of libjpeg once.
>The correct answer is probably that jmorecfg.h shouldn't arbitrarily
>define INT32 globally without first performing an autoconf test to see
>if there's something in the system includes that already provides it,
>isn't it?

Yes.  Just adding more and more ifdef guards around the INT32 definition
is not the way to go.

cgf

--
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/

