similar to: [PATCH] build: fix includedir in uninstalled libguestfs.pc

--- autoconf/configure.ac | 4 +++- cmake/modules/LLVMConfig.cmake.in | 3 ++- configure | 4 +++- tools/llvm-config/Makefile | 6 ++++++ tools/llvm-config/llvm-config.in.in | 3 ++- 5 files changed, 16 insertions(+), 4 deletions(-) diff --git a/autoconf/configure.ac b/autoconf/configure.ac index f3e94e8..cd943cc 100644 ---

Why? -eric On Sep 20, 2011, at 9:14 AM, Johannes Obermayr wrote: > --- > autoconf/configure.ac | 4 +++- > cmake/modules/LLVMConfig.cmake.in | 3 ++- > configure | 4 +++- > tools/llvm-config/Makefile | 6 ++++++ > tools/llvm-config/llvm-config.in.in | 3 ++- > 5 files changed, 16 insertions(+), 4 deletions(-)

When we are valgrinding we don't really care about the child processes, which might be qemu, libvirtd, etc. So disable tracing into children (at least, as far as is possible with valgrind, which is not entirely disabling it, but suppressing it). --- m4/guestfs_progs.m4 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/m4/guestfs_progs.m4 b/m4/guestfs_progs.m4 index

- Add $(srcdir), $(builddir) to Makefiles where required - Post-process ocamldep output - generate ocaml/.depends --- builder/Makefile.am | 7 ++++--- common/mlgettext/Makefile.am | 2 +- common/mlpcre/Makefile.am | 2 +- common/mlprogress/Makefile.am | 2 +- common/mlstdutils/Makefile.am | 2 +- common/mltools/Makefile.am | 2 +- common/mlutils/Makefile.am | 2 +-

We use a similar trick to libvirt to allow external C programs that use libguestfs to be compiled against the built (but not installed) libguestfs with: ../libguestfs/run ./configure make What actually happens is we have a second pkg-config file (lib/local/libguestfs.pc) which points to the locally built libguestfs. The ./run script sets up PKG_CONFIG_PATH to point to this directory.

We use a similar trick to libvirt and libguestfs to allow external C programs that use libnbd to be compiled against the built (but not installed) libnbd with: ../libnbd/run ./configure make What actually happens is we have a second pkg-config file (lib/local/libnbd.pc) which points to the locally built libnbd. The ./run script sets up PKG_CONFIG_PATH to point to this directory. Assuming

These changes allow virt-v2v to be compiled against the build directory of a non-installed libguestfs. Note that some small changes are also required to common and virt-v2v itself. I will post those separately. Rich.

I am building from source on RHEL 4 and have run into a problem while running "make check": running code in 'lapack.R' ...make[3]: *** [lapack.Rout] Error 1 make[3]: Leaving directory `/opt/R/R-2.9.1/tests' make[2]: *** [test-Specific] Error 2 make[2]: Leaving directory `/opt/R/R-2.9.1/tests' make[1]: *** [test-all-basics] Error 1 make[1]: Leaving

For these simple compile tests where we want to ensure that a basic external program could be compiled using libnbd, we shouldn't include <config.h>. This is because we want to test here that <libnbd.h> can stand alone, without needing anything defined by the GNU autotools infrastructure. Of course we can use <config.h> in other test programs where we aren't evaluating

> On 22/02/2023 08:41 EET James Brown <jlbrown at bordo.com.au> wrote: > > > > On 22 Feb 2023, at 5:33 pm, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > > > > Thanks Aki, that was helpful. When I add that I get: > > > > > > checking for LIBSODIUM... no > > > configure: error: Can't build with libsodium: not

Michael Grigoni wrote: >> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> Package ogg was not found in the pkg-config search path. >> Perhaps you should add the directory containing `ogg.pc' >> to the PKG_CONFIG_PATH environment variable My previous post was somehow mangled: Here

> Karl just pointed out to me that libshout is now installing its header > in $prefix/include/shout.h instead of $prefix/include/shout/shout.h. (Sorry for not replying directly, I'm not on the list and I can't figure out if gmane allows me to reply to a mail.) It's probably best to try and contact the committer first - It's possible few other people understand or care

Version 2: https://www.redhat.com/archives/libguestfs/2020-April/thread.html#00166 Version 3 contains all changes discussed in the previous review. Rich.

Nouveau related headers are installed in I${includedir}/libdrm now. --- nouveau/libdrm_nouveau.pc.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nouveau/libdrm_nouveau.pc.in b/nouveau/libdrm_nouveau.pc.in index 6170613..454fc87 100644 --- a/nouveau/libdrm_nouveau.pc.in +++ b/nouveau/libdrm_nouveau.pc.in @@ -7,5 +7,5 @@ Name: libdrm_nouveau Description: Userspace interface

In most cases it is incorrect to use this - pay attention to the note at the top of the newly added file. --- .gitignore | 1 + configure.ac | 1 + server/local/nbdkit.pc.in | 45 +++++++++++++++++++++++++++++++++++++++ 3 files changed, 47 insertions(+) diff --git a/.gitignore b/.gitignore index 4f6fcf1b..8c701295 100644 --- a/.gitignore +++ b/.gitignore @@ -83,6

- Add $(srcdir), $(builddir) to Makefiles where required - Post-process ocamldep output - generate ocaml/.depends Gbp-Pq: Name 0012-Fix-out-of-tree-builds-of-OCaml-components.patch --- builder/Makefile.am | 7 ++++--- common/mlgettext/Makefile.am | 2 +- common/mlpcre/Makefile.am | 2 +- common/mlprogress/Makefile.am | 2 +- common/mlstdutils/Makefile.am | 2 +-

I am unable to get the #includedir function to work with sudo. This works just fine on all my CentOS 5.6 servers, but on 6 it is being ignored. I have this line in the file /etc/sudoers.d/zabbix-puppet zabbix ALL=NOPASSWD: /var/lib/zabbix/bin/start_puppet However sudo still requires a password. If I put that same line into /etc/sudoers file , there is no password prompt. At the end of my

Version 1 was here: https://www.redhat.com/archives/libguestfs/2020-April/thread.html#00160 Version 2 side-steps the objections to the first patch by using a well-formed alternate nbdkit.pc file and running ordinary pkg-config against it, so any parsing of --cflags etc will be done by pkg-config. The first patch is essentially the same idea as:

Hi, I spent some time today to figure out why my clients are unable to connect to my Samba AD domain member after updating the operating system from CentOS 7.2 to 7.3 and I thought sharing the reason and the workaround can help others: If you run RHEL/CentOS 7.2 with an unmodified /etc/krb5.conf file and update to 7.3, the krb5-workstation-1.14.1-27 package adds an "includedir"

On Tuesday 20 September 2011 11:23:05 Eric Christopher wrote: > Why? > > -eric > Because openSUSE and many other linux distributions put all things to /usr/lib (i586) and /usr/lib64 (x86_64) or /usr/lib32. So it is possible to install x86 and x86_64 versions at the same time ... (See also http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-July/042068.html and