Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libglib2: Avoid absolute path to python in shebang
Date: Thu, 19 Jul 2018 15:24:49 +0200	[thread overview]
Message-ID: <20180719152449.054a35f8@windsurf> (raw)
In-Reply-To: <20180719125828.xjctfak3qpsawq5z@bifrost>

Hello,

On Thu, 19 Jul 2018 14:58:28 +0200, anisse at astier.eu wrote:

> > And also, it's not correct because our libglib package does not depend
> > on having python3 available on the host.
> 
> My understanding is that the scripts work with python2 too but that
> upstream is moving to python3 by default, because meson already requires
> host python3, which narrows the number of build-time dependencies.

OK, understood.

> So I don't think there's anything to change here, since host python2 is
> already a mandatory buidroot dependency.

Yes, that is correct. What I wasn't sure is if libglib2 needed any
version of python, or specifically python3.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-07-19 13:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12 16:37 [Buildroot] [PATCH 1/1] libglib2: Avoid absolute path to python in shebang David Owens
2018-07-18 15:18 ` Thomas Petazzoni
2018-07-19  7:58   ` Anisse Astier
2018-07-19  8:04     ` Thomas Petazzoni
2018-07-19 11:50       ` anisse at astier.eu
2018-07-19 12:15         ` Thomas Petazzoni
2018-07-19 12:58           ` anisse at astier.eu
2018-07-19 13:24             ` Thomas Petazzoni [this message]
2018-07-19 11:04     ` Peter Korsgaard
2018-07-19 11:55       ` anisse at astier.eu
2018-07-19 21:44 ` 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=20180719152449.054a35f8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox