From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/ci20: Use upstream Linux and U-Boot
Date: Wed, 12 Aug 2020 11:41:33 +0200 [thread overview]
Message-ID: <20200812114133.492bb1e3@windsurf.home> (raw)
In-Reply-To: <20200811154429.436747-1-ezequiel@vanguardiasur.com.ar>
Hello,
On Tue, 11 Aug 2020 12:44:29 -0300
Ezequiel Garcia via buildroot <buildroot@busybox.net> wrote:
> From: Ezequiel Garcia <ezequiel@collabora.com>
>
> The vendor kernel we are currently selecting no longer builds,
> and fails with a ton of:
>
> from include/linux/list.h:8,
> from include/linux/module.h:9,
> from arch/mips/jz4740/prom.c:16:
> include/linux/log2.h:22:1: error: ignoring attribute 'noreturn' because it conflicts with attribute 'const' [-Werror=a
> ttributes]
> 22 | int ____ilog2_NaN(void);
> | ^~~
>
> We can't afford to fix that, so let's just move to upstream
> kernel and bootloader. It doesn't make much sense to keep
> using an unsupported kernel and bootloader at this point.
>
> This means we will be missing some of the features supported
> by the vendor (such as HDMI support), but it is what it is.
>
> Linux v5.7 and v5.4 have been tested to boot fine, the latter
> is picked for the defconfig.
I've added a reference to the Gitlab CI failure here.
> +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
> +BR2_TARGET_UBOOT_LATEST_VERSION=y
And changed this to use a fixed version instead of "latest version", so
that we're sure this defconfig will continue to build a U-Boot version
that was tested by someone.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-08-12 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 15:44 [Buildroot] [PATCH] configs/ci20: Use upstream Linux and U-Boot Ezequiel Garcia
2020-08-12 9:41 ` Thomas Petazzoni [this message]
2020-08-12 14:05 ` Ezequiel Garcia
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=20200812114133.492bb1e3@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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