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: Mon, 10 Jan 2005 17:14:21 +0000
From: Roger Leigh <roger DOT leigh AT epictechnology DOT co DOT uk>
To: cygwin AT cygwin DOT com
Subject: Building new GLib and Pango
Message-ID: <20050110171420.GA5443@epictechnology.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-GPG-Key: 0x25BFB848
X-Debian: testing/unstable
X-OS-Uptime: 17:06:31 up 3 min,  2 users,  load average: 0.56, 0.53, 0.24
User-Agent: Mutt/1.5.6+20040907i

Could anyone involved with Cygwin glib maintenance possibly assist with
tracking down a Cygwin header bug?

While building Pango, one of the tests fails with lots of errors in
<winspool.h>.  The detail may be found here, along with a link to
a build of glib-2.6.1 (required dependency).

http://bugzilla.gnome.org/show_bug.cgi?id=163584

If you want to build glib-2.6.1 yourself, these patches are required

http://bugzilla.gnome.org/show_bug.cgi?id=163136
http://bugzilla.gnome.org/show_bug.cgi?id=163133


The bug is probably due to a #define causing a screwup in the w32api
headers, but I am uncertain whether this is a Cygwin or a Pango bug.
Since the failures occur in places that look fine, the cause is
non-obvious to me.


Many Thanks,
Roger

-- 
Roger Leigh

                Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
                GPG Public Key: 0x25BFB848.  Please sign and encrypt your mail.

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