From: Peter Lieven <pl@kamp.de>
To: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel@nongnu.org
Cc: Fam Zheng <famz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block/nfs: use per-object vars and make it modular
Date: Tue, 13 May 2014 15:04:39 +0200 [thread overview]
Message-ID: <53721867.5080404@kamp.de> (raw)
In-Reply-To: <1399813620-26668-1-git-send-email-mjt@msgid.tls.msk.ru>
On 11.05.2014 15:07, Michael Tokarev wrote:
> nfs block module uses libnfs and uses pkg-config to determine
> its build information. Somehow it used only --libs, not --cflags,
> and added those libs into global $LIBS, instead of using per-object
> variable.
the missing cflags stuff was due to a bug in the libnfs.pc file.
https://github.com/sahlberg/libnfs/commit/d47c989d886e5398143d43d3b6d25fdf7210cb11
as there where no special flags I dropped it. this was before we realized
that we had to depend on a newer libnfs version anyway. thanks for spotting this.
>
> Use both --libs and --cflags, use them as per-object variable,
> and finally make block/nfs.o to be modular.
can you explain the modular stuff?
Thanks,
Peter
>
> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
> ---
> block/Makefile.objs | 2 ++
> configure | 6 ++++--
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/block/Makefile.objs b/block/Makefile.objs
> index fd88c03..38ddc0e 100644
> --- a/block/Makefile.objs
> +++ b/block/Makefile.objs
> @@ -35,5 +35,7 @@ gluster.o-cflags := $(GLUSTERFS_CFLAGS)
> gluster.o-libs := $(GLUSTERFS_LIBS)
> ssh.o-cflags := $(LIBSSH2_CFLAGS)
> ssh.o-libs := $(LIBSSH2_LIBS)
> +nfs.o-cflags := $(LIBNFS_CFLAGS)
> +nfs.o-libs := $(LIBNFS_LIBS)
> qcow.o-libs := -lz
> linux-aio.o-libs := -laio
> diff --git a/configure b/configure
> index ac2fa15..3bc91f6 100755
> --- a/configure
> +++ b/configure
> @@ -3928,7 +3928,7 @@ if test "$libnfs" != "no" ; then
> if $pkg_config --atleast-version=1.9.3 libnfs; then
> libnfs="yes"
> libnfs_libs=$($pkg_config --libs libnfs)
> - LIBS="$LIBS $libnfs_libs"
> + libnfs_cflags=$($pkg_config --cflags libnfs)
> else
> if test "$libnfs" = "yes" ; then
> feature_not_found "libnfs"
> @@ -4534,7 +4534,9 @@ if test "$libiscsi" = "yes" ; then
> fi
>
> if test "$libnfs" = "yes" ; then
> - echo "CONFIG_LIBNFS=y" >> $config_host_mak
> + echo "CONFIG_LIBNFS=m" >> $config_host_mak
> + echo "LIBNFS_CFLAGS=$libnfs_cflags" >> $config_host_mak
> + echo "LIBNFS_LIBS=$libnfs_libs" >> $config_host_mak
> fi
>
> if test "$seccomp" = "yes"; then
next prev parent reply other threads:[~2014-05-13 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 13:07 [Qemu-devel] [PATCH] block/nfs: use per-object vars and make it modular Michael Tokarev
2014-05-13 13:04 ` Peter Lieven [this message]
2014-05-13 13:19 ` Fam Zheng
2014-05-13 13:35 ` Peter Lieven
2014-05-13 14:15 ` Fam Zheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53721867.5080404@kamp.de \
--to=pl@kamp.de \
--cc=famz@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).