From: mudongliangabcd@gmail.com (慕冬亮)
To: kernelnewbies@lists.kernelnewbies.org
Subject: error when make pdfdocs
Date: Fri, 25 Sep 2015 16:53:51 +0800 [thread overview]
Message-ID: <CAD-N9QXDVf=7=Yw627HbEdk4VVNOc_pOfXxmxVKDT5-3JeGSSA@mail.gmail.com> (raw)
In-Reply-To: <CA+r1Zhikd54qGLRunvjsZ9NKiiKuKXz8SAicjv9Ma=XCO0aXcg@mail.gmail.com>
2015-09-25 4:40 GMT+08:00 Jim Davis <jim.epost@gmail.com>:
> On Fri, Sep 18, 2015 at 7:35 AM, ??? <mudongliangabcd@gmail.com> wrote:
>> I git clone and git pull the latest linux kernel.
>> When I make pdfdocs, it reports the following error to me.
>> But I checked the filesystems.xml:14946, no error found.
>>
>> -----------------------------------------------------------------------------------------------
>> PDF Documentation/DocBook/filesystems.pdf
>> Using catalogs: /etc/sgml/catalog
>> Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
>> Working on: /home/mdl/Repos/linux/Documentation/DocBook/filesystems.xml
>> openjade:/home/mdl/Repos/linux/Documentation/DocBook/filesystems.xml:14946:16:E:
>
> The last time I tried (and failed) to get make pdfdocs to work it
> seemed to depend in very sensitive ways on the xml converter being
> used, among other issues, so if it's bombing with openjade you might
> see if there are alternatives you can try. See
> https://www.mail-archive.com/kernelnewbies%40kernelnewbies.org/msg14306.html
> for some of the painful details.
I did checkout linux-stable : linux-4.1.y, linux 4.2.y and master.
However, I always failed to generate pdf docs.
I have given up generating pdf of Document.
I can "make mandocs" to generate man pages.It is the same content with pdf.
- mudongliang
>
> --
> Jim
prev parent reply other threads:[~2015-09-25 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 14:35 error when make pdfdocs 慕冬亮
2015-09-24 20:40 ` Jim Davis
2015-09-25 8:53 ` 慕冬亮 [this message]
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='CAD-N9QXDVf=7=Yw627HbEdk4VVNOc_pOfXxmxVKDT5-3JeGSSA@mail.gmail.com' \
--to=mudongliangabcd@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 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 NNTP newsgroup(s).