search for: pkgconf

Unfortunately only tests the ./run version rather than the real one. --- .gitignore | 1 + configure.ac | 2 ++ tests/Makefile.am | 4 +++- tests/pkgconf.sh.in | 38 ++++++++++++++++++++++++++++++++++++++ 4 files changed, 44 insertions(+), 1 deletion(-) diff --git a/.gitignore b/.gitignore index 777471b..dea9274 100644 --- a/.gitignore +++ b/.gitignore @@ -159,6 +159,7 @@ Makefile.in /tests/keys.psk /tests/meta-base-allocation /tests/oldstyle +/...

...e requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: r-base-dev : Depends: pkgconf but it is not going to be installed E: Broken packages I was brave/foolish enough to just plow ahead: [08:58] ? wviechtb at wv-x5 ? ~/ ? sudo apt install pkgconf Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be inst...

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

...ght (C) 2013-2020 Red Hat Inc. > # > # This library is free software; you can redistribute it and/or > # modify it under the terms of the GNU Lesser General Public > @@ -36,6 +36,7 @@ EXTRA_DIST = \ > functions.sh.in \ > make-pki.sh \ > meta-base-allocation.sh \ > + pkgconf.sh.in \ As AC_CONFIG_FILES has tests/pkgconf.sh, the .in file is included automatically by autotools in the dist tarballs. Hence, this line is extra. > diff --git a/tests/pkgconf.sh.in b/tests/pkgconf.sh.in > new file mode 100755 > index 0000000..14b513b > --- /dev/null > +++ b/tes...

...fig binary which will return the correct CFLAGS. Fixes: commit 1ff44288ae1cf95428283e252edd9474c3fe3b55 Thanks: Dan Berrangé, Eric Blake --- .gitignore | 1 + configure.ac | 2 ++ plugins/golang/Makefile.am | 4 +++ plugins/golang/golang-pkgconf.sh.in | 40 +++++++++++++++++++++++++++++ 4 files changed, 47 insertions(+) diff --git a/.gitignore b/.gitignore index 4f6fcf1b..bda3b05a 100644 --- a/.gitignore +++ b/.gitignore @@ -74,6 +74,7 @@ plugins/*/*.3 /plugins/eval/methods.c /plugins/golang/examples/*/nbdkit-*-plugin.h /plugins/golang...

On Fri, Mar 13, 2020 at 12:57:52PM +0100, Pino Toscano wrote: > On Thursday, 12 March 2020 23:46:57 CET Richard W.M. Jones wrote: > > Unfortunately only tests the ./run version rather than the real one. > > --- > > Is it worth it though? The new pkg-config file won't be deployed to > users, and it should (hopefully) not break if the locations of the > sources are

I don't really know enough on this topic to comment on the patch, except for a general comment that this sounds like it could be a bug in either pkg-config or bash-completion. 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 virtual machines. Tiny

...n ./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. Assuming that ./configure is using pkg-config/pkgconf and > not some other half-baked solution it will pick up the libguestfs.pc > file from here which will set CFLAGS and LIBS appropriately. > --- > .gitignore | 1 + > configure.ac | 1 + > lib/Makefile.am | 1 + > lib/local/libgue...

Hello, Sorry if it is not the right place.. I installed R-2.13.0 on a x86_64 linux server. All went fine, but the svg() function yells: > svg() Error in svg() : cairo-based devices are not supported on this build I have the Cairo, cairoDevice, RSvgDevice packages installed, and running. > Cairo.capabilities() png jpeg tiff pdf svg ps x11 win TRUE TRUE TRUE TRUE TRUE

...E_TIFFIO_H 1 _ACEOF From 3.3.0 on, it starts like this (with indentation adjusted): if test "${use_libtiff}" = yes; then mod= ## pkg-config support was introduced in libtiff 4.0.0 ## I guess the module name might change in future, so ## program defensively here. if "${PKGCONF}" --exists libtiff-4; then mod=libtiff-4 fi if test -n "${mod}"; then save_CPPFLAGS=${CPPFLAGS} TIF_CPPFLAGS=`"${PKGCONF}" --cflags ${mod}` CPPFLAGS="${CPPFLAGS} ${TIF_CPPFLAGS}" for ac_header in tiffio.h do : ac_fn_c_check_header_mongrel "...

...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 that ./configure is using pkg-config/pkgconf and not some other half-baked solution it will pick up the libnbd.pc file from here which will set CFLAGS and LIBS appropriately. See also this libguestfs commit: https://github.com/libguestfs/libguestfs/commit/e33b3c83a02c1d7e82018105166e451373e8c218 --- .gitignore | 1 + configure....

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.

...; the library is installed in the C<$filterdir> directory, then users can be run it by only typing: nbdkit --filter=name plugin [args] The location of the C<$filterdir> directory is set when nbdkit is compiled and can be found by doing: nbdkit --dump-config If using the pkg-config/pkgconf system then you can also find the filter directory at compile time by doing: pkgconf nbdkit --variable=filterdir =head1 PKG-CONFIG/PKGCONF nbdkit provides a pkg-config/pkgconf file called C<nbdkit.pc> which should be installed on the correct path when the nbdkit development environment is...

...m4-1.4.18,1 GNU M4 mysql57-client-5.7.22_1 Multithreaded SQL database (client) pcre-8.40_1 Perl Compatible Regular Expressions library perl5-5.26.2 Practical Extraction and Report Language pkg-1.10.5 Package manager pkgconf-1.4.2,1 Utility to help to configure compiler and linker flags protobuf-3.5.2 Data interchange format library python2-2_3 The "meta-port" for version 2 of the Python interpreter python27-2.7.14_1 Interpreted object-oriented pr...

One last shot in the dark: what if you reboot the router in front of the node in question? Sometimes it was surprised, when managing different mac addresses on the same adapter. I might be missing some parts, but did the mobo work before? Best regards Zoran

...estfs 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. Assuming that ./configure is using pkg-config/pkgconf and not some other half-baked solution it will pick up the libguestfs.pc file from here which will set CFLAGS and LIBS appropriately. --- .gitignore | 1 + configure.ac | 1 + lib/Makefile.am | 1 + lib/local/libguestfs.pc.in | 36 +++++++++++++++++++++++...

...ary is installed in the +C<$filterdir> directory, then users can be run it by only typing: + + nbdkit --filter=name plugin [args] + +The location of the C<$filterdir> directory is set when nbdkit is +compiled and can be found by doing: + + nbdkit --dump-config + +If using the pkg-config/pkgconf system then you can also find the +filter directory at compile time by doing: + + pkgconf nbdkit --variable=filterdir + +=head1 PKG-CONFIG/PKGCONF + +nbdkit provides a pkg-config/pkgconf file called C<nbdkit.pc> which +should be installed on the correct path when the nbdkit development +envir...

...ary is installed in the +C<$filterdir> directory, then users can be run it by only typing: + + nbdkit --filter=name plugin [args] + +The location of the C<$filterdir> directory is set when nbdkit is +compiled and can be found by doing: + + nbdkit --dump-config + +If using the pkg-config/pkgconf system then you can also find the +filter directory at compile time by doing: + + pkgconf nbdkit --variable=filterdir + +=head1 PKG-CONFIG/PKGCONF + +nbdkit provides a pkg-config/pkgconf file called C<nbdkit.pc> which +should be installed on the correct path when the nbdkit development +envir...

The first release candidate of the 9.1-RELEASE release cycle is now available on the FTP servers for amd64, i386, and powerpc64. The MD5/SHA256 checksums are at the bottom of this message. The ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/9.1/ (or any of the FreeBSD mirror sites). Current

...nfig.site to: ~/R-3.2.2$ svn diff config.site Index: config.site =================================================================== --- config.site (revision 69236) +++ config.site (working copy) @@ -278,3 +278,8 @@ ## Path to the version of pkg-config to be used for locating cairographics. ## PKGCONF = +F77=gfortran48 +FC=${F77} +CC=gcc48 +CXX=g++48 +OBJC=gcc48 Then plain-vanilla configure && make worked without a hitch: ~/R-3.2.2$ ./configure [...] R is now configured for x86_64-unknown-freebsd10.2 Source directory: . Installation directory: /usr/local C compiler:...