From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org
Cc: mark.rutland@arm.com, catalin.marinas@arm.com,
keescook@chromium.org, ardb@kernel.org, nathan@kernel.org
Subject: allmodconfig builds failing to link on arm64
Date: Fri, 8 Apr 2022 12:54:07 +0100 [thread overview]
Message-ID: <20220408115407.GA27685@willie-the-truck> (raw)
Hi folks,
Since -rc1 (although I haven't tried bisecting the merge window), I'm
not able to link allmodconfig for arm64:
aarch64-linux-gnu-ld: .init.data has both ordered [`__patchable_function_entries' in init/main.o] and unordered [`.init_array.1' in virt/lib/irqbypass.o] sections
aarch64-linux-gnu-ld: final link failed: bad value
make: *** [Makefile:1158: vmlinux] Error 1
I'm using an Android clang based on 12.0.6 and LD claims to be
2.33.1.20191209.
Is anybody else having problems? The linker error is useless enough that I
haven't found time to dig any further into it and the build robots haven't
reported any failures to my knowledge. The only similar report I found in
the archive is:
https://lore.kernel.org/all/85bfe02c-9432-c5b0-04e0-8096adf37b93@gmx.com/#t
which apparently went away after a make clean whereas mine persists.
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-04-08 11:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 11:54 Will Deacon [this message]
2022-04-08 14:45 ` allmodconfig builds failing to link on arm64 Mark Rutland
2022-04-08 15:04 ` Nathan Chancellor
2022-04-08 15:04 ` Nathan Chancellor
2022-04-08 15:06 ` Mark Rutland
2022-04-08 16:13 ` Will Deacon
2022-04-08 17:17 ` Nathan Chancellor
2022-04-08 18:37 ` Nathan Chancellor
2022-04-13 9:26 ` Will Deacon
2022-04-13 15:04 ` Nathan Chancellor
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=20220408115407.GA27685@willie-the-truck \
--to=will@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=nathan@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 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.