From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patch for opencv3: python module was built for the host instead of target.
Date: Sun, 1 Apr 2018 10:50:42 +0200 [thread overview]
Message-ID: <20180401105042.577fa559@windsurf> (raw)
In-Reply-To: <MW2PR02MB3724CAF4A9F9EF9FEBF4C35E95D90@MW2PR02MB3724.namprd02.prod.outlook.com>
Hello,
On Tue, 6 Mar 2018 17:19:18 +0000, Shyrokov, Sasha wrote:
> From 9b211fb5ec49879d10d32d22ed3608ffca944e2d Mon Sep 17 00:00:00 2001
> From: Sasha Shyrokov <alexander-shyrokov@idexx.com>
> Date: Tue, 6 Mar 2018 10:58:10 -0500
> Subject: [PATCH 1/1] opencv3: python module was built for the host instead of target.
>
> distutils environment variables must be set.
> OPENCV3_CONF_ENV = $(PKG_PYTHON_DISTUTILS_ENV) All credit goes to Arnout:
> https://stackoverflow.com/questions/49059035/buildroot-opencv3-python-package-builds-for-the-wrong-target
>
> Signed-off-by: Sasha Shyrokov <alexander-shyrokov@idexx.com>
> ---
> package/opencv3/opencv3.mk | 1 +
> 1 file changed, 1 insertion(+)
Thanks, I've applied after extending the commit log to explain the
problem in more details, and apply the solution also to Python 2.x fo
consistency, even if it's only strictly needed for Python 3.x.
See
https://git.buildroot.org/buildroot/commit/?id=8ba80282c3bb580c6a45ea114e70acac98fe1690
Thanks for your contribution!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-04-01 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 17:19 [Buildroot] Patch for opencv3: python module was built for the host instead of target Shyrokov, Sasha
2018-04-01 8:50 ` Thomas Petazzoni [this message]
2018-04-08 15:07 ` Peter Korsgaard
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=20180401105042.577fa559@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