All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next v2 1/3] package/libevdev: add host-python dependency
Date: Thu, 5 Mar 2020 23:07:11 +0100	[thread overview]
Message-ID: <20200305230711.1c8f78c5@windsurf> (raw)
In-Reply-To: <20200302150907.5812-1-ps.report@gmx.net>

Hello,

On Mon,  2 Mar 2020 16:09:05 +0100
Peter Seiderer <ps.report@gmx.net> wrote:

> Fixes:
> 
>   checking for a Python interpreter with version >= 2.6... none
>   configure: error: no suitable Python interpreter found
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>

I've applied to master. Ideally, I would have preferred to use
host-python3, since Titouan is working on making sure everything in
Buildroot builds properly with Python 3. However due to another issue
host-python3 is not self-sufficient: it doesn't build if Python3 is not
already installed on the build machine!

So, for now, I've applied your patch as-is to master.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2020-03-05 22:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02 15:09 [Buildroot] [PATCH/next v2 1/3] package/libevdev: add host-python dependency Peter Seiderer
2020-03-02 15:09 ` [Buildroot] [PATCH/next v2 2/3] package/libevdev: bump version to 1.9.0 Peter Seiderer
2020-03-05 22:10   ` Thomas Petazzoni
2020-03-02 15:09 ` [Buildroot] [PATCH/next v2 3/3] package/libevdev: convert to meson Peter Seiderer
2020-03-05 20:27   ` Peter Seiderer
2020-03-05 22:11   ` Thomas Petazzoni
2020-03-05 22:07 ` Thomas Petazzoni [this message]
2020-03-15 10:28 ` [Buildroot] [PATCH/next v2 1/3] package/libevdev: add host-python dependency Peter Korsgaard

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=20200305230711.1c8f78c5@windsurf \
    --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 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.