From: kbuild test robot <lkp@intel.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: kbuild-all@01.org, linux-kbuild@vger.kernel.org,
linux-arch@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Arnd Bergmann <arnd@arndb.de>, Nicolas Pitre <nico@linaro.org>,
Alan Modra <amodra@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/5] kbuild: allow architectures to use thin archives instead of ld -r
Date: Sat, 6 Aug 2016 11:50:53 +0800 [thread overview]
Message-ID: <201608061132.dqWg7HVU%fengguang.wu@intel.com> (raw)
In-Reply-To: <1470399123-8455-2-git-send-email-npiggin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5426 bytes --]
Hi Stephen,
[auto build test ERROR on kbuild/for-next]
[also build test ERROR on v4.7]
[cannot apply to linus/master linux/master next-20160805]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Nicholas-Piggin/kbuild-changes-thin-archives-gc-sections/20160805-202258
base: https://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild.git for-next
config: um-allnoconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=um
All errors (new ones prefixed by >>):
init/built-in.o:(.bss+0x4): multiple definition of `reset_devices'
init/built-in.o:(.bss+0x4): first defined here
init/built-in.o: In function `prepare_namespace':
(.init.text+0x988): multiple definition of `prepare_namespace'
init/built-in.o:(.init.text+0x988): first defined here
init/built-in.o:(.init.data+0x1070): multiple definition of `late_time_init'
init/built-in.o:(.init.data+0x1070): first defined here
init/built-in.o: In function `load_default_modules':
(.init.text+0x2f8): multiple definition of `load_default_modules'
init/built-in.o:(.init.text+0x2f8): first defined here
init/built-in.o:(.bss+0x10): multiple definition of `system_state'
init/built-in.o:(.bss+0x10): first defined here
init/built-in.o: In function `mount_root':
(.init.text+0x987): multiple definition of `mount_root'
init/built-in.o:(.init.text+0x987): first defined here
init/built-in.o: In function `mount_block_root':
(.init.text+0x836): multiple definition of `mount_block_root'
init/built-in.o:(.init.text+0x836): first defined here
init/built-in.o:(.bss+0x14): multiple definition of `early_boot_irqs_disabled'
init/built-in.o:(.bss+0x14): first defined here
init/built-in.o:(.data+0x0): multiple definition of `loops_per_jiffy'
init/built-in.o:(.data+0x0): first defined here
init/built-in.o:(.bss+0xc): multiple definition of `saved_command_line'
init/built-in.o:(.bss+0xc): first defined here
init/built-in.o: In function `calibrate_delay':
(.text+0x2e0): multiple definition of `calibrate_delay'
init/built-in.o:(.text+0x2e0): first defined here
init/built-in.o: In function `do_one_initcall':
(.init.text+0x57a): multiple definition of `do_one_initcall'
init/built-in.o:(.init.text+0x57a): first defined here
init/built-in.o:(.rodata+0x20): multiple definition of `linux_proc_banner'
init/built-in.o:(.rodata+0x20): first defined here
init/built-in.o:(.init.data+0x20e4): multiple definition of `rd_doload'
init/built-in.o:(.init.data+0x20e4): first defined here
init/built-in.o:(.data+0x620): multiple definition of `init_task'
init/built-in.o:(.data+0x620): first defined here
init/built-in.o:(.data+0x460): multiple definition of `init_uts_ns'
init/built-in.o:(.data+0x460): first defined here
init/built-in.o:(.data+0x20): multiple definition of `envp_init'
init/built-in.o:(.data+0x20): first defined here
init/built-in.o: In function `name_to_dev_t':
(.text+0x70): multiple definition of `name_to_dev_t'
init/built-in.o:(.text+0x70): first defined here
init/built-in.o:(.data+0x618): multiple definition of `root_mountflags'
init/built-in.o:(.data+0x618): first defined here
init/built-in.o:(.bss+0x8): multiple definition of `static_key_initialized'
init/built-in.o:(.bss+0x8): first defined here
init/built-in.o: In function `start_kernel':
(.init.text+0x351): multiple definition of `start_kernel'
init/built-in.o:(.init.text+0x351): first defined here
>> init/built-in.o:(.bss+0x30): multiple definition of `Version_263936'
init/built-in.o:(.bss+0x30): first defined here
init/built-in.o: In function `parse_early_options':
(.init.text+0x2f9): multiple definition of `parse_early_options'
init/built-in.o:(.init.text+0x2f9): first defined here
init/built-in.o: In function `parse_early_param':
(.init.text+0x31a): multiple definition of `parse_early_param'
init/built-in.o:(.init.text+0x31a): first defined here
init/built-in.o:(.bss+0x40): multiple definition of `preset_lpj'
init/built-in.o:(.bss+0x40): first defined here
init/built-in.o:(.data..init_task+0x0): multiple definition of `init_thread_union'
init/built-in.o:(.data..init_task+0x0): first defined here
init/built-in.o: In function `init_rootfs':
(.init.text+0x80a): multiple definition of `init_rootfs'
init/built-in.o:(.init.text+0x80a): first defined here
init/built-in.o:(.rodata+0x80): multiple definition of `linux_banner'
init/built-in.o:(.rodata+0x80): first defined here
init/built-in.o:(.bss+0x34): multiple definition of `ROOT_DEV'
init/built-in.o:(.bss+0x34): first defined here
init/built-in.o:(.bss+0x0): multiple definition of `initcall_debug'
init/built-in.o:(.bss+0x0): first defined here
init/built-in.o:(.init.data+0x1080): multiple definition of `boot_command_line'
init/built-in.o:(.init.data+0x1080): first defined here
init/built-in.o:(.bss+0x44): multiple definition of `lpj_fine'
init/built-in.o:(.bss+0x44): first defined here
collect2: error: ld returned 1 exit status
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 3843 bytes --]
next prev parent reply other threads:[~2016-08-06 3:51 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 12:11 [RFC][PATCH 0/5] kbuild changes, thin archives, --gc-sections Nicholas Piggin
2016-08-05 12:11 ` [PATCH 1/5] kbuild: allow architectures to use thin archives instead of ld -r Nicholas Piggin
2016-08-06 3:50 ` kbuild test robot [this message]
2016-08-06 20:10 ` Sam Ravnborg
2016-08-07 1:49 ` Stephen Rothwell
2016-08-07 3:34 ` Alan Modra
2016-08-07 4:17 ` Nicolas Pitre
2016-08-07 14:40 ` Sam Ravnborg
2016-08-08 3:19 ` Nicholas Piggin
2016-08-08 4:46 ` Sam Ravnborg
2016-08-08 3:25 ` Nicholas Piggin
2016-08-08 9:18 ` Arnd Bergmann
2016-08-05 12:12 ` [PATCH 2/5] kbuild: allow archs to select build for link dead code/data elimination Nicholas Piggin
2016-08-06 20:14 ` Sam Ravnborg
2016-08-08 3:29 ` Nicholas Piggin
2016-08-08 4:49 ` Sam Ravnborg
2016-08-07 5:33 ` Nicolas Pitre
2016-08-08 3:42 ` Nicholas Piggin
2016-08-08 4:12 ` Nicolas Pitre
2016-08-08 4:27 ` Nicholas Piggin
2016-08-07 9:57 ` Alan Modra
2016-08-07 11:35 ` Andreas Schwab
2016-08-07 20:26 ` Arnd Bergmann
2016-08-07 23:49 ` Alan Modra
2016-08-08 15:14 ` Arnd Bergmann
2016-08-08 23:50 ` Alan Modra
2016-08-09 22:10 ` Arnd Bergmann
2016-08-09 3:16 ` Andi Kleen
2016-08-09 22:29 ` Arnd Bergmann
2016-08-09 23:08 ` Andi Kleen
2016-08-10 0:37 ` Andi Kleen
2016-08-05 12:12 ` [PATCH 3/5] kbuild: add arch specific post-module-link pass Nicholas Piggin
2016-08-05 13:56 ` Nicholas Piggin
2016-08-06 20:16 ` Sam Ravnborg
2016-08-08 3:30 ` Nicholas Piggin
2016-08-05 12:12 ` [PATCH 4/5] powerpc: switch to using thin archives Nicholas Piggin
2016-08-05 12:12 ` [PATCH 5/5] powerpc/64: use linker dce Nicholas Piggin
2016-08-05 13:32 ` [RFC][PATCH 0/5] kbuild changes, thin archives, --gc-sections Nicholas Piggin
2016-08-07 20:23 ` Arnd Bergmann
2016-08-08 3:53 ` Nicholas Piggin
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=201608061132.dqWg7HVU%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=amodra@gmail.com \
--cc=arnd@arndb.de \
--cc=kbuild-all@01.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nico@linaro.org \
--cc=npiggin@gmail.com \
--cc=sfr@canb.auug.org.au \
/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).