search for: 599752d

...+exec_prefix=@abs_top_builddir@ +libdir=@abs_top_builddir@/lib/.libs +includedir=@abs_top_srcdir@/include + +Name: @PACKAGE_NAME@ +Version: @PACKAGE_VERSION@ +Description: NBD client library in userspace +Requires: +Cflags: -I${includedir} +Libs: -L${libdir} -lnbd diff --git a/run.in b/run.in index 599752d..a7a2850 100755 --- a/run.in +++ b/run.in @@ -1,6 +1,6 @@ #!/usr/bin/env bash # libnbd 'run' programs locally script -# Copyright (C) 2011-2019 Red Hat Inc. +# Copyright (C) 2011-2020 Red Hat Inc. # # @configure_input@ # @@ -35,6 +35,12 @@ # >>> import nbd # locally-comp...

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

...for the pidfile to appear. +for i in {1..60}; do + if test -f $pidfile; then + break + fi + sleep 1 +done +if ! test -f $pidfile; then + echo "$0: nbdfuse PID file $pidfile was not created" + exit 1 +fi + +cmp $data $mp/nbd diff --git a/run.in b/run.in index 83c92a7..599752d 100755 --- a/run.in +++ b/run.in @@ -51,6 +51,7 @@ s="$(cd @abs_srcdir@ && pwd)" b="$(cd @abs_builddir@ && pwd)" # Set the PATH to contain all libnbd binaries. +prepend PATH "$b/fuse" prepend PATH "$b/sh" export PATH diff --git a/sh/nb...