From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [RFC 0/7] Update CI to using GCC 11.0 / LLVM-11
Date: Mon, 3 May 2021 16:48:52 -0400 [thread overview]
Message-ID: <20210503204859.18756-1-trini@konsulko.com> (raw)
Hey all,
This series does most of the work required to move to using GCC-11.0 to
build in CI. The first thing is I realized I forgot to update buildman
to know to where to fetch gcc-11 from, but I'll take care of that later.
Next, this ends up using the last gcc-11 snapshot as the gcc-11.0
prebuilds aren't quite up on kernel.org, but will be soon.
The real issues here and I'd like some feedback on, and need some help
with are:
- grub + riscv32 + gcc-11 doesn't build, and this seems known but not
addressed yet. I don't know what we want to do here as it's for
running some tests.
- I cannot get x86 to build. With this series the failures are:
https://source.denx.de/u-boot/u-boot/-/jobs/263745
But I can't find a good way to address that multiple definition error
of _X86EMU_env that doesn't break some other platform. At heart,
Chromebooks enable the emulation and we have both chromebook_link and
chromebook_link64 as builds, so we have both X86_64 and !X86_64
builds. I don't know the best way to deal with this, but I also
wonder if the bios_emulation code doesn't need a rather large cleaning
perhaps?
--
Tom
next reply other threads:[~2021-05-03 20:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 20:48 Tom Rini [this message]
2021-05-03 20:48 ` [RFC 1/7] ARM: mvebu: a38x: Correct mismatched bound warnings Tom Rini
2021-07-07 17:33 ` Tom Rini
2021-07-14 20:52 ` Pali Rohár
2021-07-15 7:59 ` Stefan Roese
2021-07-15 13:07 ` [EXT] " Kostya Porotchkin
2021-05-03 20:48 ` [RFC 2/7] freescale: Drop unnecessary cpld_data_t non-typedef Tom Rini
2021-07-07 17:34 ` Tom Rini
2021-05-03 20:48 ` [RFC 3/7] eb_cpu5282: Declare diplay_width / display_height as externs Tom Rini
2021-07-07 17:34 ` Tom Rini
2021-05-03 20:48 ` [RFC 4/7] pinctrl: mscc: Fix multiple definition error Tom Rini
2021-05-04 7:51 ` Horatiu Vultur
2021-05-04 18:57 ` Daniel Schwierzeck
2021-07-07 17:34 ` Tom Rini
2021-05-03 20:48 ` [RFC 5/7] Makefile: Disable gcc-10.0 warnings Tom Rini
2021-07-07 17:34 ` Tom Rini
2021-05-03 20:48 ` [RFC 6/7] bootstage: Eliminate when not enabled Tom Rini
2021-07-07 17:34 ` Tom Rini
2021-05-03 20:48 ` [RFC 7/7] TEST: Move to gcc-11.0 prerelease and LLVM-11 Tom Rini
2021-06-16 19:58 ` [RFCv2] " Tom Rini
2021-06-16 20:00 ` [RFCv3] Azure/GitLab: Move to gcc-11.1.0 " Tom Rini
2021-06-17 8:27 ` Bin Meng
2021-06-17 12:31 ` Tom Rini
2021-06-17 14:09 ` Bin Meng
2021-06-17 14:14 ` Tom Rini
2021-06-17 14:24 ` Bin Meng
2021-06-17 14:45 ` Tom Rini
2021-06-17 14:51 ` Bin Meng
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=20210503204859.18756-1-trini@konsulko.com \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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