From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/ima-evm-utils: fix build on musl
Date: Thu, 23 Jul 2020 22:40:44 +0200 [thread overview]
Message-ID: <20200723224044.3dc2fefe@windsurf.home> (raw)
In-Reply-To: <20200723200457.3996-1-petr.vorel@gmail.com>
On Thu, 23 Jul 2020 22:04:55 +0200
Petr Vorel <petr.vorel@gmail.com> wrote:
> Fixes:
> br-arm-cortex-a9-musl [ 7/44]: FAILED
> br-i386-pentium-mmx-musl [12/44]: FAILED
> br-x86-64-musl [34/44]: FAILED
> linaro-aarch64 [36/44]: FAILED
>
> Fix will be released in future release (after 1.3), but was needed since
> initial release.
>
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
Why don't we have autobuilder failures ?
If you look at:
http://autobuild.buildroot.net/index.php?libc=musl&symbols%5BBR2_PACKAGE_IMA_EVM_UTILS%5D=y
you will see that we have plenty of builds that succeed, with
BR2_PACKAGE_IMA_EVM_UTILS=y, with musl toolchains.
Notes:
- There are failures above, but none of them are due to ima-evm-utils.
You can also look at
http://autobuild.buildroot.net/?reason=ima-evm-utils% which shows we
never had a single build failure caused by this package (it seems).
- The above URL is slow to load, please give it some time, the SQL
query is slow!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-07-23 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 20:04 [Buildroot] [PATCH v2 1/3] package/ima-evm-utils: fix build on musl Petr Vorel
2020-07-23 20:04 ` [Buildroot] [PATCH v2 2/3] package/ima-evm-utils: bump version to 1.3 Petr Vorel
2020-07-23 20:04 ` [Buildroot] [PATCH v2 3/3] package/ima-evm-utils: fix build for old compilers Petr Vorel
2020-07-23 20:36 ` Thomas Petazzoni
2020-07-24 5:33 ` Petr Vorel
2020-07-23 20:40 ` Thomas Petazzoni [this message]
2020-07-24 5:43 ` [Buildroot] [PATCH v2 1/3] package/ima-evm-utils: fix build on musl Petr Vorel
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=20200723224044.3dc2fefe@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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