public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Luis Chamberlain <mcgrof@kernel.org>, kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>
Subject: Re: [kbuild-all] Re: [mcgrof-next:20210916-firmware-builtin-v2 14/14] drivers/base/firmware_loader/test-builtin/test-builtin-firmware.bin.gen.S:5:13: error: Could not find incbin file 'drivers/base/firmware_loader/test-builtin/test-builtin-firmware.bin'
Date: Thu, 11 Nov 2021 17:07:07 +0800	[thread overview]
Message-ID: <a822ee1e-a9a2-7208-3d7d-61239c0da695@intel.com> (raw)
In-Reply-To: <YYlVhm0ybuirMI//@bombadil.infradead.org>



On 11/9/2021 12:51 AM, Luis Chamberlain wrote:
> On Mon, Nov 08, 2021 at 01:37:31AM +0800, kernel test robot wrote:
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git 20210916-firmware-builtin-v2
>> head:   f69194f4bcf5b301f2d169b2f036c0da4b642e53
>> commit: f69194f4bcf5b301f2d169b2f036c0da4b642e53 [14/14] test_firmware: add support for testing built-in firmware
>> config: arm-randconfig-r004-20210929 (attached as .config)
>> compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project dc6e8dfdfe7efecfda318d43a06fae18b40eb498)
>> reproduce (this is a W=1 build):
>>          wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>>          chmod +x ~/bin/make.cross
>>          # install arm cross compiling tool for clang build
>>          # apt-get install binutils-arm-linux-gnueabi
>>          # https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git/commit/?id=f69194f4bcf5b301f2d169b2f036c0da4b642e53
>>          git remote add mcgrof-next https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git
>>          git fetch --no-tags mcgrof-next 20210916-firmware-builtin-v2
>>          git checkout f69194f4bcf5b301f2d169b2f036c0da4b642e53
>>          # save the attached .config to linux build tree
>>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=arm
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>>>> drivers/base/firmware_loader/test-builtin/test-builtin-firmware.bin.gen.S:5:13: error: Could not find incbin file 'drivers/base/firmware_loader/test-builtin/test-builtin-firmware.bin'
>>         .incbin "drivers/base/firmware_loader/test-builtin/test-builtin-firmware.bin"
>>                 ^
> 
> I used the latest test branch:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git/log/?h=20211020-firmware-builtin
> 
> And I can't reproduce there, that build fails for another reason though:

Hi Luis,

Sorry for the inconvenience, the reproduce step is not accurate,
we can be reproduced the error with "O=dir" option specified.

Best Regards,
Rong Chen

> 
> ld.lld: error: undefined symbol: _printk
>>>> referenced by io-acorn.o:(.text+0x38) in archive
>>>> arch/arm/mach-rpc/built-in.a
> make: *** [Makefile:1183: vmlinux] Error 1
> make: Target '__all' not remade because of errors.
> 
>    Luis
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org
> 

      reply	other threads:[~2021-11-11  9:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-07 17:37 [mcgrof-next:20210916-firmware-builtin-v2 14/14] drivers/base/firmware_loader/test-builtin/test-builtin-firmware.bin.gen.S:5:13: error: Could not find incbin file 'drivers/base/firmware_loader/test-builtin/test-builtin-firmware.bin' kernel test robot
2021-11-08 16:51 ` Luis Chamberlain
2021-11-11  9:07   ` Chen, Rong A [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=a822ee1e-a9a2-7208-3d7d-61239c0da695@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=bp@suse.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=mcgrof@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