From: Randy Dunlap <rdunlap@infradead.org>
To: kernel test robot <lkp@intel.com>,
Matt Fleming <matt@codeblueprint.co.uk>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: powerpc64-linux-ld: mm/page_alloc.o:undefined reference to `node_reclaim_distance'
Date: Sun, 30 Aug 2020 14:19:34 -0700 [thread overview]
Message-ID: <47426554-9d42-602d-d3fe-b6b38a48b8c6@infradead.org> (raw)
In-Reply-To: <202008310314.JpP8vEJ9%lkp@intel.com>
On 8/30/20 12:32 PM, kernel test robot wrote:
> Hi Matt,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 1127b219ce9481c84edad9711626d856127d5e51
> commit: a55c7454a8c887b226a01d7eed088ccb5374d81e sched/topology: Improve load balancing on AMD EPYC systems
> date: 12 months ago
> config: powerpc64-randconfig-c003-20200831 (attached as .config)
> compiler: powerpc64-linux-gcc (GCC) 9.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
> git checkout a55c7454a8c887b226a01d7eed088ccb5374d81e
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.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 >>):
>
> powerpc64-linux-ld: warning: orphan section `.gnu.hash' from `linker stubs' being placed in section `.gnu.hash'
> powerpc64-linux-ld: arch/powerpc/perf/perf_regs.o: in function `perf_reg_value':
> arch/powerpc/perf/perf_regs.c:80: undefined reference to `.is_sier_available'
>>> powerpc64-linux-ld: mm/page_alloc.o:(.toc+0x0): undefined reference to `node_reclaim_distance'
>
> ---
Build error for undefined "node_reclaim_distance" has been reported on both
arch/sh/ and arch/powerpc64/.
Matt's patch here
https://lore.kernel.org/lkml/20191223164220.GA14394@codeblueprint.co.uk/
fixes the build error in both cases (both $ARCH-es), although it needs to be
resent as a patch instead of "can someone test this?".
Matt?
Acked-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
thanks.
--
~Randy
next prev parent reply other threads:[~2020-08-30 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 19:32 powerpc64-linux-ld: mm/page_alloc.o:undefined reference to `node_reclaim_distance' kernel test robot
2020-08-30 21:19 ` Randy Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-20 8:44 kernel test robot
2020-07-30 11:40 kernel test robot
2020-07-05 13:12 kernel test robot
2020-05-21 4:54 kbuild test robot
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=47426554-9d42-602d-d3fe-b6b38a48b8c6@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@kernel.org \
--cc=peterz@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).