From: Tomi Ollila <tomi.ollila@iki.fi>
To: notmuch@notmuchmail.org
Cc: tomi.ollila@iki.fi
Subject: [PATCH] configure: check existence of python3 setuptools and dev package
Date: Mon, 1 Jun 2020 08:31:42 +0300 [thread overview]
Message-ID: <20200601053142.22578-1-tomi.ollila@iki.fi> (raw)
The notmuch2 CFFI-based Python interface is not buildable unless
python3 dev package and python3 setuptools are installed.
Check that these exist in configure (and disable notmuch2 bindings
build if not) so that build of these bindings don't fail when make(1)
is executed.
---
configure | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/configure b/configure
index 32a836bb..e4c738e5 100755
--- a/configure
+++ b/configure
@@ -711,12 +711,14 @@ if [ $have_python -eq 0 ]; then
errors=$((errors + 1))
fi
-have_python3=0
+have_python3_dev=0
if [ $have_python -eq 1 ]; then
- printf "Checking for python3..."
- if "$python" -c 'import sys; assert sys.version_info >= (3,0)' > /dev/null 2>&1; then
+ printf "Checking for python3 dev..."
+ if "$python" -c 'import os, sys, sysconfig;
+assert sys.version_info >= (3,0)
+assert os.path.isfile(sysconfig.get_config_h_filename())' >/dev/null 2>&1; then
printf "Yes.\n"
- have_python3=1
+ have_python3_dev=1
else
printf "No.\n"
fi
@@ -724,9 +726,9 @@ fi
have_python3_cffi=0
have_python3_pytest=0
-if [ $have_python3 -eq 1 ]; then
- printf "Checking for python3 cffi... "
- if "$python" -c 'import cffi' >/dev/null 2>&1; then
+if [ $have_python3_dev -eq 1 ]; then
+ printf "Checking for python3 cffi and setuptools... "
+ if "$python" -c 'import cffi; import setuptools' >/dev/null 2>&1; then
printf "Yes.\n"
have_python3_cffi=1
else
--
2.25.1
next reply other threads:[~2020-06-01 5:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 5:31 Tomi Ollila [this message]
2020-06-01 11:22 ` [PATCH] configure: check existence of python3 setuptools and dev package David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200601053142.22578-1-tomi.ollila@iki.fi \
--to=tomi.ollila@iki.fi \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).