This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: zp_fontconfig_cache_1.sh exit code 2
- From: Ken Brown <kbrown at cornell dot edu>
- To: cygwin at cygwin dot com
- Date: Sun, 12 Jun 2016 19:15:38 -0400
- Subject: Re: zp_fontconfig_cache_1.sh exit code 2
- Authentication-results: sourceware.org; auth=none
- References: <1465768502 dot 22005 dot ezmlm at cygwin dot com> <trinity-85216d9a-0388-43bb-b021-cc797cda1e3b-1465770728089 at 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