Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] boot/grub2: properly handle autoreconf for target package
Date: Tue, 11 Aug 2026 21:17:26 +0200	[thread overview]
Message-ID: <40e3182d70d60b476742b3ad34ad9cd3@free.fr> (raw)
In-Reply-To: <20260810212918.460215-1-thomas.petazzoni@bootlin.com>

On 10/08/2026 23:29, Thomas Petazzoni via buildroot wrote:
> In commit e427f85e29f7027319a5cd1ce1024d80ef4a29ea ("boot/grub2: fix
> build issue since 2.14 version bump") we added some patches that
> require regenerating the configure script. Consequently, we added
> GRUB2_AUTORECONF = YES and HOST_GRUB2_AUTORECONF = YES.
> 
> Except that grub2 is special. While the host package is indeed using
> host-autotols-package, the target package is using generic-package,
> making GRUB2_AUTORECONF = YES basically a no-op.
> 
> Except that since we're patching configure.ac, the build realize at
> build time that configure is older than configure.ac, regenerates it
> at that time, and re-runs the configure script without the right
> environment variables causing build failures.
> 
> We fix that by doing the autoreconf step "manually" for the target
> grub2 package.
> 
> Fixes:
> 
>   
> https://autobuild.buildroot.org/results/11802ca1762e046328df324d33a1ad813fcd92e8/
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-08-11 19:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10 21:29 [Buildroot] [PATCH] boot/grub2: properly handle autoreconf for target package Thomas Petazzoni via buildroot
2026-08-11 19:17 ` Julien Olivain via buildroot [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=40e3182d70d60b476742b3ad34ad9cd3@free.fr \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox