Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Tue, 27 Jul 2004 11:02:50 -0400
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: INT32: jmorecfg.h
Message-ID:	<20040727150250.GC16364@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4105AB1C DOT 8060006 AT nycap DOT rr DOT com> <NUTMEG6PQsqRje8toOH00000aa3 AT NUTMEG DOT CAM DOT ARTIMI DOT COM>
Mime-Version:	1.0
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/

- Raw text -