public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Nathan Chancellor <nathan@kernel.org>, kernel test robot <lkp@intel.com>
Cc: Heiko Carstens <hca@linux.ibm.com>,
	llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] Re: llvm-objcopy: error: invalid output format: 'elf64-s390'
Date: Mon, 30 May 2022 16:52:20 +0800	[thread overview]
Message-ID: <fd819888-844f-1a76-fee2-02e89faee090@intel.com> (raw)
In-Reply-To: <YpJMIz/QjDW5IQGr@dev-arch.thelio-3990X>



On 5/29/2022 12:21 AM, Nathan Chancellor wrote:
> On Sun, May 29, 2022 at 12:04:48AM +0800, kernel test robot wrote:
>> Hi Heiko,
>>
>> FYI, the error/warning still remains.
>>
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head:   9d004b2f4fea97cde123e7f1939b80e77bf2e695
>> commit: adda746629b4a3950f313bc645fa0e54daee871c s390/purgatory: workaround llvm's IAS limitations
>> date:   11 days ago
>> config: s390-randconfig-c005-20220527 (https://download.01.org/0day-ci/archive/20220529/202205290045.gOvUOkt3-lkp@intel.com/config)
>> compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 0fbe3f3f486e01448121f7931a4ca29fac1504ab)
>> 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 s390 cross compiling tool for clang build
>>          # apt-get install binutils-s390x-linux-gnu
>>          # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=adda746629b4a3950f313bc645fa0e54daee871c
>>          git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>          git fetch --no-tags linus master
>>          git checkout adda746629b4a3950f313bc645fa0e54daee871c
>>          # save the config file
>>          mkdir build_dir && cp config build_dir/.config
>>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=s390 SHELL=/bin/bash
>>
>> If you fix the issue, kindly add following tag where applicable
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>>>> llvm-objcopy: error: invalid output format: 'elf64-s390'
> 
> This is expected, as llvm-objcopy needs support for s390:
> https://github.com/ClangBuiltLinux/linux/issues/1530
> 
> Please use GNU objcopy for the time being by explicitly providing
> OBJCOPY=${CROSS_COMPILE}objcopy to make.

Hi Nathan,

Thanks for your reminding, will update it.

Best Regards,
Rong Chen

> 
> Cheers,
> Nathan
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org
> 

      reply	other threads:[~2022-05-30  8:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-28 16:04 llvm-objcopy: error: invalid output format: 'elf64-s390' kernel test robot
2022-05-28 16:21 ` Nathan Chancellor
2022-05-30  8:52   ` 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=fd819888-844f-1a76-fee2-02e89faee090@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=hca@linux.ibm.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@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