search for: guestfs_python

This commit starts to split our massive, monolithic configure.ac file into smaller files, using the m4_include mechanism to combine them. I don't know if we should really do this, so I'm open to comments about it. However: - Our configure.ac script is 1800+ lines long, and that's pretty long. - configure.ac lacks structure; splitting it up might improve that. - From what I read,

...ite-packages path... /opt/python/x86_64/3.6.3-1/lib/python3.6/site-packages > checking for Python extension suffix (PEP-3149)... .cpython-36m-x86_64-linux-gnu.so > checking for PyCapsule_New in -lc... no This is supposed to be ‘yes’ which is why it's failing. You'll have to debug m4/guestfs_python.m4 and config.log to find out why that is but something is obviously broken about your Python installation. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for...

...misc_libraries.m4]) dnl Check for language bindings. +AS_ECHO +AS_ECHO(["Checking for OCaml:"]) m4_include([m4/guestfs_ocaml.m4]) +AS_ECHO +AS_ECHO(["Checking for Perl:"]) m4_include([m4/guestfs_perl.m4]) +AS_ECHO +AS_ECHO(["Checking for Python:"]) m4_include([m4/guestfs_python.m4]) +AS_ECHO +AS_ECHO(["Checking for Ruby:"]) m4_include([m4/guestfs_ruby.m4]) +AS_ECHO +AS_ECHO(["Checking for Java:"]) m4_include([m4/guestfs_java.m4]) +AS_ECHO +AS_ECHO(["Checking for Haskell:"]) m4_include([m4/guestfs_haskell.m4]) +AS_ECHO +AS_ECHO(["Check...

Two (not related to each other) refactorings: Patches 1-12 split configure.ac into smaller files using the m4_include mechanism. Patches 13-15 split out parts of guestfs.pod (ie. guestfs(3)) into three new manual pages: guestfs-hacking(3) - how to extend and contribute to libguestfs guestfs-internals(3) - architecture and internals guestfs-security(3) - security and CVEs Patch 16 is a

...OCaml:"]) +HEADING([Checking for OCaml]) m4_include([m4/guestfs_ocaml.m4]) -AS_ECHO -AS_ECHO(["Checking for Perl:"]) +HEADING([Checking for Perl]) m4_include([m4/guestfs_perl.m4]) -AS_ECHO -AS_ECHO(["Checking for Python:"]) +HEADING([Checking for Python]) m4_include([m4/guestfs_python.m4]) -AS_ECHO -AS_ECHO(["Checking for Ruby:"]) +HEADING([Checking for Ruby]) m4_include([m4/guestfs_ruby.m4]) -AS_ECHO -AS_ECHO(["Checking for Java:"]) +HEADING([Checking for Java]) m4_include([m4/guestfs_java.m4]) -AS_ECHO -AS_ECHO(["Checking for Haskell:"]) +HEADIN...

If the connection is not local, paths of disks will refer to the remote host, which were mistakenly handled as local paths (in the best case failing to open a non-existing disk, and in the worst case opening a different disk!). In case the disks are remote resources like ssh or ceph, nothing guarantees that the hostname can be reached from the local machine, or even that it is actually the same on

Hopefully this time ...