From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] pyrex: new package
Date: Mon, 3 Mar 2014 22:04:17 +0100 [thread overview]
Message-ID: <20140303220417.6835ec44@skate> (raw)
In-Reply-To: <1379700560-10738-1-git-send-email-mlweber1@rockwellcollins.com>
Dear Matt Weber,
On Fri, 20 Sep 2013 13:09:20 -0500, Matt Weber wrote:
> index 0000000..551c15c
> --- /dev/null
> +++ b/package/python-pyrex/Config.in
> @@ -0,0 +1,7 @@
> +config BR2_PACKAGE_PYTHON_PYREX
> + bool "pyrex"
> + depends on BR2_PACKAGE_PYTHON
> + help
> + Pyrex is a language for writing Python extension modules
> +
> + http://www.cosc.canterbury.ac.nz/greg.ewing/python/Pyrex/
If I understand correctly what Pyrex is, it is a tool that generates C
code that then needs to be compiled with gcc. At least that's what I
understand from http://ldots.org/pyrex-guide/2-compiling.html.
Therefore, I am wondering how useful it is to support the installation
of python-pyrex to the target, while we don't have the support for
providing a compiler on the target.
Is there something I have missed about Pyrex?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-03 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 18:09 [Buildroot] [PATCH 1/1] pyrex: new package Matt Weber
2014-03-03 21:04 ` Thomas Petazzoni [this message]
2014-03-04 15:16 ` mlweber1 at rockwellcollins.com
2014-03-04 15:23 ` Thomas Petazzoni
2014-03-04 15:27 ` mlweber1 at rockwellcollins.com
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=20140303220417.6835ec44@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