similar to: [libnbd PATCH] lib: remove extra @LIBS@ from pkg-config file

On Thu, Mar 12, 2020 at 12:22:23PM +0100, Pino Toscano wrote: > At the moment it is empty, so probably it does not exist. Remove it to > avoid adding spurious content to the pkg-config file in case that > variable will get a value in the future. > --- > lib/libnbd.pc.in | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/lib/libnbd.pc.in

At the moment it is empty, so probably it does not exist. Remove it to avoid adding spurious content to the pkg-config file in case that variable will get a value in the future. --- lib/libguestfs.pc.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/libguestfs.pc.in b/lib/libguestfs.pc.in index 679ed7eba..013bf0f28 100644 --- a/lib/libguestfs.pc.in +++

On Wed, Mar 11, 2020 at 01:21:06PM +0100, Pino Toscano wrote: > At the moment it is empty, so probably it does not exist. Remove it to > avoid adding spurious content to the pkg-config file in case that > variable will get a value in the future. > --- > lib/libguestfs.pc.in | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/lib/libguestfs.pc.in

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

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

On Wed, Mar 18, 2020 at 01:46:14PM -0400, habib dan aouta wrote: > Hello Richard, > > Hope you are doing well. My name is Habib and I am current student > at the University of North Carolina at Charlotte(U.S). I am > currently following your Libnbd client fuzzing tutorial from the > Wordpress articles

This is slightly redundant with just trying nbd_set_tls(nbd, 2) then checking for failure; however, this function does not set errors and looks more similar to nbd_supports_uri. --- This is borderline enough that I figured I'd post it to check if we want it. generator/generator | 45 ++++++++++++++++++++++++++++++++++++++------- interop/interop.c | 4 ++++ lib/handle.c | 12

At the moment it is empty, so probably it does not exist. Remove it to avoid adding spurious content to the pkg-config file in case that variable will get a value in the future. --- hivex.pc.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hivex.pc.in b/hivex.pc.in index c5f594a..250a58b 100644 --- a/hivex.pc.in +++ b/hivex.pc.in @@ -8,4 +8,4 @@ Version: @VERSION@

On Tue, Mar 21, 2023 at 09:05:12AM -0500, Eric Blake wrote: > > $ podman build -f ci/containers/alpine-edge.Dockerfile -t libnbd-alpine-edge You usually shouldn't need this step when reproducing a problem on CI. Instead just use the container that gitlab has published under the project's registry For any job eg https://gitlab.com/nbdkit/libnbd/-/jobs/3973002673 you'll see at

On Wed, Mar 15, 2023 at 03:30:12PM +0100, Laszlo Ersek wrote: > On 3/15/23 15:01, Eric Blake wrote: > > > [...] > > Thanks for the thorough review; I'm glad all the fine points I sought to > put in the patch were received -- and well-received! :) > > One question: > > > The only change I recommend is the addition of the __attribute__; but > > with

On 3/11/20 7:21 AM, Pino Toscano wrote: > At the moment it is empty, so probably it does not exist. Remove it to > avoid adding spurious content to the pkg-config file in case that > variable will get a value in the future. > --- > lib/libguestfs.pc.in | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/lib/libguestfs.pc.in b/lib/libguestfs.pc.in

So I installed Libnbd which worked fined and then I was trying to run Libnbd-fuzz-wrapper.c and with afl using : afl-fuzz -i fuzzing/testcase_dir -o fuzzing/sync_dir -M fuzz01 \./fuzzing/libnbd-fuzz-wrapper @@ when I try that command it gives me an error saying Libnbd-fuzz-wrapper.c is not an EFL binary. Then I tried to compile Libnbd-fuzz-wrapper.c first into an executable file and then I

So I installed Libnbd which worked fined and then I was trying to run Libnbd-fuzz-wrapper.c and with afl using : afl-fuzz -i fuzzing/testcase_dir -o fuzzing/sync_dir -M fuzz01 \./fuzzing/libnbd-fuzz-wrapper @@ when I try that command it gives me an error saying Libnbd-fuzz-wrapper.c is not an EFL binary. Then I tried to compile Libnbd-fuzz-wrapper.c first into an executable file and then I

On 3/22/23 11:42, Laszlo Ersek wrote: > Now the "podman build -f ci/containers/alpine-edge.Dockerfile -t > libnbd-alpine-edge" command is failing with a different error message -- > the download completes, but the internal relinking etc fails due to > permission errors, which I don't understand. I've asked Martin for comments. > > Meanwhile, your other email (=

On Thu, Mar 09, 2023 at 08:44:51AM +0000, Richard W.M. Jones wrote: > When a highly multi-threaded program such as nbdcopy encounters an > error, there is a race condition in the library which can cause an > assertion failure and thus a core dump: > > (1) An error occurs on one of the threads. nbdcopy calls exit(3). > > (2) In lib/errors.c, the destructor calls

On Tue, Mar 21, 2023 at 07:04:59AM +0100, Laszlo Ersek wrote: > On 3/20/23 20:41, Eric Blake wrote: > > On Sun, Mar 19, 2023 at 10:41:37AM +0100, Laszlo Ersek wrote: > >> This is version 4 of the following sub-series: > >> > >> [libnbd PATCH v3 09/29] lib/utils: introduce async-signal-safe execvpe() > >> [libnbd PATCH v3 10/29] lib/utils: add unit tests

On Wed, Mar 22, 2023 at 12:13:49PM +0100, Laszlo Ersek wrote: > On 3/22/23 11:42, Laszlo Ersek wrote: > > > Now the "podman build -f ci/containers/alpine-edge.Dockerfile -t > > libnbd-alpine-edge" command is failing with a different error message -- > > the download completes, but the internal relinking etc fails due to > > permission errors, which I

On 3/22/23 11:24, Daniel P. Berrang? wrote: > On Tue, Mar 21, 2023 at 03:56:22PM +0100, Laszlo Ersek wrote: >> On 3/21/23 15:05, Eric Blake wrote: >>> On Tue, Mar 21, 2023 at 07:04:59AM +0100, Laszlo Ersek wrote: >>>> On 3/20/23 20:41, Eric Blake wrote: >>>>> On Sun, Mar 19, 2023 at 10:41:37AM +0100, Laszlo Ersek wrote: >>>>>> This is

On Tue, Mar 21, 2023 at 03:56:22PM +0100, Laszlo Ersek wrote: > On 3/21/23 15:05, Eric Blake wrote: > > On Tue, Mar 21, 2023 at 07:04:59AM +0100, Laszlo Ersek wrote: > >> On 3/20/23 20:41, Eric Blake wrote: > >>> On Sun, Mar 19, 2023 at 10:41:37AM +0100, Laszlo Ersek wrote: > >>>> This is version 4 of the following sub-series: > >>>> >

On 2/21/23 19:04, Daniel P. Berrang? wrote: > AFAIK, libnbd/nbdkit haven't made a statement about what platforms > they aim to target. In my response I'm more or less assuming though > that you would only care about similar modern platforms to QEMU/libvirt, > and thus POSIX conformance would not be needed in all areas. Maybe > libnbd/nbdkit want to be more explicit about