linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Andrey Ryabinin <a.ryabinin@samsung.com>,
	kbuild-all@01.org, Ben Hutchings <bwh@kernel.org>,
	Andrey Konovalov <adech.fo@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable <stable@vger.kernel.org>
Subject: Re: [linux-stable-rc:linux-3.16.y 2872/3488] head64.c:undefined reference to `__gcov_exit'
Date: Fri, 16 Feb 2018 21:28:17 +0100	[thread overview]
Message-ID: <CAK8P3a1E4=NJaZKM0z8b62ahSoBjR1K2oLsHhbY9C03Kkeeu8g@mail.gmail.com> (raw)
In-Reply-To: <201802170216.gfRZgPtX%fengguang.wu@intel.com>

On Fri, Feb 16, 2018 at 7:21 PM, kbuild test robot
<fengguang.wu@intel.com> wrote:
> Hi Andrey,
>
> It's probably a bug fix that unveils the link errors.
>
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-3.16.y
> head:   0b9f4cdd4d75131d8886b919bbf6e0c98906d36e
> commit: 3cb0dc19883f0c69225311d4f76aa8128d3681a4 [2872/3488] module: fix types of device tables aliases
> config: x86_64-allmodconfig (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
>         git checkout 3cb0dc19883f0c69225311d4f76aa8128d3681a4
>         # save the attached .config to linux build tree
>         make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
>    arch/x86/kernel/head64.o: In function `_GLOBAL__sub_D_00100_1_early_pmd_flags':
>>> head64.c:(.text.exit+0x5): undefined reference to `__gcov_exit'
>    arch/x86/kernel/head.o: In function `_GLOBAL__sub_D_00100_1_reserve_ebda_region':
>    head.c:(.text.exit+0x5): undefined reference to `__gcov_exit'
>    init/built-in.o: In function `_GLOBAL__sub_D_00100_1___ksymtab_system_state':
>    main.c:(.text.exit+0x5): undefined reference to `__gcov_exit'
>    init/built-in.o: In function `_GLOBAL__sub_D_00100_1_root_mountflags':
>    do_mounts.c:(.text.exit+0x10): undefined reference to `__gcov_exit'
>    init/built-in.o: In function `_GLOBAL__sub_D_00100_1_initrd_load':
>    do_mounts_initrd.c:(.text.exit+0x1b): undefined reference to `__gcov_exit'
>    init/built-in.o:initramfs.c:(.text.exit+0x26): more undefined references to `__gcov_exit' follow

I think this is a result of using a too new compiler with the old 3.16
kernel. In order
to build with gcc-7.3, you need to backport

05384213436a ("gcov: support GCC 7.1")

It's already part of stable-3.18 and later, but not 3.2 and 3.16.

      Arnd

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2018-02-16 20:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 18:21 kbuild test robot
2018-02-16 20:28 ` Arnd Bergmann [this message]
2018-11-11  1:38   ` Ben Hutchings

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='CAK8P3a1E4=NJaZKM0z8b62ahSoBjR1K2oLsHhbY9C03Kkeeu8g@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=a.ryabinin@samsung.com \
    --cc=adech.fo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bwh@kernel.org \
    --cc=fengguang.wu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    --cc=stable@vger.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