From: Paul Larson <plars@linuxtestproject.org>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: 2.0-testing.bk
Date: Tue, 25 Jan 2005 11:39:40 -0600 [thread overview]
Message-ID: <1106674780.5366.9.camel@localhost.localdomain> (raw)
In-Reply-To: <E1CtSqL-000136-00@mta1.cl.cam.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
Am I mistaken, or didn't this used to build, even if you don't have
latex and such things that are needed to build the documentation? It's
not a big deal to install it, but was this change intentional, or is it
preferred that things like this not cause a build failure?
*************************************************
*************************************************
* WARNING: Package 'latex' is required
* to build Xen documentation
*************************************************
*************************************************
make[1]: *** [docs] Error 1
make[1]: Leaving directory
`/home/plars/cvs/xen/xentest/xen-2.0-testing.bk'
make: *** [world] Error 2
--
Thanks,
Paul Larson
plars@linuxtestproject.org
http://www.linuxtestproject.org
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-25 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 15:00 2.0-testing.bk Nicholas Berry
2005-01-25 15:43 ` 2.0-testing.bk Ian Pratt
2005-01-25 17:39 ` Paul Larson [this message]
2005-01-25 17:45 ` 2.0-testing.bk Keir Fraser
2005-01-25 18:38 ` 2.0-testing.bk Paul Larson
2005-01-25 16:53 ` 2.0-testing.bk Keir Fraser
2005-01-25 22:08 ` 2.0-testing.bk Kip Macy
2005-01-25 22:22 ` 2.0-testing.bk Keir Fraser
2005-01-25 22:26 ` 2.0-testing.bk Kip Macy
2005-01-26 0:01 ` 2.0-testing.bk Kip Macy
-- strict thread matches above, loose matches on Subject: below --
2005-01-25 13:17 2.0-testing.bk Ian Pratt
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=1106674780.5366.9.camel@localhost.localdomain \
--to=plars@linuxtestproject.org \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.