From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] samba4: Make python2 dependency for waf explicit
Date: Wed, 18 Oct 2017 17:37:32 +0200 [thread overview]
Message-ID: <20171018173732.368ed195@windsurf.home> (raw)
In-Reply-To: <20171018140304.19737-2-christian.kellermann@solectrix.de>
Hello,
On Wed, 18 Oct 2017 16:03:04 +0200, Christian Kellermann wrote:
> Without this patch the build environment will pick up python3 if it is a
> dependency for other packages. Currently waf does not support
> python3.
Are we talking about host python or target python here ?
> +diff --git a/buildtools/bin/waf b/buildtools/bin/waf
> +index 1b0f4662a56..f66b992e78c 100755
> +--- a/buildtools/bin/waf
> ++++ b/buildtools/bin/waf
> +@@ -1,4 +1,4 @@
> +-#!/usr/bin/env python
> ++#!/usr/bin/env python2
This runs on the host, so this is about host python, and matches your
description of "waf needs python2".
> - PYTHON_CONFIG="$(STAGING_DIR)/usr/bin/python-config" \
> + PYTHON_CONFIG="$(STAGING_DIR)/usr/bin/python2-config" \
This is related to the *target* python, so how is this related to the
waf problem ?
> python_LDFLAGS="" \
> python_LIBDIR="" \
> $(TARGET_CONFIGURE_OPTS) \
> $(SAMBA4_CONF_ENV) \
> + PYTHON=python2 \
> ./buildtools/bin/waf configure \
> --prefix=/usr \
> --sysconfdir=/etc \
> @@ -115,6 +116,8 @@ define SAMBA4_CONFIGURE_CMDS
> )
> endef
>
> +TARGET_MAKE_ENV += PYTHON=python2 \
Are all of these PYTHON=python2 necessary?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-18 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 14:03 [Buildroot] [PATCH 0/1] Build samba4 for a target that also needs Python3 Christian Kellermann
2017-10-18 14:03 ` [Buildroot] [PATCH 1/1] samba4: Make python2 dependency for waf explicit Christian Kellermann
2017-10-18 15:37 ` Thomas Petazzoni [this message]
2017-10-24 9:22 ` [Buildroot] [PATCH v1] " Christian Kellermann
[not found] ` <87zi8gnbgp.fsf@sx4173-linuxdev.solectrix.de>
2017-10-26 11:47 ` [Buildroot] [PATCH 1/1] " Thomas Petazzoni
2018-01-01 12:35 ` 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=20171018173732.368ed195@windsurf.home \
--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