From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Matt Weber <matthew.weber@collins.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/rng-tools: fix musl build
Date: Tue, 28 Dec 2021 21:44:17 +0100 [thread overview]
Message-ID: <20211228214417.6afc81b3@windsurf> (raw)
In-Reply-To: <20211228133959.3690191-1-fontaine.fabrice@gmail.com>
On Tue, 28 Dec 2021 14:39:59 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following musl build failure raised since bump to version 6.14
> in commit 5292d1cf9ad0605cc264fedc75c1b9a169aa183b:
>
> /home/buildroot/autobuild/instance-0/output-1/host/opt/ext-toolchain/bin/../lib/gcc/i586-buildroot-linux-musl/9.3.0/../../../../i586-buildroot-linux-musl/bin/ld: rngd-rngd_jitter.o: in function `rngd_notime_start':
> rngd_jitter.c:(.text+0xdc2): undefined reference to `pthread_attr_setaffinity_np'
>
> Fixes:
> - http://autobuild.buildroot.org/results/3ec7df86856aa9bee2f18a8faa44fd58bc8a6657
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...ct-non-posix-extensions-for-pthreads.patch | 43 ++++++++++++++++
> ...-either-pthread-affinity-set-methods.patch | 49 +++++++++++++++++++
> 2 files changed, 92 insertions(+)
> create mode 100644 package/rng-tools/0001-Adding-ability-to-detect-non-posix-extensions-for-pthreads.patch
> create mode 100644 package/rng-tools/0002-Allow-for-use-of-either-pthread-affinity-set-methods.patch
Applied to master, thanks.
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:[~2021-12-28 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 13:39 [Buildroot] [PATCH 1/1] package/rng-tools: fix musl build Fabrice Fontaine
2021-12-28 20:44 ` Thomas Petazzoni [this message]
2022-01-25 18:08 ` 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=20211228214417.6afc81b3@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=matthew.weber@collins.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