From: Andy Grover <agrover@redhat.com>
To: Christophe Vu-Brugier <cvubrugier@fastmail.fm>
Cc: targetcli-fb-devel@lists.fedorahosted.org,
linux-modules <linux-modules@vger.kernel.org>
Subject: Re: Debugging AttributeError: 'module' object has no attribute 'kmod'
Date: Thu, 30 Oct 2014 11:36:41 -0700 [thread overview]
Message-ID: <54528539.4000600@redhat.com> (raw)
In-Reply-To: <20141030173744.681f77df@PAL-U515208D001>
On 10/30/2014 09:37 AM, Christophe Vu-Brugier wrote:
> Hi Andy,
>
> On Thu, 30 Oct 2014 09:24:37 -0700, Andy Grover wrote :
>> On 10/30/2014 08:09 AM, Christophe Vu-Brugier wrote:
>>> Hi Andy,
>>>
>>> I am working on better integrating targetcli in Buildroot. Buildroot
>>> is an easy to configure build system that uses cross compilation to
>>> generate tiny root file systems for embedded platforms.
>>>
>>> Buildroot supports systemd so I built a root file system with
>>> targetcli and systemd. When systemd is selected as the init system in
>>> Buildroot, the python-kmod module is also built by Buildroot (because
>>> kmod is a dependency of systemd). And since python-kmod is present,
>>> targetcli tries to use it. But it fails with the following error:
>>>
>>> # targetcli
>>> Traceback (most recent call last):
>>> File "/usr/bin/targetcli", line 100, in <module>
>>> main()
>>> File "/usr/bin/targetcli", line 63, in main
>>> root_node = UIRoot(shell, as_root=is_root)
>>> File "home/cvubrugier/repos/buildroot/output/x86-targetcli-systemd/target/usr/lib/python3.4/site-packages/targetcli/ui_root.py", line 44, in __init__
>>> File "home/cvubrugier/repos/buildroot/output/x86-targetcli-systemd/target/usr/lib/python3.4/site-packages/rtslib/root.py", line 66, in __init__
>>> File "home/cvubrugier/repos/buildroot/output/x86-targetcli-systemd/target/usr/lib/python3.4/site-packages/rtslib/utils.py", line 364, in modprobe
>>> AttributeError: 'module' object has no attribute 'Kmod'
>>>
>>> Trying to use python-kmod by hand also fails on the system.
>>>
>>> Python 3.4.1 (default, Oct 29 2014, 13:37:35)
>>> [GCC 4.9.1] on linux
>>> Type "help", "copyright", "credits" or "license" for more information.
>>> >>> import kmod
>>> >>> km = kmod.kmod()
>>> Traceback (most recent call last):
>>> File "<stdin>", line 1, in <module>
>>> AttributeError: 'module' object has no attribute 'kmod'
>>>
>>> Maybe python-kmod is not properly built. Do you have some advises of
>>> what I should look at to debug this issue.
>>
>> Can you supply the kmod/python-kmod version information?
>
> This is the latest version of kmod:
>
> # kmod --version
> kmod version 18
(CCing kmod dev list too)
Starting in kmod v17 the Python library was merged into the main kmod
repo, and the version indicates that you are using the Python wrapper
built from that (as opposed to the now-defunct separate project called
python-kmod, whose versions never exceeded 0.9.)
Lucas De Marchi did the build integration because my autotools knowledge
was not sufficient -- I suspect building kmod with --enable-python only
enables Python 2. I'd need to know more about what distro you're on and
look at the packaging scripts, but I think upstream support for building
the library for Python 3 is needed (this might be extremely simple but
it still probably requires a separate --enable-python3 configure
option). Did the packager think they could just take the Py2 binaries
and they'd work for Python 3???
So I'd open an issue with the kmod packager for whatever distro because
something is broken, and maybe the CC'd upstream developers might also
be able to help us have explicit support for building for Python 3?
Thanks -- Regards -- Andy
next parent reply other threads:[~2014-10-30 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141030160932.15107fde@PAL-U515208D001>
[not found] ` <54526645.2010008@redhat.com>
[not found] ` <20141030173744.681f77df@PAL-U515208D001>
2014-10-30 18:36 ` Andy Grover [this message]
2014-11-15 13:34 ` Debugging AttributeError: 'module' object has no attribute 'kmod' Lucas De Marchi
2014-11-15 20:59 ` Christophe Vu-Brugier
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=54528539.4000600@redhat.com \
--to=agrover@redhat.com \
--cc=cvubrugier@fastmail.fm \
--cc=linux-modules@vger.kernel.org \
--cc=targetcli-fb-devel@lists.fedorahosted.org \
/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).