From: jfabernathy <jfabernathy@gmail.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: prerequisite tools for making documentation
Date: Tue, 03 Jul 2012 14:57:55 -0400 [thread overview]
Message-ID: <4FF340B3.6090106@gmail.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A1FA2E@ORSMSX101.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1928 bytes --]
On 07/03/2012 02:25 PM, Rifenbark, Scott M wrote:
> Jim,
>
> Do you have a list of what you had to install? I can add this to the QS "Packages" section.
>
> Scott
*Scott,
I had to go thru the apt log for the day I posted this issues. Below are
the packages. I imagine that texlive brought in the last 8 or so.
Jim A
Selecting previously unselected package libxml2-utils.
Selecting previously unselected package docbook-xsl.
Selecting previously unselected package xmlto.
Selecting previously unselected package xmltex.
Selecting previously unselected package texlive.
Selecting previously unselected package texlive-bibtex-extra.
Selecting previously unselected package preview-latex-style.
Selecting previously unselected package texlive-pictures.
Selecting previously unselected package texlive-latex-extra.
Selecting previously unselected package texlive-math-extra.
Selecting previously unselected package dblatex.
Selecting previously unselected package texlive-latex-extra-doc.
Selecting previously unselected package texlive-pictures-doc. *
-----Original Message----- From: yocto-bounces@yoctoproject.org
[mailto:yocto-bounces@yoctoproject.org] On Behalf Of jfabernathy Sent:
Sunday, June 24, 2012 9:06 AM To: yocto@yoctoproject.org Subject:
[yocto] prerequisite tools for making documentation I had a need to look
at the bitbake manual in the poky/bitbake/doc/manual directory and tried
to make pdf. I had all the prerequisites listed in the QS guide.
However, I found the make failed due to a number of xml related tools
being missing. I installed those and got the pdf manual generated.
Should we add those xml tools to the prerequisites? BTW, I'm using
denzil branch and referring to the QS guide 1.2. Jim A
_______________________________________________ yocto mailing list
yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[-- Attachment #2: Type: text/html, Size: 3262 bytes --]
next prev parent reply other threads:[~2012-07-03 18:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 16:06 prerequisite tools for making documentation jfabernathy
2012-06-25 8:45 ` Andrei Gherzan
2012-06-25 9:40 ` Paul Eggleton
2012-07-03 18:25 ` Rifenbark, Scott M
2012-07-03 18:57 ` Chris Hallinan
2012-07-03 18:58 ` jfabernathy
2012-07-03 19:52 ` Rifenbark, Scott M
2012-07-03 19:07 ` Robert P. J. Day
2012-07-03 19:25 ` McClintock Matthew-B29882
2012-07-03 18:57 ` jfabernathy [this message]
2012-07-03 20:02 ` Rifenbark, Scott M
2012-07-13 16:51 ` Rifenbark, Scott M
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=4FF340B3.6090106@gmail.com \
--to=jfabernathy@gmail.com \
--cc=scott.m.rifenbark@intel.com \
--cc=yocto@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.