From: Marc - A. Dahlhaus <mad@wol.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] LVM2 clvmd and STABLE3
Date: Tue, 10 Mar 2009 17:45:12 +0100 [thread overview]
Message-ID: <49B69918.3050307@wol.de> (raw)
In-Reply-To: <49B66C9F.4030607@redhat.com>
Chrissie Caulfield schrieb:
> Marc - A. Dahlhaus [ Administration | Westermann GmbH ] wrote:
>
>> Hello,
>>
>>
>> what is the right approach to build LVM2 with STABLE3,
>> a build with --with-clvmd=corosync or --with-clvmd=cman ?
>>
>>
>
> I recommend you do both.
>
> --with-clvmd=corosync=cman,corosync
>
sounds nice but it doesn't build.
I use the last released tarballs of STABLE3, corosync, openais and LVM2.
I tested the following:
--with-clvmd=corosync=cman,corosync
--with-clvmd=cman,corosync
--with-clvmd=corosync,cman
All end up with:
gcc -m32 -o clvmd clvmd-command.o clvmd.o lvm-functions.o refresh_clvmd.o clvmd-cman.o clvmd-corosync.o -march=i686 -mtune=generic -O2 -pipe -march=i686 -mtune=generic -O2 -pipe -fPIC -Wall -Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Winline -Wmissing-noreturn -Wformat-security -O2 -march=i686 -mtune=generic -O2 -pipe -fPIC -Wall -Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Winline -Wmissing-noreturn -Wformat-security -O2 -fno-strict-aliasing -march=i686 -mtune=generic -O2 -pipe -fPIC -Wall -Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Winline -Wmissing-noreturn -Wformat-security -O2 -Wl,--export-dynamic -L../../libdm -L../../lib -L../../daemons/dmeventd \
-llvm -lpthread -ldevmapper-event -ldevmapper -ldlm -lcman -ldlm -lreadline -lrt -ldl -lncurses
clvmd-corosync.o: In function `_get_cluster_name':
clvmd-corosync.c:(.text+0x695): undefined reference to `confdb_initialize'
clvmd-corosync.c:(.text+0x6c6): undefined reference to `confdb_object_find_start'
clvmd-corosync.c:(.text+0x6dd): undefined reference to `confdb_finalize'
clvmd-corosync.c:(.text+0x727): undefined reference to `confdb_object_find'
clvmd-corosync.c:(.text+0x769): undefined reference to `confdb_key_get'
clvmd-corosync.o: In function `_cluster_closedown':
clvmd-corosync.c:(.text+0x7e9): undefined reference to `cpg_finalize'
clvmd-corosync.c:(.text+0x801): undefined reference to `quorum_finalize'
clvmd-corosync.o: In function `_is_quorate':
clvmd-corosync.c:(.text+0x98d): undefined reference to `quorum_getquorate'
clvmd-corosync.o: In function `_get_main_cluster_fd':
clvmd-corosync.c:(.text+0xadd): undefined reference to `cpg_fd_get'
clvmd-corosync.o: In function `_cluster_fd_callback':
clvmd-corosync.c:(.text+0xb30): undefined reference to `cpg_dispatch'
clvmd-corosync.o: In function `_cluster_send_message':
clvmd-corosync.c:(.text+0xc12): undefined reference to `cpg_mcast_joined'
clvmd-corosync.o: In function `init_corosync_cluster':
clvmd-corosync.c:(.text+0xc80): undefined reference to `cpg_initialize'
clvmd-corosync.c:(.text+0xcec): undefined reference to `quorum_initialize'
clvmd-corosync.c:(.text+0xdb9): undefined reference to `cpg_join'
clvmd-corosync.c:(.text+0xddc): undefined reference to `cpg_finalize'
clvmd-corosync.c:(.text+0xdf4): undefined reference to `quorum_finalize'
clvmd-corosync.c:(.text+0xe66): undefined reference to `cpg_local_get'
clvmd-corosync.c:(.text+0xe89): undefined reference to `cpg_finalize'
clvmd-corosync.c:(.text+0xea1): undefined reference to `quorum_finalize'
clvmd-corosync.c:(.text+0xf1c): undefined reference to `quorum_finalize'
The full configure line for reference:
./configure --enable-cmdlib --enable-dmeventd --enable-pkgconfig \
--disable-selinux --with-clvmd=corosync,cman --with-lvm1=shared \
--with-cluster=shared --with-pool=shared \
--with-snapshots=shared --with-mirrors=internal
> clvmd will default to cman, but you can switch to corosync when you feel
> the need, by adding -Icorosync to the command-line.
>
> Or there's a variable in /etc/sysconfig/cluster called
> CLVMD_CLUSTER_IFACE that is picked up by the init script too.
>
>
next prev parent reply other threads:[~2009-03-10 16:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 13:20 [Cluster-devel] LVM2 clvmd and STABLE3 Marc
2009-03-10 13:35 ` Chrissie Caulfield
2009-03-10 16:45 ` Marc - A. Dahlhaus [this message]
2009-03-10 16:50 ` Chrissie Caulfield
2009-07-30 7:45 ` Marc
2009-07-30 9:01 ` Christine Caulfield
2009-07-30 10:36 ` Marc
2009-07-30 10:42 ` Christine Caulfield
2009-07-30 10:52 ` Marc
2009-07-30 10:54 ` Christine Caulfield
2009-07-30 12:32 ` Marc
2009-07-30 12:39 ` Christine Caulfield
2009-07-30 13:06 ` Marc
2009-07-30 13:11 ` Marc
2009-07-30 13:33 ` Christine Caulfield
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=49B69918.3050307@wol.de \
--to=mad@wol.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.