From: Sean Dague <japh@us.ibm.com>
To: Julian Chesterfield <jac90@cam.ac.uk>
Cc: Jimi Xenidis <jimix@watson.ibm.com>,
xen-devel@lists.xensource.com, julian.chesterfield@xensource.com
Subject: Re: [PATCH][TOOLS] allow the selection of blktap and firmware thru config files
Date: Thu, 10 Aug 2006 22:43:37 -0400 [thread overview]
Message-ID: <20060811024337.GD30773@dargo.dague.pvt> (raw)
In-Reply-To: <68f85b619e06380994b36abaf68ea740@cam.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1226 bytes --]
On Thu, Aug 10, 2006 at 03:27:52PM +0100, Julian Chesterfield wrote:
<snip>
> >>Because libaio is often not included in the distro.
> >
> >You mean there are distros that do not have a libaio devel package?
>
> Correct.
>
> >
> >>In order to avoid breaking the build we either had to include checks
> >>in the Makefile for the existence of the library and build if
> >>necessary, or just statically build within the tree.
> >
> >Assuming the libaio devel package is available, how is this different
> >than the recent build break that required me to install openssl-devel
> >packages?
>
> We link against libcrypto, however I wasn't aware that this requires
> the openssl-devel package. In my experience libcrypto typically ships
> as part of the base distro for utilities such as ssh, scp etc.. Perhaps
> this isn't the case?
In more of the rpm and deb based distros, header files are seperate.
Building against libcrypto (which comes with openssl), requires
openssl-devel (or openssl-dev in the debian case IIRC).
-Sean
--
Sean Dague
IBM Linux Technology Center email: japh@us.ibm.com
Open Hypervisor Team alt: sldague@us.ibm.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 191 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-08-11 2:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 17:23 [PATCH][TOOLS] allow the selection of blktap and firmware thru config files Jimi Xenidis
2006-08-08 18:40 ` Alex Williamson
2006-08-09 9:41 ` Keir Fraser
2006-08-09 12:34 ` Jimi Xenidis
2006-08-09 16:37 ` Keir Fraser
2006-08-10 1:06 ` Jimi Xenidis
2006-08-10 10:08 ` Julian Chesterfield
2006-08-10 10:51 ` Jimi Xenidis
2006-08-10 13:51 ` Julian Chesterfield
2006-08-10 14:08 ` Jimi Xenidis
2006-08-10 14:27 ` Julian Chesterfield
2006-08-11 2:43 ` Sean Dague [this message]
2006-08-10 16:58 ` Jeremy Katz
2006-08-10 22:07 ` Anil Madhavapeddy
2006-08-11 2:45 ` Sean Dague
2006-08-11 11:03 ` Christian Limpach
2006-08-11 13:11 ` Jimi Xenidis
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=20060811024337.GD30773@dargo.dague.pvt \
--to=japh@us.ibm.com \
--cc=jac90@cam.ac.uk \
--cc=jimix@watson.ibm.com \
--cc=julian.chesterfield@xensource.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.