Change:
1. Make sure you have installed the dependencies: * `g++` 4.7 or `clang++` 3.x <del> * `python` 2.6 or later (but not 3.x) </del> <ins> * `python` 2.7 or later (but not 3.x) </ins> * GNU `make` 3.81 or later * `curl` * `git`

Discussion:
The "Building from Source" instructions on the github wiki page specify that the rust compiler requires python 2.6 or later, however the ./configure script says that python 2.7 is required.
We do not have a github wiki anymore, where did you find this?
Hi Steve, I found the github wiki page at: , Steve Klabnik wrote:
I think refers to the README:
Ah ha! Thanks, I will send a fix.
Where in ./configure is 2.7 required? It seems it accepts both 2.6 and 2.7.
Our Python situation is really confusing. The script indicates that Python is needed for LLVM, but LLVM's docs say it only needs Python for its tests, and we (thankfully) don't run LLVM tests. Perhaps there is some flag that enables them, but by default that is not the case. Furthermore, seems to accept Python versions as old as 2.4 (or rather, rejects 2.3 because "LLVM requires Python 2.4-2.7") when provided with a argument, though as found it will look for only 2.6/2.7 in the absence of this argument. But LLVM 2.8's docs state that Python "=2.7" is required (from lurking on the llvm-dev mailing list, I recall that this does not include 3.x). As if all that wasn't bad enough, we have a number of Python scripts in with no easy way to tell what Python version those require. Not all of those scripts are part of the normal build/development process (for example, some generate tables of precomputed constants). At a glance, I saw one use of the statement in which gives us a lower bound of 2.6 for a normal process. It's also quite possibly that some 2.7 features have slipped in. Honestly I would be in favor of just requiring 2.7 regardless of whether anything even needs it. Just to make all this confusion stop.
presently: CentOS 6.2 ships with Python 2.6.6 and depends on that specific version. Be careful not to replace it or bad things will happen. If you need access to a newer version of Python you must compile it yourself and install it side-by-side with the system version.

source: script: checking for python... user defined: /usr/bin/python2.6 checking for python = 2.7... not found configure: error: found python 2.6.6 (/usr/bin/python2.6); required = 2.7 See `' for more details. configure: error: LLVM configure failed , rkruppe wrote:
Ah, this error is from LLVM's configure script, not from Rust's. Ours should be updated to correctly check for 2.7, since LLVM apparently requires it<sup1</sup. Someone could check if our LLVM build even requires Python (as mentioned before, the docs say it's only needed for tests, which we don't run). If not, maybe (if all of Rust's Python scripts work on 2.6) building with Python 2.6 could still be supported.
Just to be clear, is the github site no longer used for Rust? If not, the wiki page should at least be updated to say that it's no longer active, and point users at the current instructions for obtaining and building the rust compiler. , est31 wrote:
There is a difference between the GitHub repository and the GitHub wiki. GitHub offers wikis for the projects it hosts, but Rust does not use that capability any more. Rust still uses and will continue to use GitHub for development, issue tracking, etc. &mdash; only the wiki is not used any more. For comparison, here is a random example of what GitHub wiki looks like:
:+1: for not supporting Python 2.6 (which is no longer maintained by the PSF)