Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Kellermann <christian.kellermann@solectrix.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/1] Build samba4 for a target that also needs Python3
Date: Wed, 18 Oct 2017 16:03:03 +0200	[thread overview]
Message-ID: <20171018140304.19737-1-christian.kellermann@solectrix.de> (raw)

This patch is necessary to build samba for a target that also needs
Python 3. The python 3 installation overwrites the symbolic links for
the python target and staging directories.  The samba4 waf build tool
cannot yet cope with python3.

This patch is meant as a starting point for discussion as I am not
sure whether this is the Right Way to do this.  Hacking the waf script
itself is rather ugly, I have not found a way to make env pick up any
other hint to evaluate it as a python2 script.  Same goes for the
MAKE_ENV manipulation.

Suggestions welcome as always.

King regards,

Christian



Christian Kellermann (1):
  samba4: Make python2 dependency for waf explicit

 ...ake-python-2.7-dependency-in-waf-explicit.patch | 27 ++++++++++++++++++++++
 package/samba4/samba4.mk                           |  5 +++-
 2 files changed, 31 insertions(+), 1 deletion(-)
 create mode 100644 package/samba4/0002-Make-python-2.7-dependency-in-waf-explicit.patch

-- 
2.12.1

             reply	other threads:[~2017-10-18 14:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 14:03 Christian Kellermann [this message]
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
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=20171018140304.19737-1-christian.kellermann@solectrix.de \
    --to=christian.kellermann@solectrix.de \
    --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