From: Philip Li <philip.li@intel.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: kbuild test robot <lkp@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Sam Ravnborg <sam@ravnborg.org>,
kbuild-all@01.org,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [kbuild-all] [PATCH v2 1/3] kbuild: use 'include' directive to load auto.conf from top Makefile
Date: Sun, 24 Jun 2018 18:35:16 +0800 [thread overview]
Message-ID: <20180624103516.GA29697@intel.com> (raw)
In-Reply-To: <CAK7LNARv7VyPaew6XpRiYqh1YTapj-oErGuiq4rS1_BmEjC8Lw@mail.gmail.com>
On Sun, Jun 24, 2018 at 05:56:24PM +0900, Masahiro Yamada wrote:
> Hi.
>
> 2018-06-24 3:59 GMT+09:00 kbuild test robot <lkp@intel.com>:
> > Hi Masahiro,
> >
> > I love your patch! Yet something to improve:
> >
> > [auto build test ERROR on kbuild/for-next]
> > [also build test ERROR on v4.18-rc1 next-20180622]
> > [cannot apply to mmarek/for-next mmarek/rc-fixes]
> > [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/Masahiro-Yamada/kbuild-use-include-directive-to-load-auto-conf-from-top-Makefile/20180623-220114
> > base: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git for-next
> > config: xtensa-nommu_kc705_defconfig (attached as .config)
> > compiler: xtensa-de212-elf-gcc (crosstool-NG crosstool-ng-1.23.0-307-g452ee331) 7.3.0
> > reproduce:
> > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > # save the attached .config to linux build tree
> > GCC_VERSION=7.3.0 make.cross ARCH=xtensa
>
> This did not work for me
> because the make.cross script tries to download GCC 7.3.0 xtensa-linux
> but it is missing in the web site.
>
> $ GCC_VERSION=7.3.0 make.cross ARCH=xtensa
> Cannot find xtensa-linux under
> https://download.01.org/0day-ci/cross-package check
> /tmp/crosstool-files
thanks for info, we will fix it as early as possible, and
reproduce the issue to provide feedback later.
>
>
> I installed xtensa-de212-elf-gcc by hand,
> but I could not reproduce the error.
>
>
> GCC_VERSION=7.2.0 make.cross ARCH=xtensa
> worked, but I could not reproduce the issue either.
> (the build terminated with a different error.)
>
>
> Where can I see the full build log?
>
>
> > All errors (new ones prefixed by >>):
> >
> >>> Makefile:592: include/config/auto.conf: No such file or directory
> > drivers/staging/mt7621-dts/Kconfig:4:warning: 'BUILTIN_DTB' has wrong type. 'select' only accept arguments of bool and tristate type
> > <stdin>:1332:2: warning: #warning syscall io_pgetevents not implemented [-Wcpp]
> > <stdin>:1335:2: warning: #warning syscall rseq not implemented [-Wcpp]
> >
> > vim +592 Makefile
> >
> > 590
> > 591 ifeq ($(dot-config),1)
> > > 592 include include/config/auto.conf
> > 593 endif
> > 594
> >
> > ---
> > 0-DAY kernel test infrastructure Open Source Technology Center
> > https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
>
>
> --
> Best Regards
> Masahiro Yamada
> _______________________________________________
> kbuild-all mailing list
> kbuild-all@lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all
next prev parent reply other threads:[~2018-06-24 10:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 13:56 [PATCH v2 1/3] kbuild: use 'include' directive to load auto.conf from top Makefile Masahiro Yamada
2018-06-23 13:56 ` [PATCH v2 2/3] kbuild: do not update config when running install targets Masahiro Yamada
2018-06-23 13:56 ` [PATCH v2 3/3] kbuild: do not update config for 'make kernelrelease' Masahiro Yamada
2018-06-23 18:59 ` [PATCH v2 1/3] kbuild: use 'include' directive to load auto.conf from top Makefile kbuild test robot
2018-06-24 8:56 ` Masahiro Yamada
2018-06-24 10:35 ` Philip Li [this message]
2018-06-28 13:39 ` Masahiro Yamada
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=20180624103516.GA29697@intel.com \
--to=philip.li@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=michal.lkml@markovi.net \
--cc=sam@ravnborg.org \
--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