From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libressl: needs MMU
Date: Sun, 5 Nov 2017 15:39:18 +0100 [thread overview]
Message-ID: <20171105153918.58d05c6f@windsurf.home> (raw)
In-Reply-To: <2f141bf5-ccdb-ecff-88d8-17e59e724e90@mind.be>
Hello,
On Sat, 4 Nov 2017 23:25:57 +0100, Arnout Vandecappelle wrote:
> >> But I think the commit log isn't correct, as pthread_atfork can be
> >> used for glibc, musl and uClibc-ng. (for glibc -lpthread must be
> >> added)
> >>
> >> One possible solution might be, to check for __register_atfork, if
> >> it does not exist, fallback to pthread_atfork, if it does not exist
> >> provide a pthread_atfork dummy (noMMU case).
> >
> > This should be doable without too much effort I believe.
>
> But someone has to do it :-)
>
> Note that the autobuilders no longer complain about this since libressl is now
> a choice, so it never gets built. But the problem still persists.
We discussed it during the Developers Meeting (remember?) and I have in
my notes to mark it as not available on noMMU platforms that use uClibc
(because it's really a uClibc limitation).
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-11-05 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 20:08 [Buildroot] [PATCH 1/1] package/libressl: needs MMU Bernd Kuhls
2017-07-24 16:07 ` Thomas Petazzoni
2017-07-24 21:07 ` Waldemar Brodkorb
2017-07-25 7:32 ` Thomas Petazzoni
2017-11-04 22:25 ` Arnout Vandecappelle
2017-11-05 14:39 ` Thomas Petazzoni [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=20171105153918.58d05c6f@windsurf.home \
--to=thomas.petazzoni@free-electrons.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