All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
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: Sun, 05 Oct 2025 23:16:31 +0200	[thread overview]
Message-ID: <a0837005bddaaece56d78bce2c55d6d7@free.fr> (raw)
In-Reply-To: <20251005113846.3940440-1-peter@korsgaard.com>

On 05/10/2025 13:38, Peter Korsgaard wrote:
> With the change to default to gcc 14.x with commit 1e1fafa1f0f5
> ("package/gcc: switch to GCC 14.x as the default"), the old u-boot 
> version
> no longer builds:
> 
> board/ti/am57xx/board.c:948:17: error: implicit declaration of function 
> 'do_cape_detect'; did you mean 'do_board_detect'? 
> [-Wimplicit-function-declaration]
> 
> https://gitlab.com/buildroot.org/buildroot/-/jobs/11570241744
> 
> So move to u-boot 2025.04 to fix that.  We still need a small patch as
> (early) beagleboneai boards do not have the EEPROM (or eMMC partition)
> populated, so include the bb.org patch from
> 
> https://github.com/beagleboard/u-boot/commit/0b161f8e89a411fe54059cf1d0ba61354ee1e8a2
> 
> The new u-boot version needs both openssl and gnutls on the host, so 
> enable
> them.
> 
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

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

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?

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2025-10-05 21:16 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 ` Julien Olivain via buildroot [this message]
2025-10-07 11:46   ` [Buildroot] [PATCH 1/2] configs/beagleboneai: move to u-boot 2025.04 to unbreak build with gcc 14 Peter Korsgaard

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=a0837005bddaaece56d78bce2c55d6d7@free.fr \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=peter@korsgaard.com \
    /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.