linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	kernel test robot <lkp@intel.com>,
	Feng Tang <feng.tang@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Masahiro Yamada <masahiroy@kernel.org>,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [kbuild-all] Re: make[2]: *** [arch/powerpc/Makefile.postlink:31: vmlinux] Error 1
Date: Thu, 5 Aug 2021 18:28:26 +0800	[thread overview]
Message-ID: <176ab0a5-72dd-dc24-be64-6919cffba9ed@intel.com> (raw)
In-Reply-To: <c3e9247d-95cd-718c-d8a5-f0cd5e5a3598@infradead.org>



On 8/4/2021 11:10 AM, Randy Dunlap wrote:
> On 7/30/21 1:29 AM, kernel test robot wrote:
>> tree:   
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head:   764a5bc89b12b82c18ce7ca5d7c1b10dd748a440
>> commit: cf536e185869d4815d506e777bcca6edd9966a6e Makefile: extend 32B 
>> aligned debug option to 64B aligned
>> date:   10 weeks ago
>> config: powerpc64-randconfig-c023-20210730 (attached as .config)
>> compiler: powerpc-linux-gcc (GCC) 10.3.0
>> 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
>>          # 
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cf536e185869d4815d506e777bcca6edd9966a6e 
>>
>>          git remote add linus 
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>          git fetch --no-tags linus master
>>          git checkout cf536e185869d4815d506e777bcca6edd9966a6e
>>          # save the attached .config to linux build tree
>>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 
>> make.cross ARCH=powerpc64
>>
>> 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 >>):
>>
>>>> make[2]: *** [arch/powerpc/Makefile.postlink:31: vmlinux] Error 1
>>
>> ---
> 
> Hi ktr/lkp,
> 
> This is not "All errors". I suggest that you improve your output by
> (also) grepping for "ERROR:", so that the following lines would be
> included here:
> 
> ERROR: start_text address is c000000000000200, should be c000000000000100
> ERROR: try to enable LD_HEAD_STUB_CATCH config option
> ERROR: see comments in arch/powerpc/tools/head_check.sh

Hi Randy,

Thanks for the advice, the "ERROR:" lines weren't redirected to stderr, 
so the bot didn't notice them, it looks difficult to change the output.

Best Regards,
Rong Chen

> 
> 
> and yes, enabling LD_HEAD_STUB_CATCH does fix this build error.
> 
> thanks.

  reply	other threads:[~2021-08-05 10:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30  8:29 make[2]: *** [arch/powerpc/Makefile.postlink:31: vmlinux] Error 1 kernel test robot
2021-08-04  3:10 ` Randy Dunlap
2021-08-05 10:28   ` Chen, Rong A [this message]
2021-08-05 19:25     ` [kbuild-all] " Randy Dunlap
2021-08-06 10:30       ` Chen, Rong A

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=176ab0a5-72dd-dc24-be64-6919cffba9ed@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=feng.tang@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=masahiroy@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=rdunlap@infradead.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).