From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@buildroot.org
Subject: [Buildroot] [git commit] package/zbar: fix python build
Date: Sun, 3 Oct 2021 08:57:31 +0200 [thread overview]
Message-ID: <20211003070206.9F1C08B3B5@busybox.osuosl.org> (raw)
commit: https://git.buildroot.net/buildroot/commit/?id=eda35c429b9df120dcb06a34e20619d87b6d2fc3
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
Fix the following build failure with python raised since its activation
by commit cfc80eeeb4f3cb8e59b56bedd5bd49761764671f:
In file included from /home/giuliobenetti/autobuild/run/instance-2/output-1/host/include/python3.9/Python.h:63,
from python/zbarmodule.h:24,
from python/zbarmodule.c:24:
/home/giuliobenetti/autobuild/run/instance-2/output-1/host/include/python3.9/pyport.h:741:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
741 | #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
| ^~~~~
Fixes:
- http://autobuild.buildroot.org/results/43a8c8d5403c329f2d754ed09807a53772174397
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
---
package/zbar/zbar.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/zbar/zbar.mk b/package/zbar/zbar.mk
index 5554dca6a1..fb83fa01d5 100644
--- a/package/zbar/zbar.mk
+++ b/package/zbar/zbar.mk
@@ -34,6 +34,7 @@ endif
ifeq ($(BR2_PACKAGE_PYTHON3),y)
ZBAR_DEPENDENCIES += host-python3 python3
ZBAR_CONF_OPTS += --with-python=python3
+ZBAR_CONF_ENV += PYTHON_CONFIG="$(STAGING_DIR)/usr/bin/python3-config"
else
ZBAR_CONF_OPTS += --with-python=no
endif
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2021-10-03 7:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211003070206.9F1C08B3B5@busybox.osuosl.org \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
/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.