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: Mon, 1 Jan 2018 13:35:57 +0100 [thread overview]
Message-ID: <20180101133557.5501db35@windsurf> (raw)
In-Reply-To: <20171026134701.3e633e03@windsurf>
Hello,
On Thu, 26 Oct 2017 13:47:01 +0200, Thomas Petazzoni wrote:
> > >> - 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 ?
> >
> > It needs to pick up the python headers. Without this I get the error:
> > ?Could not find the python development headers?
>
> I don't see how this modification changes anything. BR2_PACKAGE_SAMBA4
> selects BR2_PACKAGE_PYTHON, and BR2_PACKAGE_PYTHON3 depends
> on !BR2_PACKAGE_PYTHON.
>
> So if you have samba4 enabled, the python version enabled for the
> target is always Python 2.x, and therefore python-config and
> python2-config in staging should be the same thing.
>
> So we need to understand if this change is really necessary, and if it
> is, why is it that it creates a difference.
Since you did not give further feedback, and I still don't understand
what problem this patch is solving, I've marked your patch as Rejected
in our patch tracking system.
Do not hesitate to send an updated version with an improved explanation
(for example with a defconfig that allows to reproduce the problem, and
some answers to the questions I've asked).
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2018-01-01 12:35 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
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 [this message]
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=20180101133557.5501db35@windsurf \
--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