linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [nfs-utils PATCH] build: avoid AM_CONDITIONAL in conditional execution.
Date: Fri, 18 May 2012 11:05:07 -0400	[thread overview]
Message-ID: <20120518110507.75bbc20e@corrin.poochiereds.net> (raw)
In-Reply-To: <1337297671-9614-1-git-send-email-flameeyes@flameeyes.eu>

On Thu, 17 May 2012 16:34:31 -0700
Diego Elio Pettenò <flameeyes@flameeyes.eu> wrote:

> Automake does not support conditional AM_CONDITIONAL calls; what that
> means is that you always have to execute AM_CONDITIONAL one way or the
> other. Both the libsqlite3.m4 file and the nfsdcld conditionals are
> executed only when NFSv4 is enabled, which breaks building with
> --disable-nfsv4.
> 
> Remove the SQLite3 conditional altogether as it's never used, and move
> the nfsdcld conditional outside of the conditional code.
> 
> Signed-off-by: Diego Elio Pettenò <flameeyes@flameeyes.eu>
> ---
>  aclocal/libsqlite3.m4 |    1 -
>  configure.ac          |    3 +--
>  2 files changed, 1 insertions(+), 3 deletions(-)
> 
> diff --git a/aclocal/libsqlite3.m4 b/aclocal/libsqlite3.m4
> index 73d1e46..8c38993 100644
> --- a/aclocal/libsqlite3.m4
> +++ b/aclocal/libsqlite3.m4
> @@ -29,5 +29,4 @@ AC_DEFUN([AC_SQLITE3_VERS], [
>      LIBS="$saved_LIBS"])
>  
>    AC_MSG_RESULT($libsqlite3_cv_is_recent)
> -  AM_CONDITIONAL(CONFIG_SQLITE3, [test "$libsqlite3_cv_is_recent" = "yes"])
>  ])dnl
> diff --git a/configure.ac b/configure.ac
> index 9ba53e2..b408f1b 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -278,8 +278,6 @@ if test "$enable_nfsv4" = yes; then
>  	fi
>    fi
>  
> -  AM_CONDITIONAL(CONFIG_NFSDCLD, [test "$enable_nfsdcld" = "yes" ])
> -
>    dnl librpcsecgss already has a dependency on libgssapi,
>    dnl but we need to make sure we get the right version
>    if test "$enable_gss" = yes; then
> @@ -293,6 +291,7 @@ if test "$enable_nfsv41" = yes; then
>  fi
>  
>  dnl enable nfsidmap when its support by libnfsidmap
> +AM_CONDITIONAL(CONFIG_NFSDCLD, [test "$enable_nfsdcld" = "yes" ])
>  AM_CONDITIONAL(CONFIG_NFSIDMAP, [test "$ac_cv_header_keyutils_h$ac_cv_lib_nfsidmap_nfs4_owner_to_uid" = "yesyes"])
>  
>  

Seems to do the right thing. Thanks for fixing this up.

I'll note too that on my machine the build also fails if you
--disable-nfsv4 and --disable-nfsv41, but do not --disable-gss. That's
an entirely separate bug however and has probably been there a long
time.

In any case..

Acked-by: Jeff Layton <jlayton@redhat.com>

  parent reply	other threads:[~2012-05-18 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 23:34 [nfs-utils PATCH] build: avoid AM_CONDITIONAL in conditional execution Diego Elio Pettenò
2012-05-18  0:00 ` Chuck Lever
2012-05-18  0:01   ` Diego Elio Pettenò
2012-05-18  0:03     ` Chuck Lever
2012-05-18 15:05 ` Jeff Layton [this message]
2012-05-29 19:16 ` Steve Dickson

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=20120518110507.75bbc20e@corrin.poochiereds.net \
    --to=jlayton@redhat.com \
    --cc=flameeyes@flameeyes.eu \
    --cc=linux-nfs@vger.kernel.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).