[meta-virtualization] [meta-virt][PATCH 1/1] libvirt: use relative path to local .m4 files

Joe Slater joe.slater at windriver.com
Fri Jul 27 12:45:39 PDT 2018

If our project is in a directory with a pathname of longer than
about 125 characters, configuration will fail with an "Argument
list too long" error.  This patch uses the technique that was applied
to the coreutils recipe.

Signed-off-by: Joe Slater <joe.slater at windriver.com>
 recipes-extended/libvirt/libvirt_4.3.0.bb | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/recipes-extended/libvirt/libvirt_4.3.0.bb b/recipes-extended/libvirt/libvirt_4.3.0.bb
index e6dac5d..194f049 100644
--- a/recipes-extended/libvirt/libvirt_4.3.0.bb
+++ b/recipes-extended/libvirt/libvirt_4.3.0.bb
@@ -42,6 +42,12 @@ SRC_URI[libvirt.sha256sum] = "a531e22c8b985ecb2d1223b913fd6ec0f1800e3ebe02351924
 inherit autotools gettext update-rc.d pkgconfig ptest systemd
+# Override the default set in autotools.bbclass so that we will use relative pathnames
+# to our local m4 files.  This prevents an "Argument list too long" error during configuration
+# if our project is in a directory with an absolute pathname of more than about 125 characters.
+acpaths = "-I ./m4"
 ac_cv_path_XMLCATLOG=/usr/bin/xmlcatalog \
 ac_cv_path_AUGPARSE=/usr/bin/augparse \

More information about the meta-virtualization mailing list