ImportError: No module named libvirt #21
Comments
|
gedit /home/mario/Desktop/pkgsrc-wip/py-libvirt/Makefile #$NetBSD: Makefile,v 1.32 2018/11/30 09:59:40 adam Exp $ PKGNAME= ${PYPKGPREFIX}-${DISTNAME:S/-python//} MAINTAINER= pkgsrc-users@NetBSD.org USE_TOOLS+= pkg-config #.include "../../wip/libvirt/buildlink3.mk" .include "/home/mario/Desktop/pkgsrc-wip/libvirt/buildlink3.mk" netbsd-marietto# make make: "/home/mario/Desktop/pkgsrc-wip/py-libvirt/Makefile" line 19: Need an operator |
|
.include "/home/mario/Desktop/pkgsrc-wip/libvirt/buildlink3.mk"
.include "/usr/pkgsrc/lang/python/distutils.mk"
.include "/usr/pkgsrc/mk/bsd.pkg.mk"
Don't those lines need to start from coloumn 0?
- Håvard
|
|
|
netbsd-marietto# make
make: "/home/mario/Desktop/pkgsrc-wip/libvirt/buildlink3.mk" line 11: Could not find ../../security/gnutls/buildlink3.mk
make: "/home/mario/Desktop/pkgsrc-wip/libvirt/buildlink3.mk" line 12: Could not find ../../textproc/libxml2/buildlink3.mk
make: "/home/mario/Desktop/pkgsrc-wip/libvirt/buildlink3.mk" line 13: Could not find ../../devel/yajl/buildlink3.mk
make: "/usr/pkgsrc/mk/bsd.fast.prefs.mk" line 7: Could not find ../../mk/bsd.prefs.mk
make: "/usr/pkgsrc/mk/bsd.prefs.mk" line 377: Cannot open /mk/defaults/mk.conf
make: "/usr/pkgsrc/mk/bsd.prefs.mk" line 395: Cannot open /mk/platform/NetBSD.mk
etc. etc. etc.
Have you manually messed with ${_PKGSRC_TOPDIR}? "Don't do that!"
The leading underscore in the variable name is an indication that this
is a private variable for the pkgsrc mk implementation, and thus not a
variable the user is expected to tweak. The construct in
mk/bsd.prefs.mk which includes mk/defaults/mk.conf looks like this:
.include "${_PKGSRC_TOPDIR}/mk/defaults/mk.conf"
and your make invocation seems to think that ${_PKGSRC_TOPDIR} is the
empty string, which it most certainly should not be.
Regards,
- Håvard
|
|
No. The only thing that I did has been to comment these lines : and I have changed the paths with these : because if I don't do that,I get the following error : |
|
The pkgsrc-wip repository needs to be checked out as "wip" and put into /usr/pkgsrc (or wherever the rest of your pkgsrc checkout is). We do not use github issues, please use the pkgsrc-users@NetBSD.org mailing list instead. |
|
I've already bootstrapped the pkgsrc. They are in /home/marietto/Desktop/pkgsrc-wip folder. Infact I have exchanged the paths stored in the Makefile with these : but I got the folowing situation : |
|
Please use the mailing list, as I said above. You need to get a checkout of pkgsrc in source form, e.g. in /home/marietto/Desktop/pkgsrc; then you need to put the checkout of the wip repository at /home/marietto/Desktop/pkgsrc/wip. The bootstrap destination is for the binaries, not the sources. If you bootstrapped into /home/marietto/Desktop/pkgsrc-wip you will find your binaries in /home/marietto/Desktop/pkgsrc-wip/bin You still need the pkgsrc sources separately (see above). |
wip-sync
pushed a commit
that referenced
this issue
Jun 21, 2024
0.6.6 (2023-10-03)
Bug fixes
Fix PyMem_Calloc() call signature. (#76)
Contributors
@dholth
@kenodegard
0.6.5 (2023-10-02)
Enhancements
Update Python version support. (#56)
Bug fixes
Use PyMem_Calloc() to initialize memory to 0. (#58)
Contributors
@conda-bot
@dholth made their first contribution in #54
@kenodegard
0.6.4 (2022-10-24)
Fix memory leak in blocksol() when iterating over solutions
0.6.3 (2017-10-29)
Revert 'always use Python memory manager'
0.6.2 (2017-03-16)
update picosat to 965
fixed version attribute on Windows, #21
fix some typos
add official Python 3.5 and 3.6 support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello.
I've just installed virt-manager with pkgin. Everything went ok. But,when I ran it,an error came up :
Googling a little bit maybe I've found the solution here :
https://www.unitedbsd.com/d/285-linux-user-and-netbsd-enthusiast-hoping-to-migrate-some-day
where "kim" said :
Looking at pkgsrc/sysutils/libvirt/PLIST it doesn't look like the package provides any Python bindings -- which is what the "ImportError: No module named libvirt" error message is about. You could try py-libvirt from pkgsrc-wip and see how that works out.
I tried,but it didn't work :
The text was updated successfully, but these errors were encountered: