From: Guenter Roeck <linux@roeck-us.net>
To: Nicholas Piggin <npiggin@gmail.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Build failure in -next due to 'sh: thin archives fix linking'
Date: Wed, 28 Jun 2017 05:38:50 -0700 [thread overview]
Message-ID: <77ef6224-28f6-d71d-29d8-74b41fa26f0b@roeck-us.net> (raw)
Hi,
I see the following build error in -next when building sh:rts7751r2dplus_defconfig.
sh4-linux-ld: arch/sh/kernel/vsyscall/vsyscall-dummy.o: compiled for a big endian system and target is little endian
sh4-linux-ld: arch/sh/kernel/vsyscall/vsyscall-dummy.o: uses instructions which are incompatible with instructions used in previous modules
sh4-linux-ld: failed to merge target specific data of file arch/sh/kernel/vsyscall/vsyscall-dummy.o
make[2]: *** [arch/sh/kernel/vsyscall/vsyscall-syms.o] Error 1
Bisect points to 'sh: thin archives fix linking' as the culprit. Bisect log is attached.
I tried with gcc 4.8.3 and 6.3.0, both built with buildroot for sh4eb.
After reverting the offending patch, I get the following error.
arch/sh/kernel/signal_32.o: In function `do_signal':
signal_32.c:(.text+0x5c4): undefined reference to `__kernel_sigreturn'
signal_32.c:(.text+0x724): undefined reference to `__kernel_rt_sigreturn'
Makefile:989: recipe for target 'vmlinux' failed
Guenter
---
# bad: [89a39f3c7086301342175c461c4db43c68d34cc7] Add linux-next specific files for 20170627
# good: [c0bc126f97fb929b3ae02c1c62322645d70eb408] Linux 4.12-rc7
git bisect start 'HEAD' 'v4.12-rc7'
# bad: [32e240e33387e1c3dcf302518d4420e7f19d51e2] Merge remote-tracking branch 'crypto/master'
git bisect bad 32e240e33387e1c3dcf302518d4420e7f19d51e2
# bad: [5fa6b60a63a80c0d1adc4a7d2478fc7d22593493] Merge remote-tracking branch 'printk/for-next'
git bisect bad 5fa6b60a63a80c0d1adc4a7d2478fc7d22593493
# bad: [99f4c8ff2a80c7c39dfd5558bda9f125313fc7ef] Merge remote-tracking branch 'arm-soc/for-next'
git bisect bad 99f4c8ff2a80c7c39dfd5558bda9f125313fc7ef
# good: [fff3affce6cd166063a56528e42eaf16c6a901b8] Merge branch 'next/dt' into for-next
git bisect good fff3affce6cd166063a56528e42eaf16c6a901b8
# good: [88ad71aab1a7931ac3d35c3acaa431c3dc05afd9] [media] vimc: sen: Support several image formats
git bisect good 88ad71aab1a7931ac3d35c3acaa431c3dc05afd9
# bad: [2bbc45806045b005f6a0f6db22a341f52622aca8] Merge remote-tracking branch 'asm-generic/master'
git bisect bad 2bbc45806045b005f6a0f6db22a341f52622aca8
# bad: [fd47ada97a68d8be20dbdc115343f9d51bdf3714] Merge remote-tracking branch 'kbuild/for-next'
git bisect bad fd47ada97a68d8be20dbdc115343f9d51bdf3714
# good: [1887a40b8699a8bde4a0b2883a1381c0a6e119e6] Merge remote-tracking branch 'net/master'
git bisect good 1887a40b8699a8bde4a0b2883a1381c0a6e119e6
# bad: [39be5eac380dabc761c47358cdf8036bb5090f6b] Merge branches 'misc', 'kbuild' and 'thin-ar' into for-next
git bisect bad 39be5eac380dabc761c47358cdf8036bb5090f6b
# bad: [e7238f4fac14967bba823ef4b4b77ee928a4860a] kbuild: thin archives make default for all archs
git bisect bad e7238f4fac14967bba823ef4b4b77ee928a4860a
# good: [9fc5b7bc3c905ad207f21e8478659f4b935407c4] kbuild: handle libs-y archives separately from built-in.o archives
git bisect good 9fc5b7bc3c905ad207f21e8478659f4b935407c4
# bad: [11690a748f62365890a9a9f9abf56ada9b7d5c40] ia64: thin archives fix linking
git bisect bad 11690a748f62365890a9a9f9abf56ada9b7d5c40
# bad: [e2c99c9125c39eb43960da79f5691126b55d4b6c] sh: thin archives fix linking
git bisect bad e2c99c9125c39eb43960da79f5691126b55d4b6c
# first bad commit: [e2c99c9125c39eb43960da79f5691126b55d4b6c] sh: thin archives fix linking
next reply other threads:[~2017-06-28 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 12:38 Guenter Roeck [this message]
2017-06-28 12:58 ` Nicholas Piggin
2017-06-28 14:02 ` Guenter Roeck
2017-06-29 15:36 ` Masahiro Yamada
2017-06-29 16:58 ` 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=77ef6224-28f6-d71d-29d8-74b41fa26f0b@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®