From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/openssl: fix libressl dependency
Date: Thu, 04 Aug 2022 17:01:58 +0200 [thread overview]
Message-ID: <87czdgrr15.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220716134714.611106-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sat, 16 Jul 2022 15:47:14 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> libressl can be built with uclibc on noMMU since bump to version 3.0.2
> in commit 26f42106e8acfd336d8e902da96cd2ac9e63c09d and
> https://github.com/libressl-portable/openbsd/commit/f542e84c859e3fb2728075c702062cce8a0ea93f
> However, uclibc-ng doesn't provide __register_atfork without NPTL
> resulting in the following libressl build failure:
> /nvmedata/autobuild/instance-28/output-1/host/lib/gcc/arceb-buildroot-linux-uclibc/10.3.0/../../../../arceb-buildroot-linux-uclibc/bin/ld:
> ../../tls/libtls.a(arc4random.c.o): in function `_rs_stir':
> arc4random.c:(.text+0x50c): undefined reference to `__register_atfork'
> So fix the dependency and, while at it, drop the double negation for
> readability
> Fixes:
> - http://autobuild.buildroot.org/results/2fa4fa10cf19f1f942b6b49b5f6f05339c008cd4
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2022.05.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-08-04 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 13:47 [Buildroot] [PATCH 1/1] package/openssl: fix libressl dependency Fabrice Fontaine
2022-07-16 22:04 ` Yann E. MORIN
2022-08-04 15:01 ` Peter Korsgaard [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=87czdgrr15.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.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.