From: Marian Csontos <mcsontos@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Oliver Rath <rath@mglug.de>
Subject: Re: [linux-lvm] addendum [was: lvmdbusd failure(s) at ubuntu ]
Date: Mon, 11 Dec 2017 14:00:35 +0100 [thread overview]
Message-ID: <44b19799-a6c2-9b9d-8d6a-8e988ad9f2dd@redhat.com> (raw)
In-Reply-To: <cd9e1cf3-2680-ef50-8629-161215d467a0@mglug.de>
On 12/11/2017 03:27 AM, Oliver Rath wrote:
> Hi list,
>
> trying to compile lvm2 with these flags:
>
> ./configure --enable-lvmetad --enable-lvmpolld --enable-dmfilemapd
> --enable-applib --enable-cmdlib --enable-dbus-service
> --enable-notify-dbus --enable-python3_bindings
>
> make
> ..
>
> make install
> ..
> warning: install_lib: 'build/lib.linux-x86_64-3.6' does not exist -- no
> Python modules to install
Oliver Rath -vv
Try being more verbose, please.
Removing all context is not helpful at all.
make install for lvmdbusd should run py-compile script found in autoconf
directory, which should write bytecode *.py[co] to that directory.
May be:
- it did not run,
- or it used different directory,
- or ...???
>
> What does this mean?
No idea. Not very helpful answer, but if you post full output from
`configure ...` and `make install`, you might get better one.
-- Martian
>
> Tfh!
>
> Oliver
>
>
>
>
> _______________________________________________
> 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/
>
next prev parent reply other threads:[~2017-12-11 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 2:27 [linux-lvm] addendum [was: lvmdbusd failure(s) at ubuntu ] Oliver Rath
2017-12-11 13:00 ` Marian Csontos [this message]
2017-12-11 18:08 ` [linux-lvm] More logs [was: Re: addendum [was: lvmdbusd failure(s) at ubuntu ]] Oliver Rath
2017-12-12 11:37 ` Oliver Rath
2017-12-12 12:19 ` [linux-lvm] More logs [was: lvmdbusd failure(s) at ubuntu ] Oliver Rath
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=44b19799-a6c2-9b9d-8d6a-8e988ad9f2dd@redhat.com \
--to=mcsontos@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=rath@mglug.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 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).