public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Gilles Detillieux <grdetil@scrc.umanitoba.ca>
Subject: Re: libharfbuzz0 1.7.6-1 update causing xwin-xdg-menu.exe to crash
Date: Mon, 14 May 2018 21:44:00 -0000	[thread overview]
Message-ID: <f7712b5a-688e-66c9-fa6d-a7a68822361c@dronecode.org.uk> (raw)
In-Reply-To: <5ebcd9b9-c745-d468-5ecf-aae259bedf2a@scrc.umanitoba.ca>

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

  reply	other threads:[~2018-05-14 21:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 21:15 Gilles Detillieux
2018-04-24 21:30 ` Gilles Detillieux
2018-04-26 14:03 ` Jon Turney
2018-04-26 15:40   ` Gilles Detillieux
2018-05-12 14:27     ` Jon Turney
2018-05-14 19:29       ` Gilles Detillieux
2018-05-14 21:44         ` Jon Turney [this message]
2018-05-15 15:01           ` Gilles Detillieux
2018-05-14 21:38   ` Brian Inglis
2018-05-14 21:47     ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f7712b5a-688e-66c9-fa6d-a7a68822361c@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=grdetil@scrc.umanitoba.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).