From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [BUG] host-python-2.7.16 fails to build on aarch64, luajit fails for soft float
Date: Mon, 1 Jul 2019 12:01:13 +0200 [thread overview]
Message-ID: <20190701120113.4da32768@windsurf.home> (raw)
In-Reply-To: <d596b57f-e046-ec2c-4413-e2a3f301412e@gmail.com>
Hello Petr,
Thanks for your bug report. See below for some comments. Adding
Fran?ois Perrad in Cc about the LuaJIT bump.
On Fri, 28 Jun 2019 19:07:40 +0200
Petr Cvek <petrcvekcz@gmail.com> wrote:
> Trying to build an MIPS system on debian/sid/aarch64 machine fails to build python2 for the host. It seems the current used python has a bundled version of libffi, which doesn't yet support aarch64.
>
> A temporary solution is to hardcopy libffi-3.3-rc0 into python source tree:
>
> output/build/host-python-2.7.16/Modules/_ctypes/libffi
For the target python, we're building libffi separately. I guess we
should do the same for host-python, i.e use host-libffi instead of the
bundled libffi.
Could you have a look at implementing this ?
> Alse luajit for the target fails to build for MIPS -msoft-float. This seems to be fixed in 2.1.0-beta3.
There is a patch at http://patchwork.ozlabs.org/patch/1095710/ that
bumps to 2.1.0-beta3, but only for AArch64. I'm not sure what we should
do about this.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-07-01 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 17:07 [Buildroot] [BUG] host-python-2.7.16 fails to build on aarch64, luajit fails for soft float Petr Cvek
2019-07-01 10:01 ` 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=20190701120113.4da32768@windsurf.home \
--to=thomas.petazzoni@bootlin.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