From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 12/12] libffi and python: need threads support
Date: Sun, 14 Sep 2014 08:42:45 +0200 [thread overview]
Message-ID: <88168771.CuPlRCWCIN@sagittea> (raw)
In-Reply-To: <20140913095712.223528dd@free-electrons.com>
On Saturday 13 September 2014 09:57:12 Thomas Petazzoni wrote:
> Dear J?r?me Pouiller,
>
> On Fri, 12 Sep 2014 17:50:11 +0200, J?r?me Pouiller wrote:
> > libffi depends on pthreads.
> >
> > Python depends on libffi (it can provide a builtin libffi, but also
> > depends on pthreads). Thus this patch also disable Python support if
> > toolchain is compiled w/o treads support.
> >
> > Fixes http://sysmic.org/~jezz/results/204099dd:
> >
> > ../src/closures.c:119:21: fatal error: pthread.h: No such file or
> > directory
>
> This seems weird. We have a no threads toolchain in our autobuilders
> and it was never detected, even though I'm pretty sure libffi was built
> a number of times. Do you have the configuration that exhibits the
> problem?
I can reproduce problem using:
BR2_powerpc=y
BR2_powerpc_440=y
BR2_TOOLCHAIN_BUILDROOT_LARGEFILE=y
BR2_TOOLCHAIN_BUILDROOT_INET_IPV6=y
BR2_TOOLCHAIN_BUILDROOT_INET_RPC=y
BR2_TOOLCHAIN_BUILDROOT_LOCALE=y
BR2_PTHREADS_NONE=y
BR2_BINUTILS_VERSION_2_24=y
BR2_GCC_VERSION_4_9_X=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_PACKAGE_LIBFFI=y
In add, I found this patch :
http://lists.busybox.net/pipermail/buildroot/2012-November/061976.html
It is seems is had never been applied and it should solve this issue.
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
prev parent reply other threads:[~2014-09-14 6:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 15:49 [Buildroot] Fix some build issues Jérôme Pouiller
2014-09-12 15:50 ` [Buildroot] [PATCH 01/12] xdriver_xf86-video-vmware: only avaiblable on x86 Jérôme Pouiller
2014-09-12 21:15 ` Peter Korsgaard
2014-09-12 15:50 ` [Buildroot] [PATCH 02/12] xapp_xkbevd: depends on MMU Jérôme Pouiller
2014-09-12 21:21 ` Peter Korsgaard
2014-09-12 15:50 ` [Buildroot] [PATCH 03/12] xapp_xinit: " Jérôme Pouiller
2014-09-12 21:19 ` Peter Korsgaard
2014-09-13 5:59 ` Jérôme Pouiller
2014-09-12 15:50 ` [Buildroot] [PATCH 04/12] xapp_xsm: " Jérôme Pouiller
2014-09-12 21:15 ` Peter Korsgaard
2014-09-12 15:50 ` [Buildroot] [PATCH 05/12] xapp_xmh: " Jérôme Pouiller
2014-09-12 21:16 ` Peter Korsgaard
2014-09-12 15:50 ` [Buildroot] [PATCH 06/12] xapp_xdm: " Jérôme Pouiller
2014-09-12 21:20 ` Peter Korsgaard
2014-09-12 15:50 ` [Buildroot] [PATCH 07/12] xterm: " Jérôme Pouiller
2014-09-12 21:16 ` Peter Korsgaard
2014-09-12 15:50 ` [Buildroot] [PATCH 08/12] xfsprogs: " Jérôme Pouiller
2014-09-12 21:20 ` Peter Korsgaard
2014-09-12 15:50 ` [Buildroot] [PATCH 09/12] ltp-testsuite: " Jérôme Pouiller
2014-09-12 21:20 ` Peter Korsgaard
2014-09-12 15:50 ` [Buildroot] [PATCH 10/12] sdl: remove dga support in no MMU Jérôme Pouiller
2014-09-12 21:31 ` Peter Korsgaard
2014-09-12 15:50 ` [Buildroot] [PATCH 11/12] directfb: allow SVG support Jérôme Pouiller
2014-09-13 7:23 ` Peter Korsgaard
2014-09-12 15:50 ` [Buildroot] [PATCH 12/12] libffi and python: need threads support Jérôme Pouiller
2014-09-13 7:39 ` Peter Korsgaard
2014-09-13 7:57 ` Thomas Petazzoni
2014-09-14 6:42 ` Jérôme Pouiller [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=88168771.CuPlRCWCIN@sagittea \
--to=jezz@sysmic.org \
--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.