linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: kbuild-all@01.org, LKML <linux-kernel@vger.kernel.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Michal Marek <michal.lkml@markovi.net>,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kbuild: Fail the build early when no lz4 present
Date: Fri, 12 Oct 2018 04:33:54 +0800	[thread overview]
Message-ID: <201810120448.uX17jxBY%fengguang.wu@intel.com> (raw)
In-Reply-To: <20181010222333.17794-1-bp@alien8.de>

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

Hi Borislav,

I love your patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v4.19-rc7 next-20181011]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Borislav-Petkov/kbuild-Fail-the-build-early-when-no-lz4-present/20181012-013752
config: i386-randconfig-b0-10112221 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

>> Makefile:793: *** "lz4 tool not found on this system but CONFIG_KERNEL_LZ4 enabled".  Stop.
   make: *** [sub-make] Error 2

vim +793 Makefile

   790	
   791	ifdef CONFIG_KERNEL_LZ4
   792	ifeq ($(CONFIG_SHELL which lz4c),)
 > 793	$(error "lz4 tool not found on this system but CONFIG_KERNEL_LZ4 enabled")
   794	endif
   795	endif
   796	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31850 bytes --]

      parent reply	other threads:[~2018-10-11 20:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 22:23 [PATCH] kbuild: Fail the build early when no lz4 present Borislav Petkov
2018-10-10 22:34 ` Randy Dunlap
2018-10-11  4:26 ` Masahiro Yamada
2018-10-11  8:52   ` Borislav Petkov
2018-10-11 15:08     ` Masahiro Yamada
2018-10-11 15:32       ` Borislav Petkov
2018-10-16  9:17         ` Masahiro Yamada
2018-10-11 20:33 ` kbuild test robot [this message]

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=201810120448.uX17jxBY%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=bp@alien8.de \
    --cc=kbuild-all@01.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=yamada.masahiro@socionext.com \
    /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).