linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] make: don't spray static check failures all over the subdir build
Date: Fri, 9 Nov 2018 13:34:44 -0600	[thread overview]
Message-ID: <267751ec-88d1-cdbb-a6f2-74d6b8b437da@redhat.com> (raw)
In-Reply-To: <20181109192822.GF15721@magnolia>

On 11/9/18 1:28 PM, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
> 
> Debian package building is special -- it directly calls make -C libxfs
> when building the debian-installer packages.  This means that any
> variables we define in the top level Makefile don't get passed down to
> subdir make processes.
> 
> This means that the new static checker support effectively runs the
> first argument in $(CFLAGS) as a command, which is surprising.  Fix up
> buildrules to patch out CHECK_CMD if nobody's defined it, so that direct
> subdir make works again.
> 
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
>  include/buildrules |    4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/include/buildrules b/include/buildrules
> index 83dfe05b..5c3e6eb9 100644
> --- a/include/buildrules
> +++ b/include/buildrules
> @@ -36,6 +36,10 @@ $(SUBDIRS):
>  	$(Q)$(MAKE) $(MAKEOPTS) -q -C $@ || $(MAKE) $(MAKEOPTS) -C $@
>  endif
>  
> +ifndef CHECK_CMD
> +CHECK_CMD = @true
> +endif
> +

Hm, ok, not quite clear if this is a hack or a proper fix - maybe
all the check stuff should have gone into buildrules in the first
place?  But at this late stage in the game, it's probably good enough.

Reviewed-by: Eric Sandeen <sandeen@redhat.com>

Thanks,
-eric

  reply	other threads:[~2018-11-10  5:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 19:28 [PATCH] make: don't spray static check failures all over the subdir build Darrick J. Wong
2018-11-09 19:34 ` Eric Sandeen [this message]
2018-11-09 19:50   ` Darrick J. Wong

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=267751ec-88d1-cdbb-a6f2-74d6b8b437da@redhat.com \
    --to=sandeen@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@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).