From: Chris Lalancette <clalance@redhat.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH]: Add openssl-dev and xorg-x11-dev to README
Date: Tue, 27 Feb 2007 11:36:33 -0500 [thread overview]
Message-ID: <45E45E11.2050606@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
Attached is a documentation patch to the top-level README file; it just adds two
notes saying that you need to have openssl-devel and xorg-x11-devel installed to
successfully complete a "make world" at the top level.
Signed-off-by: Chris Lalancette <clalance@redhat.com>
[-- Attachment #2: xen-3.0.5-README.patch --]
[-- Type: text/x-patch, Size: 563 bytes --]
diff -r 1c5e6239a8d0 README
--- a/README Sun Feb 25 23:58:33 2007 -0600
+++ b/README Tue Feb 27 11:34:17 2007 -0500
@@ -92,6 +92,8 @@ provided by your Linux distributor:
* Development install of zlib (e.g., zlib-dev)
* Development install of Python v2.3 or later (e.g., python-dev)
* Development install of curses (e.g., libncurses-dev)
+ * Development install of openssl (e.g., openssl-dev)
+ * Development install of x11 (e.g. xorg-x11-dev)
* bridge-utils package (/sbin/brctl)
* iproute package (/sbin/ip)
* hotplug or udev
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2007-02-27 16:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=45E45E11.2050606@redhat.com \
--to=clalance@redhat.com \
--cc=xen-devel@lists.xensource.com \
/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.