public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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:35:00 -0000	[thread overview]
Message-ID: <8e20b063-fdc2-1fa7-35a7-db13583b2d9f@cornell.edu> (raw)
In-Reply-To: <trinity-85216d9a-0388-43bb-b021-cc797cda1e3b-1465770728089@3capp-gmx-bs72>

On 6/12/2016 6:32 PM, Mark McGregor wrote:
> ----Ken wrote:
>
> 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
> ----
> Thank you. After running
> $ /etc/postinstall/zp_fontconfig_cache_1.sh
> I obtained the output in the attachment, which looks good. Are you saying that the message is bogus and no action is needed?

Yes.

> While compiling some (seemingly good) LaTeX file I'm getting
> [
> ...
> xdvipdfmx:fatal: This font using the "seac" command for accented characters...
>
> Output file removed.
>  )
> Error 256 (driver return code) generating output;
> file file.pdf may not be valid.
> ]
> I have no idea about whether it is related.

I suspect it's unrelated.  Please make a separate bug report about that, 
and I'll see if I can help.  Try to cut your LaTeX file down to a 
minimal file that exhibits the problem.

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

  reply	other threads:[~2016-06-12 23:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1465768502.22005.ezmlm@cygwin.com>
2016-06-12 23:26 ` Mark McGregor
2016-06-12 23:35   ` Ken Brown [this message]
2016-06-12 23:36 Mark McGregor
2016-06-12 23:42 ` Ken Brown
2016-07-01  8:24   ` Václav Haisman
  -- strict thread matches above, loose matches on Subject: below --
2016-06-12 22:32 Mark McGregor
2016-06-12 23:15 ` 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=8e20b063-fdc2-1fa7-35a7-db13583b2d9f@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).