Skip to content

Fail to configure without an LLVM-friendly Python #2722

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 26, 2012

Conversation

bstrie
Copy link
Contributor

@bstrie bstrie commented Jun 26, 2012

This addresses issue #2720. According to LLVM's documentation, it requires a
version of Python between 2.4 and 2.7. Without the proper version, LLVM fails
to build with cryptic errors. Prior to this commit, the configure script
checked for the python command in the environment, but didn't actually check
the version, which can cause problems e.g. on Linux distros where the default
is Python 3. Now the configure script always prefers to select a more specific
version of Python when available, in the order python2.7 > python2.6 >
python2 > python, and will always check to ensure that the interpreter's
version is in the correct range.

This addresses issue rust-lang#2720. According to LLVM's documentation, it requires a
version of Python between 2.4 and 2.7. Without the proper version, LLVM fails
to build with cryptic errors. Prior to this commit, the configure script
checked for the `python` command in the environment, but didn't actually check
the version, which can cause problems e.g. on Linux distros where the default
is Python 3. Now the configure script always prefers to select a more specific
version of Python when available, in the order `python2.7` > `python2.6` >
`python2` > `python`, and will always check to ensure that the interpreter's
version is in the correct range.
brson added a commit that referenced this pull request Jun 26, 2012
Fail to configure without an LLVM-friendly Python
@brson brson merged commit c904927 into rust-lang:incoming Jun 26, 2012
@brson
Copy link
Contributor

brson commented Jun 26, 2012

Thanks!

celinval pushed a commit to celinval/rust-dev that referenced this pull request Jun 4, 2024
1. Build and run regression tests, and create a labelled PR (Z-BenchCI) when these pass.
2. File an issue instead of creating a PR when either of the checks fail.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants