linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Gang He" <ghe@suse.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] compile lvm2 with --enable-lvmlockd-sanlock on Ubuntu 1710, configure failed.  For help, thanks
Date: Sun, 01 Apr 2018 20:16:17 -0600	[thread overview]
Message-ID: <5AC202F1020000F9000B3146@prv-mh.provo.novell.com> (raw)
In-Reply-To: <71604351584F6A4EBAE558C676F37CA401071B1902@H3CMLB12-EX.srv.huawei-3com.com>

I can compile the code smoothly on openSUSE Tumbleweed, but I am not sure if my configuration is the same with yours.

tb0307-nd3:/usr/src/packages/BUILD/LVM2.2.02.177 # rpm -qa | grep -i san
sane-backends-1.0.27-3.3.x86_64
noto-sans-fonts-20170919-2.1.noarch
adobe-sourcesanspro-fonts-2.020-1.8.noarch
hplip-sane-3.17.9-2.2.x86_64
sanlock-devel-3.6.0-1.2.x86_64
libtsan0-gcc8-8.0.1+r257983-1.1.x86_64
libubsan0-7.3.1+r258025-1.3.x86_64
sane-backends-autoconfig-1.0.27-3.3.x86_64
libsanlock1-3.6.0-1.2.x86_64
ruby2.5-rubygem-rails-html-sanitizer-1.0.3-1.8.x86_64
libasan4-7.3.1+r258025-1.3.x86_64
liblsan0-gcc8-8.0.1+r257983-1.1.x86_64
sanlock-3.6.0-1.2.x86_64


Thanks
Gang


>>> 

> 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
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com 
> https://www.redhat.com/mailman/listinfo/linux-lvm 
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

  reply	other threads:[~2018-04-02  2:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2018-04-04  7:40 Guozhonghua

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=5AC202F1020000F9000B3146@prv-mh.provo.novell.com \
    --to=ghe@suse.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).