diff options
| -rw-r--r-- | source/blog/2016-10-26-pyenv-compiling-python-with-sqlite-in-nonstandard-location.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/source/blog/2016-10-26-pyenv-compiling-python-with-sqlite-in-nonstandard-location.md b/source/blog/2016-10-26-pyenv-compiling-python-with-sqlite-in-nonstandard-location.md index 0ce3f9e8..96530740 100644 --- a/source/blog/2016-10-26-pyenv-compiling-python-with-sqlite-in-nonstandard-location.md +++ b/source/blog/2016-10-26-pyenv-compiling-python-with-sqlite-in-nonstandard-location.md @@ -6,7 +6,7 @@ date_display: October 26, 2016 This is a quick post sharing a workaround that I needed just now. -I was trying to compile Pythons with pyenv on a RHEL 6.8 cluster. Unfortunately `sqlite-devel` is not installed and I doubt I can convince my sysadmin to install a package for me. The lack of SQLite headers resulted in Pythons without `_sqlite3` which is essential for me. Hitting at SQLite headers from Linuxbrew with `CPATH` did not help either. +I was trying to compile Pythons with pyenv on a RHEL 6.8 cluster. Unfortunately `sqlite-devel` is not installed and I doubt I can convince my sysadmin to install a package for me. The lack of SQLite headers resulted in Pythons without `_sqlite3` which is essential for me. Hinting at SQLite headers from Linuxbrew with `CPATH` did not help either. Digging into CPython source code, turns out that CPython only looks into [a fixed set of paths](https://github.com/python/cpython/blob/59fa72e34da71fb24f52251c1cc88ed3c3b14797/setup.py#L1132-L1138): |