similar to: [PATCH 1/2] python: Don't build static library

At least libpython2.7-dev and libpython3.3-dev on current Debian/unstable ship with pkg-config files. As with the pkg-config check for Lua, we check for versioned and an unversioned .pc files. --- configure.ac | 35 ++++++++++++++++++++--------------- python/Makefile.am | 2 +- 2 files changed, 21 insertions(+), 16 deletions(-) diff --git a/configure.ac b/configure.ac index

--- configure.ac | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/configure.ac b/configure.ac index 261c44c..6c019e4 100644 --- a/configure.ac +++ b/configure.ac @@ -237,8 +237,8 @@ PYTHON_PREFIX= PYTHON_VERSION= if test "x$PYTHON" != "xno"; then - PYTHON_PREFIX=`$PYTHON -c "import sys; print sys.prefix"` - PYTHON_VERSION=`$PYTHON

This is the same fix I posted a few days ago for hivex (<1369351909-23821-3-git-send-email-bengen@hilluzination.de>). Cheers, -Hilko

The OCaml and Python bindings directly use the utils.c source in common/utils, mostly for guestfs_int_free_string_list. That source contained also functions using gnulib functions, however without linking to gnulib. When building with default build flags (e.g. without as-needed mode), the gnulib symbols cannot be resolved, leading to unusable OCaml and Python libraries. As solution, update the

--- configure.ac | 9 +++++++++ python/Makefile.am | 2 +- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index ea403c3..00ef507 100644 --- a/configure.ac +++ b/configure.ac @@ -1163,6 +1163,14 @@ AS_IF([test "x$enable_python" != "xno"],[ AC_MSG_RESULT([$PYTHON_INSTALLDIR]) fi +

Building against multiple versions of Python is a lot of fun as it is. Add autoconf/automake/libtool (and possible distribution-specific stuff) to the mix and things get really interesting: On Debian and Ubuntu, building against python 3.3 requires an extra include path as documented in <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692387>. As discussed in

The code has been taken from specifically ac_python_devel.m4 published at <http://ac-archive.sf.net/>, it has turned out to be less error-prone on my Debian system. --- configure.ac | 46 ++++++++++++---------------------------------- 1 files changed, 12 insertions(+), 34 deletions(-) diff --git a/configure.ac b/configure.ac index b82a841..5805ddd 100644 --- a/configure.ac +++

On Thu, May 16, Hilko Bengen wrote: > AC_MSG_RESULT([$PYTHON_VERSION]) > - > - AC_MSG_CHECKING([for Python include path]) > - if test -z "$PYTHON_INCLUDEDIR"; then > - python_path=`$PYTHON -c "import distutils.sysconfig; \ > - print (distutils.sysconfig.get_python_inc ());"` > -

On Sun, Jun 16, 2013 at 02:55:29PM +0200, Olaf Hering wrote: > On Thu, May 16, Hilko Bengen wrote: > > > AC_MSG_RESULT([$PYTHON_VERSION]) > > - > > - AC_MSG_CHECKING([for Python include path]) > > - if test -z "$PYTHON_INCLUDEDIR"; then > > - python_path=`$PYTHON -c "import distutils.sysconfig; \ > > -

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,

Patch #7 depends on: https://www.redhat.com/archives/libguestfs/2020-January/msg00035.html No, Python < 3 support is not dropped yet, however it will be easier after this series. Pino Toscano (7): build: enforce a minimum Python version python: drop code for Python < 2.5 python: assume support for Capsules python: remove compile time check for PyString_AsString python: replace

Certain functions are intended to be internal only, but we currently export them anyway. This change moves them into a separate section of guestfs.h protected by a GUESTFS_PRIVATE variable. This change also enables private structs, but doesn't implement any. This change only affects the C api. Language bindings aren't affected, but probably should be in the future. --- align/Makefile.am

On Lua: lua_version=5.3.4 On Perl: perl_version=5.28.0 On Python 2: python_version=2.7.15 On Python 3: python_version=3.7.0 python_pep_384_abi_version=3 On Ruby 2.5.1p57: ruby_api_version=2.5.0 On Tcl: tcl_version=8.6 tcl_patch_level=8.6.8 --- plugins/lua/lua.c | 11 +++++++++++ plugins/perl/perl.c | 4 ++++ plugins/python/python.c | 8 ++++++++

On Monday, 7 January 2019 14:30:00 CET Richard W.M. Jones wrote: > On Thu, Dec 13, 2018 at 06:58:30PM +0100, Pino Toscano wrote: > > Do not assume that the Python plugin of nbdkit has the same name of the > > Python interpreter. > > > > Use the default upstream name of nbdkit to identify it; downstream > > distributions must adjust this variable, in case they

Python 3.8 no longer links C extensions to -lpython, instead relying on the fact that the python binary itself already contains those symbols. This means $PYTHON_LIBS is empty and so the Python bindings are not built. Use a different test to see if the python module is available. --- m4/guestfs-python.m4 | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

Estimados compañeros: Estoy interesado en el NLP, así que, al hallar el post State-of-the-art NLP models from R <https://blogs.rstudio.com/ai/posts/2020-07-30-state-of-the-art-nlp-models-from-r/>, gracias a Carlos Ortega, me puse con ilusión a leerlo. Sin embargo, tengo problemas con lo más básico, la instalación del paquete *transformers*. No puedo

Hi I seem to be having a little trouble with libxenstat, and was wondering if the xenstat guys might be able to help. I''ve pulled the xen-unstable.hg tree and done a somewhat clean install (ie, post-make uninstall, as well as deleting the relevant libxenstat libraries). Next, I entered the tools/xenstat/libxenstat directory and modified the Makefile so that the shared libraries would

Estimados Una pregunta, ¿Que posibilidad hay que esté instalado todo correctamente, pero algo cambie en entorno de python, el cual al ser buscado por R esté dando problemas? Hace años que no utilizo macOS, pero se me ocurre que un programa coloque en entorno adecuado para él, pero al mismo tiempo este toque al entorno requerido por R. Javier Rubén Marcuzzi El dom., 2 ago. 2020 a las 15:59,

Just code motion. This commit makes it clearer what is a utility and what is part of the library. It also makes it clear that we should rename: guestfs-internal-frontend.h -> utils.h guestfs-internal-frontend-cleanups.h -> cleanups.h (?) but this commit does not make that change. --- .gitignore | 10 ++--- Makefile.am

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