From: Dan Williams <dan.j.williams@intel.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Johannes Thumshirn <jthumshirn@suse.de>
Subject: Re: make[2]: *** No rule to make target 'tools/testing/nvdimm//config_check.o', needed by 'tools/testing/nvdimm//dax.o'.
Date: Mon, 15 Aug 2016 17:58:36 -0700 [thread overview]
Message-ID: <CAPcyv4jpd++7ALjfp7Ci24cCTC9g93J_DOGUO8LbtwSQ5ex3Tw@mail.gmail.com> (raw)
In-Reply-To: <201608151849.0GQ0EGLP%fengguang.wu@intel.com>
On Mon, Aug 15, 2016 at 3:03 AM, kbuild test robot
<fengguang.wu@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 694d0d0bb2030d2e36df73e2d23d5770511dbc8d
> commit: ab68f26221366f92611650e8470e6a926801c7d4 /dev/dax, pmem: direct access to persistent memory
> date: 3 months ago
> config: i386-randconfig-i1-201633 (attached as .config)
> compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4
> reproduce:
> git checkout ab68f26221366f92611650e8470e6a926801c7d4
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
>>> make[2]: *** No rule to make target 'tools/testing/nvdimm//config_check.o', needed by 'tools/testing/nvdimm//dax.o'.
> make[2]: Target '__build' not remade because of errors.
I think this is an invalid build test. tools/testing/nvdimm/ uses a
external module Kbuild environment, not Kconfig. So, there's nothing
I can do to prevent this compile error, unless there's some other way
0-day could determine the configuration dependencies?
next prev parent reply other threads:[~2016-08-16 0:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 10:03 make[2]: *** No rule to make target 'tools/testing/nvdimm//config_check.o', needed by 'tools/testing/nvdimm//dax.o' kbuild test robot
2016-08-16 0:58 ` Dan Williams [this message]
2016-08-16 1:26 ` [kbuild-all] " Fengguang Wu
2016-08-16 1:30 ` Dan Williams
2016-08-16 1:36 ` Fengguang Wu
2016-08-16 1:41 ` Fengguang Wu
2016-08-16 1:47 ` Yilong Ren
2016-08-16 1:58 ` Fengguang Wu
2016-08-16 2:19 ` Yilong Ren
2016-08-16 2:30 ` Fengguang Wu
2016-08-16 2:33 ` Yilong Ren
2016-08-16 1:48 ` Dan Williams
2016-08-16 1:41 ` Yilong Ren
2016-08-22 12:26 ` Yilong Ren
2016-08-23 23:42 ` Dan Williams
2016-08-24 2:47 ` Fengguang Wu
2016-08-24 14:59 ` Dan Williams
2016-08-25 0:09 ` Fengguang Wu
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=CAPcyv4jpd++7ALjfp7Ci24cCTC9g93J_DOGUO8LbtwSQ5ex3Tw@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=fengguang.wu@intel.com \
--cc=jthumshirn@suse.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@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).