linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Guozhonghua <guozhonghua@h3c.com>
To: "linux-lvm@redhat.com" <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] compile lvm2 with --enable-lvmlockd-sanlock on Ubuntu 1710, configure failed.  For help, thanks
Date: Wed, 4 Apr 2018 07:40:44 +0000	[thread overview]
Message-ID: <71604351584F6A4EBAE558C676F37CA401071B23EB@H3CMLB12-EX.srv.huawei-3com.com> (raw)


Hi, All

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

root@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@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@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

             reply	other threads:[~2018-04-04  7:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04  7:40 Guozhonghua [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-30  8:33 [linux-lvm] compile lvm2 with --enable-lvmlockd-sanlock on Ubuntu 1710, configure failed. For help, thanks Guozhonghua
2018-04-02  2:16 ` Gang He

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=71604351584F6A4EBAE558C676F37CA401071B23EB@H3CMLB12-EX.srv.huawei-3com.com \
    --to=guozhonghua@h3c.com \
    --cc=linux-lvm@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).