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
Message-ID: <41073BD1.3060707@cwilson.fastmail.fm>
Date: Wed, 28 Jul 2004 01:38:25 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 MultiZilla/1.6.4.0b
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: INT32: jmorecfg.h
References: <4105AB1C DOT 8060006 AT nycap DOT rr DOT com> <NUTMEG6PQsqRje8toOH00000aa3 AT NUTMEG DOT CAM DOT ARTIMI DOT COM> <20040727150250 DOT GC16364 AT trixie DOT casa DOT cgf DOT cx>
In-Reply-To: <20040727150250.GC16364@trixie.casa.cgf.cx>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Christopher Faylor wrote:

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

Unfortunately, the ijg group does not distribute the autoconf source for 
libjpeg's configure script.  It's on my todo list to really truly 
autoconfiscate libjpeg (and libtiff) -- which will make things like this 
easier.  But it's not a very high priority.

Nor am I all that worked up about this INT32 issue.  jmorecfg.h is 
present in all builds of libjpeg; I don't understand why INT32 is 
causing a problem *only* on cygwin.  It seems that you should be seeing 
the problem on all platforms, or none.  Since your package is showing 
this behavior only on cygwin, I suspect something wacky in (a) your 
cygwin environment, or (b) the procedure/configury you're using to build 
on cygwin (e.g. mixing native and cygwin headers).

Given that, I'm not going to rush out and fix this right away, because I 
only have bad choices: (1) add yet another #ifdef hack, or (2) spend a 
week teasing out and reverse-engineering the autoconfigury source files...

--
Chuck


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