From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Erico Nunes <nunes.erico@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/2] package/efivar: bump to version 38
Date: Thu, 6 Oct 2022 22:12:36 +0200 [thread overview]
Message-ID: <20221006221236.7dd6580a@windsurf> (raw)
In-Reply-To: <20221004143943.1456694-1-nunes.erico@gmail.com>
On Tue, 4 Oct 2022 16:39:42 +0200
Erico Nunes <nunes.erico@gmail.com> wrote:
> Drop backported patches and rebase the ones that are still relevant.
>
> From version 37 to 38, there is a new build system in place, which is
> still custom Makefiles.
> This introduces a host-efivar package to account for the 'makeguids'
> tool. Previously it was not too cumbersome to work around building that
> tool for the host, but with the new build system it is increasingly
> coupled with the target build that the least hacky way to work around it
> is with a host package and a Makefile patch.
>
> Signed-off-by: Erico Nunes <nunes.erico@gmail.com>
I've applied both, but I'm not super fan of the Buildroot-specific
patch in efivar to not build makeguids. Would it be possible to work
with the upstream efivar community to find a suitable solution to this
issue?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-10-06 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 14:39 [Buildroot] [PATCH v2 1/2] package/efivar: bump to version 38 Erico Nunes
2022-10-04 14:39 ` [Buildroot] [PATCH v2 2/2] package/efibootmgr: bump to version 18 Erico Nunes
2022-10-06 20:12 ` Thomas Petazzoni via buildroot [this message]
2022-10-07 6:46 ` [Buildroot] [PATCH v2 1/2] package/efivar: bump to version 38 Erico Nunes
2022-10-10 15:12 ` Thomas Petazzoni via buildroot
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=20221006221236.7dd6580a@windsurf \
--to=buildroot@buildroot.org \
--cc=nunes.erico@gmail.com \
--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 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.