linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Rong Chen <rong.a.chen@intel.com>, kbuild test robot <lkp@intel.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [kbuild-all] [mmotm:master 19/222] arch/sh/kernel/cpu/sh2/clock-sh7619.o:undefined reference to `followparent_recalc'
Date: Wed, 3 Apr 2019 07:46:16 -0700	[thread overview]
Message-ID: <38dbc113-2b1c-3fe6-ba37-36f89bbb71c4@infradead.org> (raw)
In-Reply-To: <44789370-4ca9-329f-65ad-8ff428a7e91b@intel.com>

On 4/3/19 12:09 AM, Rong Chen wrote:
> 
> On 4/3/19 2:26 PM, Randy Dunlap wrote:
>> On 4/2/19 10:54 PM, kbuild test robot wrote:
>>> Hi Randy,
>>>
>>> It's probably a bug fix that unveils the link errors.
>>>
>>> tree:   git://git.cmpxchg.org/linux-mmotm.git master
>>> head:   03590d39c08e0f2969871a5efcf27a366c1e8c60
>>> commit: cffa367bb8abe4c1424e93e345c7d63844d1c5db [19/222] sh: fix multiple function definition build errors
>>> config: sh-allmodconfig (attached as .config)
>>> compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
>>> reproduce:
>>>          wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>>>          chmod +x ~/bin/make.cross
>>>          git checkout cffa367bb8abe4c1424e93e345c7d63844d1c5db
>>>          # save the attached .config to linux build tree
>>>          GCC_VERSION=7.2.0 make.cross ARCH=sh
>>>
>>> All errors (new ones prefixed by >>):
>>>
>>>>> arch/sh/kernel/cpu/sh2/clock-sh7619.o:(.data+0x1c): undefined reference to `followparent_recalc'
>>> ---
>>> 0-DAY kernel test infrastructure                Open Source Technology Center
>>> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
>>>
>> Hi,
>> I suspect that it's more of an invalid .config file.
>> How do you generate the .config files?  or is it a defconfig?
> 
> the config file was generated by "make ARCH=sh allmodconfig"
> 
> 
>>
>> Yes, I have seen this build error, but I was able to get around it
>> by modifying the .config file.  That's why I suspect that it may be
>> an invalid .config file.
> 
> Can you share the fix steps? We'll take a look at it.

Hi,

For this build error:
>> arch/sh/kernel/cpu/sh2/clock-sh7619.o:(.data+0x1c): undefined reference to `followparent_recalc'

the problem is with CONFIG_COMMON_CLK.  The COMMON_CLK framework does not
provide this API.  However, in arch/sh/boards/Kconfig, COMMON_CLK is always
selected by SH_DEVICE_TREE.  By disabling SH_DEVICE_TREE, the build
succeeds.


-- 
~Randy


  reply	other threads:[~2019-04-03 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03  5:54 kbuild test robot
2019-04-03  6:26 ` Randy Dunlap
2019-04-03  7:09   ` [kbuild-all] " Rong Chen
2019-04-03 14:46     ` Randy Dunlap [this message]
2019-04-04  0:20       ` Rong Chen
2019-04-04  0:39         ` Randy Dunlap

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=38dbc113-2b1c-3fe6-ba37-36f89bbb71c4@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=rong.a.chen@intel.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