Re: [Xen-devel] [PATCH][TOOLS] allow the selection of blktap and firmware thru config files

[Julian Chesterfield <jac90@xxxxxxxxx>]

On 10 Aug 2006, at 15:08, Jimi Xenidis wrote:

> On Aug 10, 2006, at 9:51 AM, Julian Chesterfield wrote:
>
> > On 10 Aug 2006, at 11:51, Jimi Xenidis wrote:
> >
> > > On Aug 10, 2006, at 6:08 AM, Julian Chesterfield wrote:
> > >
> > > > Thanks Jim. I'll post the patch to the libaio folks also so we can 
> > > > keep things in synch.
> > > > On 10 Aug 2006, at 02:06, Jimi Xenidis wrote:
> > > >
> > > > > On Aug 9, 2006, at 12:37 PM, Keir Fraser wrote:
> > > > > > On 9/8/06 1:34 pm, "Jimi Xenidis" <jimix@xxxxxxxxxxxxxx> wrote:
> > > > > > > I may have missed this discussion, but why can't we just use the 
> > > > > > > one
> > > > > > > that comes with the Distro?
> > > > > > That's a question for Julian (cc'ed).
> > >
> > > Thanks... but... you... never... said... why?
> > 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?
> > We chose the latter since it was the cleanest approach.
> warning: maintaining and monitoring an external package that your 
> system depends on is always fraught with issues, but it your makework 
> :(
Certainly, we'd rather not maintain a separate version of libaio. Given 
the alternative options of either disabling the automatic blktap build 
or causing build failures for significant numbers of people this really 
seemed to be the only option. We're happy to revisit the Makefile build 
check option however if this is the preferred approach.
Thanks,
Julian

> -JX

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel