From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Allow imagemagick to find ghostscript fonts.
Date: Tue, 29 Dec 2015 17:45:04 +0100 [thread overview]
Message-ID: <20151229174504.1ab322da@free-electrons.com> (raw)
In-Reply-To: <1434420746-20199-1-git-send-email-grepper@gmail.com>
Hello Robert,
Sorry for the long delay in replying to your patch.
On Mon, 15 Jun 2015 22:12:26 -0400, grepper wrote:
> It appears that Imagemagick needs to be configured with
> --with-gs-font-dir=/usr/share/fonts/gs else it will not find
> the ghostscript fonts and /etc/ImageMagick-6/type-ghostscript.xml
> will contain the wrong font paths. You end up with messages like:
> Magick: unable to read font `(null)' @ error/annotate.c/RenderFreetype/1153
> They are non-fatal but could get annoying fast if you are using 'convert'
> on a lot of files.
Could you give a specific example use of imagemagick that triggers this
problem, so that we can reproduce the problem on our side and
investigate the possible solutions?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-29 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 2:12 [Buildroot] [PATCH 1/1] Allow imagemagick to find ghostscript fonts grepper
2015-06-16 3:39 ` Baruch Siach
2015-06-16 18:27 ` grepper
2015-06-16 20:01 ` Baruch Siach
2015-12-29 16:45 ` Thomas Petazzoni [this message]
2016-07-04 15:50 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2016-02-09 4:29 Ricardo Martincoski
2016-02-09 17:23 ` Yann E. MORIN
2016-02-09 18:16 ` Ricardo Martincoski
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=20151229174504.1ab322da@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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