From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] configs/roseapplepi: remove defconfig, broken
Date: Thu, 09 Oct 2025 20:21:44 +0200 [thread overview]
Message-ID: <87a520x7ev.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20251009145438.482069-1-thomas.perale@mind.be> (Thomas Perale's message of "Thu, 9 Oct 2025 16:54:38 +0200")
>>>>> "Thomas" == Thomas Perale <thomas.perale@mind.be> writes:
> In reply of:
>> The roseapplepi defconfig fails to build u-boot since the move to GCC 15.x:
>>
>> https://gitlab.com/buildroot.org/buildroot/-/jobs/11501385206
>>
>> The issues are mainly related to missing includes, but given that the build
>> has been broken for a while, there is no mainline u-boot support for the
>> platform and the minimal kernel support has not seen any updates since it
>> was added for v5.15, just drop the defconfig.
>>
>> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> Applied to 2025.02.x, 2025.05.x & 2025.08.x. Thanks
Ups, I see I wrote GCC 15.x above, but it should naturally be 14.x. As
for the beagleboneai commits, we did not truly need to remove it from
2025.02.x / 2025.05.x.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-10-09 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 8:54 [Buildroot] [PATCH] configs/roseapplepi: remove defconfig, broken Peter Korsgaard
2025-10-05 13:43 ` Peter Korsgaard
2025-10-09 14:54 ` Thomas Perale via buildroot
2025-10-09 18:21 ` Peter Korsgaard [this message]
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=87a520x7ev.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=thomas.perale@mind.be \
/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.