From: Oliver Rath <rath@mglug.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] compile error: 'DMEVENTD_PATH' undeclared
Date: Mon, 31 Mar 2014 15:19:18 +0200 [thread overview]
Message-ID: <53396B56.3050602@mglug.de> (raw)
Hi list,
if i compile lvm2 (from today) with this configure:
./configure --with-thin=internal --with-cache=internal
--with-replicators=internal --enable-udev_sync --enable-udev_rules
then the following occures:
.
.
.
make -C lib
make[1]: Entering directory `/root/lvm2/lib'
gcc -c -I. -I../include -DHAVE_CONFIG_H -DDM_IOCTLS -Wall -Wundef
-Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes
-Wmissing-declarations -Wnested-externs -Winline -Wmissing-noreturn
-Wformat-security -Wredundant-decls -Wpointer-arith -Wuninitialized
-Wmissing-include-dirs -Wfloat-equal -Wstrict-prototypes
-Wold-style-definition -Wmissing-format-attribute -Wjump-misses-init
-Wclobbered -Wempty-body -Wignored-qualifiers -Wmissing-parameter-type
-Wold-style-declaration -Woverride-init -Wtype-limits -Wsync-nand
-Wlogical-op -fPIC -O2 config/config.c -o config/config.o
In file included from config/config.c:70:0:
config/config_settings.h:257:1: error: 'DMEVENTD_PATH' undeclared here
(not in a function)
make[1]: *** [config/config.o] Error 1
make[1]: Leaving directory `/root/lvm2/lib'
make: *** [lib] Error 2
.
.
if i take
./configure --with-thin=internal --with-cache=internal
--with-replicators=internal --enable-udev_sync --enable-udev_rules
--enable-cmdlib --enable-dmeventd
all compiles fine. But I dont know, what dmevetd-flag is good for. Do i
run into problems on a Ubuntu 12.04, if i enable additionally
--enable-cmdlib --enable-dmeventd
before installing?
Tfh!
Regards
Oliver
next reply other threads:[~2014-03-31 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 13:19 Oliver Rath [this message]
2014-03-31 14:08 ` [linux-lvm] compile error: 'DMEVENTD_PATH' undeclared Peter Rajnoha
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=53396B56.3050602@mglug.de \
--to=rath@mglug.de \
--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).