From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: zp_fontconfig_cache_1.sh exit code 2
Date: Sun, 12 Jun 2016 23:15:00 -0000 [thread overview]
Message-ID: <07375b01-b392-2b11-1c0d-22f5ad4b702a@cornell.edu> (raw)
In-Reply-To: <trinity-f44febaf-a656-4566-b42a-bcccd2e6123a-1465767160468@3capp-gmx-bs72>
On 6/12/2016 5:32 PM, Mark McGregor wrote:
> ... and after one more installation, I get exit code 1. Don't ask me why.
The exit code is the number of font caches that fontconfig thinks it
failed to write.
In fact, I'm pretty sure it actually did successfully write the cache,
and the error message is bogus. You can test this by adding the -v flag
to the fc-cache invocation in zp_fontconfig_cache_1.sh:
/usr/libexec/fc-cache-1 -sv
I think you'll find that if you rerun zp_fontconfig_cache_1.sh after it
has reported "failed to write cache" on a certain font directory, it
will then give a message saying the cache is up to date and doesn't need
to be rewritten.
That's what I've found, anyway.
Ken
--
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
next prev parent reply other threads:[~2016-06-12 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 22:32 Mark McGregor
2016-06-12 23:15 ` Ken Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-12 23:36 Mark McGregor
2016-06-12 23:42 ` Ken Brown
2016-07-01 8:24 ` Václav Haisman
[not found] <1465768502.22005.ezmlm@cygwin.com>
2016-06-12 23:26 ` Mark McGregor
2016-06-12 23:35 ` Ken Brown
2016-06-12 21:32 Mark McGregor
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=07375b01-b392-2b11-1c0d-22f5ad4b702a@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/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).