All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Richard Weinberger <richard@nod.at>
Subject: (*ABS*+0xbb29b267): multiple definition of `__crc___gcov_merge_add'
Date: Sun, 22 Oct 2017 12:02:26 +0800	[thread overview]
Message-ID: <201710221224.VEHWtqs3%fengguang.wu@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 984 bytes --]

Hi Thomas,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   0787643a5f6aad1f0cdeb305f7fe492b71943ea4
commit: d3488649dcd23b7a6e63895274ec69f80e92d4ed um: Fix CONFIG_GCOV for modules.
date:   5 weeks ago
config: um-allyesconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        git checkout d3488649dcd23b7a6e63895274ec69f80e92d4ed
        # save the attached .config to linux build tree
        make ARCH=um 

All errors (new ones prefixed by >>):

   kernel/gcov/base.o: In function `__crc___gcov_merge_add':
>> (*ABS*+0xbb29b267): multiple definition of `__crc___gcov_merge_add'
   kernel/gcov/base.o: In function `__crc___gcov_init':
>> (*ABS*+0xdceb3072): multiple definition of `__crc___gcov_init'

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 19505 bytes --]

             reply	other threads:[~2017-10-22  4:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-22  4:02 kbuild test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-15  6:49 (*ABS*+0xbb29b267): multiple definition of `__crc___gcov_merge_add' kbuild test robot
2017-09-24  6:42 kbuild test robot
2017-09-24  7:50 ` Richard Weinberger
2017-09-17 18:52 kbuild test robot
2017-09-18 16:32 ` Thomas Meyer

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=201710221224.VEHWtqs3%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@nod.at \
    --cc=thomas@m3y3r.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.