From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Please enable cid-x.map in dvipdfmx.cfg when installing texlive-langjapanese
Date: Tue, 09 May 2017 15:52:00 -0000 [thread overview]
Message-ID: <56a3e238-fed6-dcaf-8699-6a6d0de68e25@cornell.edu> (raw)
In-Reply-To: <20170509202205.60A6.50F79699@gmail.com>
On 5/9/2017 7:22 AM, Lemures Lemniscati wrote:
> My situation has been resolved on x86_64 version by:
> (1) removing /var/lib/texmf
> (2) reinstalling texlive-* packages
>
> It seemed the cause that
> /var/lib/texmf/fonts/map/dvipdfmx/updmap/kanjix.map
> was not updated properly.
>
> On x86 version, I can't resolve it yet, and still keep trying...
Check the logs in /var/log to see if some of the postinstall scripts had
fork failures. Unfortunately, this is fairly common on x86, and a full
rebase (perhaps followed by a reboot) might be necessary. See
https://cygwin.com/ml/cygwin/2017-05/msg00087.html
for example.
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:[~2017-05-09 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 10:26 [ANNOUNCEMENT] TeX Live 2016 collections Ken Brown
2017-05-07 0:17 ` Please enable cid-x.map in dvipdfmx.cfg when installing texlive-langjapanese Lemures Lemniscati
2017-05-07 15:05 ` Ken Brown
2017-05-08 5:42 ` Ken Brown
2017-05-08 14:23 ` Lemures Lemniscati via cygwin
2017-05-08 16:19 ` Ken Brown
2017-05-09 6:17 ` Lemures Lemniscati
2017-05-09 13:21 ` Lemures Lemniscati
2017-05-09 15:52 ` Ken Brown [this message]
2017-05-10 11:30 ` Lemures Lemniscati
2017-05-07 3:47 ` [ANNOUNCEMENT] TeX Live 2016 collections Eliot Moss
2017-05-07 9:56 ` Eliot Moss
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=56a3e238-fed6-dcaf-8699-6a6d0de68e25@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).