All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rob Prowel" <rprowel@comcast.net>
To: yocto@lists.yoctoproject.org
Subject: cannot build PDF docs
Date: Fri, 31 Jul 2020 11:19:31 -0400	[thread overview]
Message-ID: <de5d2fa6-d353-9113-72cf-f75d2544707c@comcast.net> (raw)

Is there some magic to building the PDF versions of the yocto docs? 
I've tried on multiple machines running debian and differing versions of 
ubuntu and consistently the PDF docs fail to build.

Font substitution errors are trivial, but not being able to locate the 
images that get are inserted is a pretty serious build bug.

What's the secret to building PDF docs, or where are they online?  and 
no, not interested in referring to cloud based HTML docs.  I want 
offline PDF documentation.

Thanks!

$ make DOC=adt-manual pdf
cd adt-manual; ../tools/poky-docbook-to-pdf adt-manual.xml ../template; 
cd ..
Note: namesp. cut : stripped namespace before processing
             Yocto Project Application Developer's Guide

Making portrait pages on A4 paper (210mmx297mm)
Attributed 561 IDs for element, cleaned up 0
[warning] /usr/bin/fop: JVM flavor 'sun' not understood
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on 
-Dswing.aatext=true
[INFO] FopConfParser - Default page-height set to: 11in
[INFO] FopConfParser - Default page-width set to: 8.26in
[ERROR] FOUserAgent - Image not found. URI: figures/adt-title.png. (See 
position 2:38206)
[WARN] FOUserAgent - Font "Symbol,normal,700" not found. Substituting 
with "Symbol,normal,400".
[WARN] FOUserAgent - Font "ZapfDingbats,normal,700" not found. 
Substituting with "ZapfDingbats,normal,400".
[ERROR] FOUserAgent - Image not found. URI: figures/adt-title.png. (No 
context info available)
[INFO] FOUserAgent - Rendered page #1.
[INFO] FOUserAgent - Rendered page #2.
[INFO] FOUserAgent - Rendered page #3.
[INFO] FOUserAgent - Rendered page #4.
[INFO] FOUserAgent - Rendered page #5.
[ERROR] FOUserAgent - Image not found. URI: 
figures/using-a-pre-built-image.png. (See position 736:275)
[WARN] FOUserAgent - Font "veramono,italic,400" not found. Substituting 
with "veramono,normal,400".
[WARN] FOUserAgent - The contents of fo:block line 1 exceed the 
available area in the inline-progression direction by more than 50 
points. (See position 496:372)
[WARN] FOUserAgent - The contents of fo:block line 1 exceed the 
available area in the inline-progression direction by more than 50 
points. (See position 496:372)
[WARN] FOUserAgent - The contents of fo:block line 1 exceed the 
available area in the inline-progression direction by more than 50 
points. (See position 496:372)
[WARN] FOUserAgent - The contents of fo:block line 1 exceed

             reply	other threads:[~2020-07-31 15:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31 15:19 Rob Prowel [this message]
2020-07-31 16:15 ` [yocto] cannot build PDF docs Armin Kuster

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=de5d2fa6-d353-9113-72cf-f75d2544707c@comcast.net \
    --to=rprowel@comcast.net \
    --cc=yocto@lists.yoctoproject.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.