X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:cc:reply-to:from
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=RQoXjX7tXnyoX3KM
	7bS5k6uaP3d1sn2oFFRuigqRRWwNZD3DdT33GjMC54yQzKeDL5agZTTnmp6ER4Oy
	IXwGGBSNuKyoSoFIT0Wy7MFG8wyhpeeCln0I37iFqyXs8/+c4KBWNhw56O94krks
	Zyporg1XLtztVfVE8tMxZwMH0A4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:cc:reply-to:from
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=3IBbQwr8JzcgsfZTVBw7fN
	7GQ0U=; b=PescrDbT4KZqlIF2mYMhMl22wG+UP8xva3mOgzLCAheixPChmGJxZ9
	sGoEGB1EY6T5cr7mi2rMJQwa30ttYs4VdgweR+HQDEhtXeEMhxLzsrc9atI07XIV
	HPvkgi6A3IG6xKHkcCO6A0lkU0i8+44wnwMuRpDDCe/HRfJn7ggcM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:651, rebuilt, our, Hx-spam-relays-external:ESMTPA
X-HELO: out2-smtp.messagingengine.com
X-ME-Sender: <xms:DwP6Wv6JXlR645nVfHrj6QSNwAC-Pt5iuYKpBU9NvJdAxwuU8U-Phw>
Subject: Re: libharfbuzz0 1.7.6-1 update causing xwin-xdg-menu.exe to crash
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
References: <30aa068b-574f-8770-d8f3-eb037c038709 AT scrc DOT umanitoba DOT ca> <63a969f7-00eb-2067-7dbe-f141bfecbaae AT dronecode DOT org DOT uk> <45934aef-f59b-7ca6-5cf9-8e60ad559cae AT scrc DOT umanitoba DOT ca> <b907254e-fe2d-155d-aa3f-6cda50cd4be1 AT dronecode DOT org DOT uk> <5ebcd9b9-c745-d468-5ecf-aae259bedf2a AT scrc DOT umanitoba DOT ca>
Cc: Gilles Detillieux <grdetil AT scrc DOT umanitoba DOT ca>
Reply-To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
From: Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Message-ID: <f7712b5a-688e-66c9-fa6d-a7a68822361c@dronecode.org.uk>
Date: Mon, 14 May 2018 22:43:40 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <5ebcd9b9-c745-d468-5ecf-aae259bedf2a@scrc.umanitoba.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 14/05/2018 18:05, Gilles Detillieux wrote:
> Thanks, Jon. The local.conf blacklist rule worked like a charm!
> 
> It's odd that the fontconfig packages appear not to have been built with 
> the latest stable gcc release, but so long as it's just this one 

I don't know if that's the case or not.  More things than just the 
compiler can effect the resulting binary.

> (unneeded) font that's causing the headaches I'll just keep blacklisting 
> it on our systems.

Yaakov has rebuilt and uploaded the fontconfig 2.12.6-2, which doesn't 
seem to suffer from this problem in my testing.

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