From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the efi tree
Date: Mon, 19 Sep 2022 19:11:26 +1000 [thread overview]
Message-ID: <20220919191126.4a3c36f9@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
Hi all,
After merging the efi tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
x86_64-linux-gnu-ld: drivers/firmware/efi/libstub/x86-stub.stub.o:(.bss.efistub+0x8): multiple definition of `efi_system_table'; drivers/firmware/efi/libstub/systable.stub.o:(.bss.efistub+0x0): first defined here
Presumably caused by commit
8fd3c9a90998 ("efi/libstub: move efi_system_table global var into separate object")
(or maybe commit
ba2dd31b7588 ("efi/libstub: implement generic EFI zboot")
)
I have used the efi tree from next-20220916 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-09-19 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 9:11 Stephen Rothwell [this message]
2022-09-19 9:12 ` linux-next: build failure after merge of the efi tree Ard Biesheuvel
2022-09-19 9:25 ` Ard Biesheuvel
-- strict thread matches above, loose matches on Subject: below --
2023-08-22 6:48 Stephen Rothwell
2023-08-22 7:32 ` Ard Biesheuvel
2023-08-22 8:08 ` Stephen Rothwell
2023-08-22 8:41 ` Ard Biesheuvel
2025-07-09 10:21 Stephen Rothwell
2025-07-09 10:23 ` Ard Biesheuvel
2026-03-10 19:06 Mark Brown
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=20220919191126.4a3c36f9@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ardb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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