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] gnuradio: needs host-python2
Date: Thu, 19 Jul 2018 17:02:05 +0200	[thread overview]
Message-ID: <20180719170205.0c06ccd3@windsurf> (raw)
In-Reply-To: <CAPi7W81kEgCx815QZcyewyLim-2F1uPYQTzVXG-xAjpi=hrcxA@mail.gmail.com>

Hello,

On Thu, 28 Jun 2018 19:25:32 +0200, Fabrice Fontaine wrote:

> Next branch builds fine however it seems there is outstanding issues:
> https://github.com/gnuradio/gnuradio/issues/1842. What should we do until
> an official release is made with python3 support?

In the mean time, I think I will just apply your patch that adds the
"depends on !BR2_PACKAGE_PYTHON3". It's not great, but it's not the
only simple approach to resolve the build failures.

In today's Buildroot, if a package needs host Python modules in the
Python version which is not the default one, this is not supported, and
it will be difficult to support this.

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

  reply	other threads:[~2018-07-19 15:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 21:43 [Buildroot] [PATCH 1/1] gnuradio: needs host-python2 Fabrice Fontaine
2018-06-27  3:36 ` Baruch Siach
2018-06-27  5:35   ` Fabrice Fontaine
2018-06-27 16:24     ` Fabrice Fontaine
2018-06-28  3:25       ` Baruch Siach
2018-06-28  7:58         ` Yegor Yefremov
2018-06-28  8:23           ` Thomas Petazzoni
2018-06-28  9:15             ` Yegor Yefremov
2018-06-28  9:20               ` Thomas Petazzoni
2018-06-28 10:02                 ` Yegor Yefremov
2018-06-28 17:25                   ` Fabrice Fontaine
2018-07-19 15:02                     ` Thomas Petazzoni [this message]
2018-06-28 18:46         ` Trent Piepho
2018-08-05 12:39 ` Thomas Petazzoni

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=20180719170205.0c06ccd3@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