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
From: "Dave Korn" <dk AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: INT32: jmorecfg.h
Date: Tue, 27 Jul 2004 10:01:08 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <4105AB1C.8060006@nycap.rr.com>
Message-ID: <NUTMEG6PQsqRje8toOH00000aa3@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 27 Jul 2004 09:01:08.0218 (UTC) FILETIME=[416EE5A0:01C473B8]

> -----Original Message-----
> From: cygwin-owner On Behalf Of Mathieu Malaterre
> Sent: 27 July 2004 02:09

> Christopher Faylor wrote:
> > On Mon, Jul 26, 2004 at 08:44:11PM -0400, Mathieu Malaterre wrote:
> > 
> >>Hi,
> >>
> >>	I am trying to compile VTK using the jpeg library shipped with 
> >>	cygwin. And I have a problem of compilation:
> >>	
> >>Building object file vtkJPEGReader.o...
> >>In file included from /usr/include/jpeglib.h:30,
> >>                from 
> /home/mathieu/Kitware/VTK/Utilities/vtk_jpeg.h:21,
> >>                from 
> /home/mathieu/Kitware/VTK/IO/vtkJPEGReader.cxx:23:
> >>/usr/include/jmorecfg.h:250: error: conflicting types for 
> `typedef long int
> >>  INT32'
> >>/usr/include/w32api/basetsd.h:52: error: previous declaration as 
> >>`typedef int
> >>  INT32'
> >>
> >>
> >>	could someone patch the jpeg6b lib (look at line 249) :
> > 
> > 
> > You're mixing cygwin includes with native windows includes. 
>  That's not designed
> > to work well.
> 
> VTK compiles / runs on:
> 
> - Nearly every Unix-based plateform (SGI, HP-UX, SUN ...)
> - Windows 95/98/NT/2000/XP
> - Tons of linux flavor
> - Mac OS X
> - *BSD
> 
> So I believe we have a rather clean approach. It's just the fact that 
> defining INT32 globally without no namespace is rather 
> dangerous, don't 
> you think ? All I was asking, was just for a little barrier (since a 
> barrier from XMD_H was already done).
 

  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?


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


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