configure: error: no suitable Python interpreter found

2,562 views
Skip to first unread message

dpham

unread,
May 25, 2012, 12:24:02 PM5/25/12
to hyperdex-discuss
Hi All,
I'm building hyperdex on CentOS 5.5 and I'm running into this error
when executing the

sudo ./configure --enable-python-bindings --prefix=/opt/hyperdex-0.2b9

the stack trace is

checking whether make sets $(MAKE)... yes
checking for a Python interpreter with version >= 2.6... none
configure: error: no suitable Python interpreter found

CentOS 5.5 has a 2.4 python version so I installed Python 2.7.3 in
the /opt/ directory and confirm that
python is in my path and can be invoked.

python -V returns "Python 2.7.3"

Can you tell me where the configure script is expecting to find the
python interpreter? The strange thing is, I successfully built
hyperdex on CentOS 5.7 and 6.0 but each flavor always presents a new
problem.

Best Regards,
David

Robert Escriva

unread,
May 31, 2012, 10:50:47 AM5/31/12
to hyperdex...@googlegroups.com
Hi David,

I'm not quite sure what's going on here. Can you give me some
information about your setup? I assume you're installing from the
tarball. Where is Python.h in relation to /opt/?

-Robert

dpham

unread,
May 31, 2012, 2:44:24 PM5/31/12
to hyperdex-discuss
Hi Robert,
Unfortunately I cannot send logs or stack traces because I'm working
behind a firewall.
The Python.h is located at /opt/python2.7/include/python2.7/

The problem is that the hyperdex configure script cannot find python
even though
I can invoke it with my user account.

My server is running CentOS 5.5 (Final) which came with Python 2.4.3.
I had to manually update
Python to 2.7.3 using a tarball. Python and hyperdex are installed
under /opt. All hyperdex
dependencies were successfully installed.
directory.

I may try reinstalling python.

Best Regards,
David

Robert Escriva

unread,
Jan 23, 2013, 1:50:23 PM1/23/13
to hyperdex...@googlegroups.com
Hi David,

I'm hoping you've solved this problem already, but a pull request I
received today made me think about it. I had, apparently, been misusing
the version comparison for the Python macro as pointed out by Malthe
Borch.

The comparison should not fail now.

-Robert
Reply all
Reply to author
Forward
0 new messages