Closed kescherCode closed 2 years ago
The intent here is that the NBDKit plugin should be installed into nbdkit's ${plugindir}
, which is a variable defined by the nbdkit installation itself and made available to us via pkg-config:
$ pkg-config --variable=plugindir nbdkit
/usr/lib64/nbdkit/plugins
For most people, it doesn't make sense to install an nbdkit plugin somewhere else, so even a change to ${prefix}
should not affect where the NBD plugin goes. (Note, if what you want is to install everything under some directory, use DESTDIR
for that).
In any case, there's a way for you to override this, by overriding NBDKIT_PLUGINDIR
on the command line:
$ ./configure NBDKIT_PLUGINDIR=/tmp/foobar
$ make -n install
...
list='nbdkit-s3backer-plugin.la'; test -n "/tmp/foobar" || list=; \
list2=; for p in $list; do \
if test -f $p; then \
list2="$list2 $p"; \
else :; fi; \
done; \
test -z "$list2" || { \
echo " /usr/bin/mkdir -p '/tmp/foobar'"; \
/usr/bin/mkdir -p "/tmp/foobar" || exit 1; \
echo " /bin/sh ./libtool --mode=install /usr/bin/install -c $list2 '/tmp/foobar'"; \
/bin/sh ./libtool --mode=install /usr/bin/install -c $list2 "/tmp/foobar"; \
}
:
Let me know if the above makes sense. If not feel free to re-open this issue.
This does make sense, yes.
I am currently attempting to build s3backer in NBD mode, for packaging purposes. I am running:
Everything up to the
make install
command works just as expected. However, when make install is being run, the following happens:Expected
nbdkit-s3backer-plugin.so
being installed into/tmp/s3backer-build/pkg/s3backer/usr/lib/nbdkit/plugins
Actual
nbdkit-s3backer-plugin.so
being (attempted to be) installed directly into/usr/lib/nbdkit/plugins