From: Peter Korsgaard <peter@korsgaard.com>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] configs/beagleboneai: move to u-boot 2025.04 to unbreak build with gcc 14
Date: Tue, 07 Oct 2025 13:46:45 +0200 [thread overview]
Message-ID: <87ldln0w9m.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <a0837005bddaaece56d78bce2c55d6d7@free.fr> (Julien Olivain's message of "Sun, 05 Oct 2025 23:16:31 +0200")
>>>>> "Julien" == Julien Olivain <ju.o@free.fr> writes:
> Series applied to master, thanks.
> For info, I fixed a check-package error by removing the stale
> entry in .checkpackageingore file. See:
> https://gitlab.com/buildroot.org/buildroot/-/commit/7ec419fb9c07292dc28b87ccb0ed35b00437dd16
Ups, thanks.
> Also, if you still have your board available for testing, I suggest
> the following maintenance followup patches:
> Could you fix the shellcheck warnings in:
> board/beagleboard/beagleboneai/post-build.sh
> and remove the .checkpackageignore entry
> Could you also switch this beagleboneai_defconfig to use a bootlin
> external glibc stable toolchain please?
Sure, I'll do a quick test and send a series.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-10-07 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-05 11:38 [Buildroot] [PATCH 1/2] configs/beagleboneai: move to u-boot 2025.04 to unbreak build with gcc 14 Peter Korsgaard
2025-10-05 11:38 ` [Buildroot] [PATCH 2/2] configs/beagleboneai: move to Linux 6.12.50 Peter Korsgaard
2025-10-09 14:54 ` Thomas Perale via buildroot
2025-10-09 18:19 ` Peter Korsgaard
2025-10-05 21:16 ` [Buildroot] [PATCH 1/2] configs/beagleboneai: move to u-boot 2025.04 to unbreak build with gcc 14 Julien Olivain via buildroot
2025-10-07 11:46 ` 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=87ldln0w9m.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
/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.