All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH 0/9] Prepare Sphinx to build media PDF books
Date: Wed, 24 Aug 2016 07:42:13 -0300	[thread overview]
Message-ID: <20160824074213.56fe8e50@vento.lan> (raw)
In-Reply-To: <20160818172127.190fad79@lwn.net>

Markus,

Em Thu, 18 Aug 2016 17:21:27 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:

> On Tue, 16 Aug 2016 13:25:34 -0300
> Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote:
> 
> > I think this patch series belong to docs-next. Feel free to merge them there, if
> > you agree. There's one extra patch that touches Documentation/conf.py,
> > re-adding the media book to the PDF build, but IMHO this one would be better
> > to be merged via the media tree, after the fixes inside the media documentation
> > to fix the build.  
> 
> It's now in docs-next.  I was able to build some nice-looking docs with it
> without too much (additional) pain...

I'm noticing a very weird behavior when I'm building documentation on
my server. There, I'm using this command:

	$ make cleandocs; make V=1 DOCBOOKS="" SPHINXDIRS=media SPHINX_CONF="conf.py" htmldocs

This is what happens on my local machine:
	http://pastebin.com/VGqvDa7T

And this is the result of the same command on my server, accessed via ssh:
	http://pastebin.com/1MFi5LEG

As you can see, it seems that internally sphinx is calling a
make -C Documentation/output/latex, with is very bad, because it takes
a lot of extra time to run and produces an useless output. It also produces 
a wrong output, as it would be calling pdflatex, instead of xelatex.

Do you have any glue about what's going on?

Also, if I use the "-j33" sphinx option, it complains:

WARNING: the kernel_include extension does not declare if it is safe for parallel reading, assuming it isn't - please ask the extension author to check and make it explicit
WARNING: doing serial read

Btw, we need to add support to build just one PDF file, as we did with
the htmldocs.

Thanks,
Mauro

  parent reply	other threads:[~2016-08-24 10:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 16:25 [PATCH 0/9] Prepare Sphinx to build media PDF books Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 1/9] docs-rst: fix a breakage when building PDF documents Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 2/9] docs-rst: remove a rst2pdf left over code Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 3/9] docs-rst: allow generating some LaTeX pages in landscape Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 4/9] docs-rst: improve output for .. notes:: on LaTeX Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 5/9] docs-rst: Don't mangle with UTF-8 chars on LaTeX/PDF output Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 6/9] docs-rst: better adjust margins and font size Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 7/9] docs-rst: parse-heraders.pl: escape LaTeX characters Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 8/9] docs-rst: Don't go to interactive mode on errors Mauro Carvalho Chehab
2016-08-16 16:25 ` [PATCH 9/9] docs-rst: enable the Sphinx math extension Mauro Carvalho Chehab
2016-08-18 23:21 ` [PATCH 0/9] Prepare Sphinx to build media PDF books Jonathan Corbet
2016-08-19 13:24   ` Mauro Carvalho Chehab
2016-08-24 10:42   ` Mauro Carvalho Chehab [this message]
2016-08-24 11:46     ` Markus Heiser
2016-08-24 12:23       ` Mauro Carvalho Chehab

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=20160824074213.56fe8e50@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=corbet@lwn.net \
    --cc=linux-media@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=mchehab@infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.