Fix --enable-pythoninterp on systems where python is a symlink to python3. [code]

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Link /usr/bin/python to /usr/bin/python3
2. Run ./configure --enable-pythoninterp

What is the expected output? What do you see instead?
I expect the ./configure script to succeed, but it fails because
the ./configure script does not expect a python3 to be symlinked
to `python`.

What version of the product are you using? On what operating system?
This happens on the current (2012-12-09) tip, everywhere where
`python` is a symlink to `python3`.

Please provide any additional information below.
I have attached an hg-bundle that fixes the ./configure script by
using the `AC_PATH_PROGS` autoconf macro to prefer a `python2`
binary over a `python` one.

Original issue reported on code.google.com by wunderse...@gmail.com on 9 Dec 2012 at 10:50

Attachments:

• configure-systems-with-python2.bundle

[GoogleCodeExporter]

I can't see what is inside the bundle.  Please provide a diff instead.

Original comment by brammool...@gmail.com on 9 Dec 2012 at 1:00

[GoogleCodeExporter]

Sorry, I'm not all that familar with mercurial and wasn't sure what's preferred.

Next time. :)

Original comment by wunderse...@gmail.com on 9 Dec 2012 at 1:15

Attachments:

• configure-systems-with-python2.diff

[GoogleCodeExporter]

Thanks.  See my alternate patch on the vim-dev maillist.

Original comment by brammool...@gmail.com on 9 Dec 2012 at 2:47

[GoogleCodeExporter]

Should be fixed by 7.3.755. Closing

Original comment by chrisbr...@googlemail.com on 30 Sep 2014 at 6:53

• Changed state: Fixed