DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=O+79IW7xlYLGa/E6GuFkFooM/0z2BuZBWsj2dxVqVp7
	c55bhjL2gbKfj56+nZtw4fRy1slrIypiokERXmL8JhgUghOks5TChguP2+L2yJT7
	/wXqsXqd7eZViVkst3xS7pGsjdbvSraUyifV0o29SC57EjtbI/Sw0ARXAkLBzNlk
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5168147A.10403@cwilson.fastmail.fm>
Date: Fri, 12 Apr 2013 10:04:42 -0400
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: [64bit] type conflict for INT32
References: <5166EB44.6010907@cornell.edu> <51673471.3060401@users.sourceforge.net> <516813C8.8030403@cwilson.fastmail.fm>
In-Reply-To: <516813C8.8030403@cwilson.fastmail.fm>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 4/12/2013 10:01 AM, Charles Wilson wrote:
> On 4/11/2013 6:08 PM, Yaakov (Cygwin/X) wrote:
>> It does mean that Win32API (or X11, for that matter) headers must be
>> #include'd before <jpeglib.h>.  Before I spin a new release, could you
>> test if this works with emacs?
>
> Would this problem go away if we switched to jpeg-turbo?

Sorry, wrong list. Please ignore.

--
Chuck


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple