From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/5] openpgm: make its build system python2/python3 friendly
Date: Mon, 14 Apr 2014 23:15:34 +0200 [thread overview]
Message-ID: <20140414231534.355388db@skate> (raw)
In-Reply-To: <1397509552-5278-6-git-send-email-s.martin49@gmail.com>
Dear Samuel Martin,
On Mon, 14 Apr 2014 23:05:52 +0200, Samuel Martin wrote:
> This patch fixes build issue when python3 is enabled, and host python2
> interpreter is not available.
>
> Fixes:
> http://autobuild.buildroot.net/results/01f/01f886a073439c0639ed93e596b68bcadf1a5824/
>
> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
> Cc: Baruch Siach <baruch@tkos.co.il>
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-04-14 21:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 21:05 [Buildroot] [PATCH 0/5] Python fixes Samuel Martin
2014-04-14 21:05 ` [Buildroot] [PATCH 1/5] nodejs: use the standard configure/make options Samuel Martin
2014-04-14 21:12 ` Thomas Petazzoni
2014-04-14 21:20 ` Samuel Martin
2014-04-14 21:05 ` [Buildroot] [PATCH 2/5] nodejs: force python interpreter Samuel Martin
2014-04-14 21:05 ` [Buildroot] [PATCH 3/5] omniorb: force python interperter Samuel Martin
2014-04-14 21:14 ` Thomas Petazzoni
2014-04-14 21:05 ` [Buildroot] [PATCH 4/5] host-python-pyrex: use the HOST_*_NEEDS_HOST_PYTHON infrastructure Samuel Martin
2014-04-14 21:15 ` Thomas Petazzoni
2014-04-14 21:22 ` Samuel Martin
2014-04-14 21:28 ` Thomas Petazzoni
2014-04-14 21:05 ` [Buildroot] [PATCH 5/5] openpgm: make its build system python2/python3 friendly Samuel Martin
2014-04-14 21:15 ` 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=20140414231534.355388db@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