From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] libffi: make thread support optional
Date: Wed, 29 Oct 2014 18:54:00 -0300 [thread overview]
Message-ID: <545161F8.5040207@zacarias.com.ar> (raw)
In-Reply-To: <20141029222418.17f91967@free-electrons.com>
On 10/29/2014 06:24 PM, Thomas Petazzoni wrote:
> To be honest, I am wondering if we really should bother merging a patch
> to make libffi usable on configurations that have thread support
> disabled. Nowadays, not having thread support is also impossible due to
> the large number of libraries/applications that rely on threads. libffi
> is generally used in "big" things like Python or glib, so not having
> thread support in systems using such big things is a bit unlikely.
>
> In addition, I'm not sure the patch could be upstreamed as is, which
> means we would have to carry it in Buildroot forever.
>
> Peter, Arnout, Gustavo, what is your point of view on this?
+1, ditching threads (uClibc) is for really small targets which these
days would mostly mean noMMU.
Regards.
next prev parent reply other threads:[~2014-10-29 21:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 12:26 [Buildroot] [PATCH v2 1/2] libffi: make thread support optional Jérôme Pouiller
2014-09-15 12:26 ` [Buildroot] [PATCH v2 2/2] Revert "libffi and python: need threads support" Jérôme Pouiller
2014-10-29 21:24 ` [Buildroot] [PATCH v2 1/2] libffi: make thread support optional Thomas Petazzoni
2014-10-29 21:54 ` Gustavo Zacarias [this message]
2014-10-30 8:09 ` Arnout Vandecappelle
2014-10-30 10:31 ` Thomas Petazzoni
2014-10-30 10:51 ` Jérôme Pouiller
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=545161F8.5040207@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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 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.