From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] libffi: make thread support optional
Date: Wed, 29 Oct 2014 22:24:18 +0100 [thread overview]
Message-ID: <20141029222418.17f91967@free-electrons.com> (raw)
In-Reply-To: <1410784002-8659-1-git-send-email-jezz@sysmic.org>
Dear J?r?me Pouiller,
On Mon, 15 Sep 2014 14:26:41 +0200, J?r?me Pouiller wrote:
> From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>
> Fixes:
>
> http://autobuild.buildroot.org/results/7ee57d01917ea72d1811469e482513dda2ceb1ea/build-end.log
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Signed-off-by: J?r?me Pouiller <jezz@sysmic.org>
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?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-29 21:24 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 ` Thomas Petazzoni [this message]
2014-10-29 21:54 ` [Buildroot] [PATCH v2 1/2] libffi: make thread support optional Gustavo Zacarias
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=20141029222418.17f91967@free-electrons.com \
--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