From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
SeongJae Park <sj38.park@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH 0/5] Add a script to check for Sphinx install requirements
Date: Mon, 17 Jul 2017 06:33:03 -0300 [thread overview]
Message-ID: <20170717063303.6c5dfd58@vento.lan> (raw)
In-Reply-To: <576692E6-3663-4E69-A92B-7F7DA326B081@darmarit.de>
Em Mon, 17 Jul 2017 10:15:26 +0200
Markus Heiser <markus.heiser@darmarit.de> escreveu:
> > Am 17.07.2017 um 00:08 schrieb Mauro Carvalho Chehab <mchehab@s-opensource.com>:
> >
> > [1] There's an unrelated bug with the Kernel's sphinx extension
> > kimage: when parsing GraphViz graphs, it uses "-Tpdf" argument,
> > in order to generate a PDF image. That doesn't work on some
> > distros, as GraphViz doesn't support PDF images.
> >
>
> Hmm .. http://www.graphviz.org/content/output-formats#dpdf
>
> Is it a problem of the GraphViz version?
>
> See http://www.graphviz.org/News.php ..
>
> """New Release 2.32 (1 August 2013)
>
> ... In addition, if the poppler library is available, Graphviz
> can now use PDF files as images."""
>
> I suppose that 2.32 is in your distro .. it's from 2013
Fedora 26 is shipped with version 2.40:
$ rpm -q graphviz
graphviz-2.40.1-4.fc26.x86_64
Yet:
$ dot -Thelp|grep pdf
Format: "help" not recognized. Use one of: canon cmap cmapx cmapx_np dot dot_json eps fig gv imap imap_np ismap json json0 mp pic plain plain-ext pov ps ps2 svg svgz tk vdx vml vmlz xdot xdot1.2 xdot1.4 xdot_json
I actually noticed this issue first on OpenSuse, where GraphViz is
packaged on several packages, but I was unable to find one package
there with pdf suport. I'm pretty sure pdf used to work on F25.
>
> It seems, that the graphiz homepage is not up to date. I found
> the repo at github. There is a issue about PDF
>
> https://github.com/ellson/graphviz/issues/1180
>
> So I guess graphviz is compiled without HAVE_PANGOCAIRO in your
> distros?
>From Fedora source package, it is requiring both cairo and pango:
BuildRequires: cairo-devel >= 1.1.10, pango-devel, gmp-devel, lua-devel, gtk2-devel, libgnomeui-devel
Building it gets:
checking for PANGOCAIRO... yes
Still, no PDF support. I'll try to investigate it further, as I
found myself useful to produce PDF directly from GraphViz.
Anyway, I guess we should modify kfigure.py to check if PDF is
available, falling back to SVG, using ImageMagick to convert
from SVG to PDF.
Thanks,
Mauro
next prev parent reply other threads:[~2017-07-17 9:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 22:08 [PATCH 0/5] Add a script to check for Sphinx install requirements Mauro Carvalho Chehab
2017-07-16 22:08 ` [PATCH 1/5] scripts/sphinx-pre-install: add a script to check Sphinx install Mauro Carvalho Chehab
2017-07-16 22:08 ` [PATCH 2/5] sphinx-pre-install: detect an existing virtualenv Mauro Carvalho Chehab
2017-07-16 22:08 ` [PATCH 3/5] sphinx-pre-install: use a requirements file Mauro Carvalho Chehab
2017-07-17 6:00 ` Markus Heiser
2017-07-17 9:36 ` Mauro Carvalho Chehab
2017-07-16 22:08 ` [PATCH 4/5] sphinx.rst: document scripts/sphinx-pre-install script Mauro Carvalho Chehab
2017-07-16 22:08 ` [PATCH 5/5] doc: Makefile: if sphinx is not found, run a check script Mauro Carvalho Chehab
2017-07-17 8:15 ` [PATCH 0/5] Add a script to check for Sphinx install requirements Markus Heiser
2017-07-17 9:33 ` Mauro Carvalho Chehab [this message]
2017-07-17 10:09 ` Mauro Carvalho Chehab
2017-07-17 10:32 ` Markus Heiser
2017-07-17 10:57 ` Mauro Carvalho Chehab
2017-07-18 8:53 ` Markus Heiser
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=20170717063303.6c5dfd58@vento.lan \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@infradead.org \
--cc=sj38.park@gmail.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