mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Ulf Magnusson <ulfalizer@gmail.com>
Subject: Kconfig:12: can't open file "arch/powerpc64/Kconfig"
Date: Sun, 11 Feb 2018 11:41:15 +0800	[thread overview]
Message-ID: <201802111111.M5DJTfR5%fengguang.wu@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   d48fcbd864a008802a90c58a9ceddd9436d11a49
commit: 9e3e10c725360b9d07018cfcd5b7b6b7d325fae5 kconfig: send error messages to stderr
date:   2 days ago
config: powerpc64-defconfig
compiler: powerpc64-linux-gcc (GCC) 7.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 9e3e10c725360b9d07018cfcd5b7b6b7d325fae5
        make.cross ARCH=powerpc64  defconfig
        make.cross ARCH=powerpc64 

All errors (new ones prefixed by >>):

   Makefile:499: arch/powerpc64/Makefile: No such file or directory
   make[1]: *** No rule to make target 'arch/powerpc64/Makefile'.
   make[1]: Failed to remake makefile 'arch/powerpc64/Makefile'.
>> Kconfig:12: can't open file "arch/powerpc64/Kconfig"
   make[2]: *** [defconfig] Error 1
   make[1]: *** [defconfig] Error 2
   make: *** [sub-make] Error 2
--
   Makefile:499: arch/powerpc64/Makefile: No such file or directory
   make[1]: *** No rule to make target 'arch/powerpc64/Makefile'.
   make[1]: Failed to remake makefile 'arch/powerpc64/Makefile'.
>> Kconfig:12: can't open file "arch/powerpc64/Kconfig"
   make[2]: *** [oldconfig] Error 1
   make[1]: *** [oldconfig] Error 2
   make: *** [sub-make] Error 2
--
   Makefile:499: arch/powerpc64/Makefile: No such file or directory
   make[1]: *** No rule to make target 'arch/powerpc64/Makefile'.
   make[1]: Failed to remake makefile 'arch/powerpc64/Makefile'.
>> Kconfig:12: can't open file "arch/powerpc64/Kconfig"
   make[2]: *** [olddefconfig] Error 1
   make[2]: Target 'oldnoconfig' not remade because of errors.
   make[1]: *** [oldnoconfig] Error 2
   make: *** [sub-make] Error 2

vim +12 Kconfig

838a2e55 Arnaud Lacombe 2010-09-04   7  
838a2e55 Arnaud Lacombe 2010-09-04   8  config SRCARCH
838a2e55 Arnaud Lacombe 2010-09-04   9  	string
838a2e55 Arnaud Lacombe 2010-09-04  10  	option env="SRCARCH"
838a2e55 Arnaud Lacombe 2010-09-04  11  
838a2e55 Arnaud Lacombe 2010-09-04 @12  source "arch/$SRCARCH/Kconfig"

:::::: The code at line 12 was first introduced by commit
:::::: 838a2e55e6a4e9e8a10451ed2ef0f7a08dabdb04 kbuild: migrate all arch to the kconfig mainmenu upgrade

:::::: TO: Arnaud Lacombe <lacombar@gmail.com>
:::::: CC: Arnaud Lacombe <lacombar@gmail.com>

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

             reply	other threads:[~2018-02-11  3:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-11  3:41 kbuild test robot [this message]
2018-02-11  4:07 ` Masahiro Yamada
2018-02-11  9:16   ` 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=201802111111.M5DJTfR5%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ulfalizer@gmail.com \
    --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

all inboxes | Powered by JetHome®