On Sat, Apr 2, 2016 at 2:13 AM, Jeff Darcy <jdarcy@xxxxxxxxxx> wrote:
>
> I've seen a lot of patches blocked lately by this:
>
> > BD xlator requested but required lvm2 development library not found.
>
Hi Jeff,
IIRC, this happens because in the build job use "--enable-bd-xlator"
option while configure;
but looks like bd library dependencies were missing in this slave.
/me looking into configure.ac
[part of configure.ac]
if test "x$enable_bd_xlator" != "xno"; then
AC_CHECK_LIB([lvm2app],
[lvm_init,lvm_lv_from_name],
[HAVE_BD_LIB="yes"],
[HAVE_BD_LIB="no"])
[...]
if test "x$enable_bd_xlator" = "xyes" -a "x$HAVE_BD_LIB" = "xno"; then
echo "BD xlator requested but required lvm2 development library not found."
exit 1
fi
>From above I can say liblvm2app.so doesn't have
lvm_init/lvm_lv_from_name functions or
there is no liblvm2app.so in this slave, hence 'HAVE_BD_LIB' will be set to 'no'
IMO, no one really uses "BD-xlator" and I think we need to remove this
option In the build script while we configure.
Thanks,
-- Prasanna
> It doesn't happen all the time, so there must be something about
> certain patches that triggers it. Any thoughts?
> _______________________________________________
> Gluster-infra mailing list
> Gluster-infra@xxxxxxxxxxx
> http://www.gluster.org/mailman/listinfo/gluster-infra
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
