All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] python-libconfig: fix build with python2
Date: Tue, 26 Jun 2018 20:39:45 +0200	[thread overview]
Message-ID: <20180626183945.28667-1-fontaine.fabrice@gmail.com> (raw)

Since boost 1.67, libboost_python is now named libboost_python27 when
python2 is enabled

Fixes:
 - http://autobuild.buildroot.net/results/a1feb4c4b70b3c939ae1127417130ea33a91159b

Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
 .../0001-Determine-boost_python-name-depending-on-current-Pyt.patch | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/package/python-libconfig/0001-Determine-boost_python-name-depending-on-current-Pyt.patch b/package/python-libconfig/0001-Determine-boost_python-name-depending-on-current-Pyt.patch
index 53000cd678..478bac76f6 100644
--- a/package/python-libconfig/0001-Determine-boost_python-name-depending-on-current-Pyt.patch
+++ b/package/python-libconfig/0001-Determine-boost_python-name-depending-on-current-Pyt.patch
@@ -4,8 +4,8 @@ Date: Thu, 27 Jul 2017 09:46:07 +0200
 Subject: [PATCH] Determine boost_python name depending on current Python
  version
 
-Python2 requires boost_python and Python3 requires boost_python36 (since
-boost 1.67).
+Python2 requires boost_python27 and Python3 requires boost_python36
+(since boost 1.67).
 
 Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
@@ -23,7 +23,7 @@ index fdf5c27..4b38569 100644
  
 +boostlib = "boost_python36"
 +if sys.version_info < (3, 0):
-+    boostlib = "boost_python"
++    boostlib = "boost_python27"
 +
  setup(
      name				= 'pylibconfig',
-- 
2.14.1

             reply	other threads:[~2018-06-26 18:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 18:39 Fabrice Fontaine [this message]
2018-07-01 13:49 ` [Buildroot] [PATCH 1/1] python-libconfig: fix build with python2 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=20180626183945.28667-1-fontaine.fabrice@gmail.com \
    --to=fontaine.fabrice@gmail.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.