From: jfabernathy <jfabernathy@gmail.com>
To: Chris Hallinan <challinan@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: prerequisite tools for making documentation
Date: Tue, 03 Jul 2012 14:58:42 -0400 [thread overview]
Message-ID: <4FF340E2.5030500@gmail.com> (raw)
In-Reply-To: <CAME0jBRJS_zxENDxB8_-rhgwCR49B_wM-x=g-kZw=ggpWNbUcA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]
On 07/03/2012 02:57 PM, Chris Hallinan wrote:
> On Tue, Jul 3, 2012 at 2:25 PM, Rifenbark, Scott M
> <scott.m.rifenbark@intel.com <mailto:scott.m.rifenbark@intel.com>> wrote:
>
> Jim,
>
> Do you have a list of what you had to install? I can add this to
> the QS "Packages" section.
>
> Scott
>
> -----Original Message-----
> From: yocto-bounces@yoctoproject.org
> <mailto:yocto-bounces@yoctoproject.org>
> [mailto: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 <mailto: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.
>
>
> I'd also be interested in knowing what host you built it on, as
> several of us (including myself) have had difficulty building docs.
>
I'm running Ubuntu 12.04 LTS.
Jim A
> Thanks,
>
> Chris
> --
> Life is like Linux - it never stands still.
>
>
[-- Attachment #2: Type: text/html, Size: 3009 bytes --]
next prev parent reply other threads:[~2012-07-03 18:58 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 [this message]
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
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=4FF340E2.5030500@gmail.com \
--to=jfabernathy@gmail.com \
--cc=challinan@gmail.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.