Re: zp_fontconfig_cache_1.sh exit code 2

["Mark McGregor" <mark dot mcgregor at gmx dot de>]

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

Attachment: output_of_zp_fontconfig_cache_1.txt
Description: Text document

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