Currently, if you have python and swig installed, gpgme builds the python extensions. There is no way to turn this off, it would be great if there was.
Workaround: add ac_cv_path_SWIG= to the configure command line (setting an internal configure variable).
I just tried this, but this doesn't disable the detection, and if that fails, the configure script stops:
checking for swig... /usr/pkg/bin/swig
checking for a Python interpreter with version >= 2.7... python2.7
checking for python2.7... /usr/pkg/bin/python2.7
checking for python2.7 version... 2.7
checking for python2.7 platform... netbsd7
checking for python2.7 script directory... ${prefix}/lib/python2.7/site-packages
checking for python2.7 extension module directory... ${exec_prefix}/lib/python2.7/site-packages
checking for python2.7... (cached) /usr/pkg/bin/python2.7
checking for a version of Python >= '2.1.0'... yes
checking for the distutils Python package... yes
checking for Python include path... -I/usr/pkg/include/python2.7
checking for Python library path... -L/usr/pkg/lib -lpython2.7
checking for Python site-packages path... /usr/pkg/lib/python2.7/site-packages
checking python extra libraries... -lutil -lm
checking python extra linking flags... -Wl,--export-dynamic
checking consistency of all components of python development environment... no
configure: WARNING:
Could not link test program to Python. Maybe the main Python library has been
installed in some non-standard library path. If so, pass it to configure,
via the LDFLAGS environment variable.
Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib"
============================================================================
You probably have to install the development version of the Python package
for your distribution. The exact name of this package varies among them.
============================================================================
checking for a Python interpreter with version >= 3.4... none
configure: error: no suitable Python interpreter found
*** Error code 1