From: Erico Nunes <nunes.erico@gmail.com>
To: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/efivar: fix build with musl libc
Date: Thu, 10 Nov 2022 11:01:41 +0100 [thread overview]
Message-ID: <CAK4VdL2JLMZvb6oE7gkZxt_VaccQOy+f1OkNnG4paHkkmMmNyQ@mail.gmail.com> (raw)
In-Reply-To: <20221011084946.2276735-1-nunes.erico@gmail.com>
Hello,
On Tue, Oct 11, 2022 at 10:49 AM Erico Nunes <nunes.erico@gmail.com> wrote:
>
> Backport upstream patch to fix build with musl libc.
> This patch is only a requirement since efivar 38 and was applied
> upstream shortly after the 38 version tag.
>
> Fixes:
> http://autobuild.buildroot.net/results/c49d894b109d68e2624074eab8b939fefa3b42ef/
Looks like this patch was missed in the queue and that issue is still
generating daily autobuilder failures. Could someone take a look
please?
Thanks
Erico
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-11-10 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 8:49 [Buildroot] [PATCH] package/efivar: fix build with musl libc Erico Nunes
2022-11-10 10:01 ` Erico Nunes [this message]
2022-11-13 11:51 ` Yann E. MORIN
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=CAK4VdL2JLMZvb6oE7gkZxt_VaccQOy+f1OkNnG4paHkkmMmNyQ@mail.gmail.com \
--to=nunes.erico@gmail.com \
--cc=buildroot@buildroot.org \
/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;
as well as URLs for NNTP newsgroup(s).