[linux-lvm] compile lvm2 with --enable-lvmlockd-sanlock on Ubuntu 1710, configure failed. For help, thanks

[Guozhonghua]

Hi, All

I add one file as below, so compiled it successfully. 

root at u610:/usr/lib/x86_64-linux-gnu/pkgconfig# cat libsanlock_client.pc 
		prefix=/usr
		exec_prefix=/usr
		libdir=${prefix}/lib/x86_64-linux-gnu
		includedir=${prefix}/include

		Name: libsanlock_client
		Version: 3.3.0-2.1
		Description: libsanlock_client
		Requires: corosync
		Cflags: -I${includedir}

While compile the code, I found one bug in the file, so there is one patch about. 

+	int lv_info_with_seg_status(struct cmd_context *cmd,
+                const struct lv_segment *lv_seg,
+                struct lv_with_info_and_seg_status *status,
+                int with_open_count, int with_read_ahead)
-	int lv_info_with_seg_status(struct cmd_context *cmd, const struct logical_volume *lv,
-				    const struct lv_segment *lv_seg, int use_layer,
-				    struct lv_with_info_and_seg_status *status,
-				    int with_open_count, int with_read_ahead)
	{
		return 0;
	}


Thanks. 
Guozhonghua.  



> -----邮件原件-----
> 发件人: guozhonghua (Cloud)
> 发送时间: 2018年3月30日 16:34
> 收件人: 'linux-lvm at redhat.com'
> 主题: compile lvm2 with --enable-lvmlockd-sanlock on Ubuntu 1710, configure
> failed. For help, thanks
> 
> 
> Hi,
> 
> I want to have a test of lvmlockd, while try to compile the lvm2, which version is
> LVM2.2.02.177, or 2.2.02.168.
> 
> With the configure:
> ./configure --enable-cmirrord --enable-debug --disable-devmapper
> --enable-lvmetad --enable-lvmpolld --enable-lvmlockd-sanlock --enable-dmeventd
> --enable-udev_sync --enable-cmdlib
> 
> But failed as below with configure error check:
> 
> checking for LOCKD_SANLOCK... no
> configure: error: bailing out
> 
> The environment is Ubuntu 1710.
> 
> And I had install the sanlock as below:
> root at u610:~/LVM2.2.02.177# dpkg -l |grep sanlock
> ii  libsanlock-client1                         3.3.0-2.1
> amd64        Shared storage lock manager (client library)
> ii  libsanlock-dev                             3.3.0-2.1
> amd64        Shared storage lock manager (development files)
> ii  libsanlock1                                3.3.0-2.1
> amd64        Shared storage lock manager (shared library)
> ii  libvirt-sanlock                            3.6.0-1ubuntu5
> amd64        Sanlock plugin for virtlockd
> ii  python-sanlock                             3.3.0-2.1
> amd64        Python bindings to shared storage lock manager
> ii  sanlock                                    3.3.0-2.1
> amd64        Shared storage lock manager
> 
> Is there something wrong with it?
> 
> Thanks