Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] including python when compiling for microblaze
Date: Thu, 12 Jan 2012 11:02:45 +0100	[thread overview]
Message-ID: <20120112110245.73e2323b@skate> (raw)
In-Reply-To: <2AB0B5A7-70EA-4CDB-8B28-A07F81E83394@informatik.uni-bremen.de>

Hello,

Le Thu, 12 Jan 2012 09:47:13 +0100,
Johannes Teiwes <jteiwes@informatik.uni-bremen.de> a ?crit :

> I am currently trying to port the python package in buidroot to the
> microblaze platform. I have everything set up with a custom toolchain
> etc. and it works fine. The problem is the libffi library, which is
> required for building any script language (e.g. perl, python) for
> buildroot. The exact error message says
> 
> configure: error: "libffi has not been ported to
> microblaze-unknown-linux-gnu."
> 
> Has anyone started to port libffi to another platform or even found a
> specific workaround for microblaze? Is there any alternative to the
> libffi library or installing python via buildroot?

Apparently, libffi has no supported for microblaze, and it seems that
libffi is a mandatory dependency for building Python. It looks like you
have two options:

 *) Port libffi to Microblaze

 *) Use a more lightweight scripting language such as Lua. Python is
    quite heavy for MMU-less systems at 100-180 Mhz such as Microblaze
    systems. Lua is probably a much better fit for this kind of systems.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2012-01-12 10:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-12  8:47 [Buildroot] including python when compiling for microblaze Johannes Teiwes
2012-01-12 10:02 ` 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=20120112110245.73e2323b@skate \
    --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