3

I installed sqlite3 using homebrew in order to use the newer version than the system-wide version supplied by OS X.

Now I want to install Python 3.4.3 using pyenv and guide the build process to use the sqlite3 installed by homebrew rather than the OS X's version.

I found this: Compile Python 3.4 with sqlite3, and tried adapting it to work with pyenv, but failed - the installed Python 3.4.3 still links with the OS X sqlite3. The command I tried:

env LD_RUN_PATH="/usr/local/opt" LDFLAGS="-L/usr/local/opt" CPPFLAGS="-I/usr/local/include" pyenv install 3.4.3

What is the correct way of doing it with pyenv?

Community
  • 1
  • 1
skyork
  • 7,113
  • 18
  • 63
  • 103
  • it's a little odd that some of your special paths point to usr-local-**opt** while another to usr-local-**include** – Dima Tisnek Mar 17 '15 at 07:25

1 Answers1

1

Based on https://github.com/yyuu/pyenv/tree/master/plugins/python-build#special-environment-variables

Best match:

PYTHON_CONFIGURE_OPTS and PYTHON_MAKE_OPTS allow you to specify configure and make options for buildling CPython. These variables will be passed to Python only, not any dependent packages (e.g. libyaml).

More general, if needed:

CONFIGURE_OPTS lets you pass additional options to ./configure

Dima Tisnek
  • 11,241
  • 4
  • 68
  • 120
  • 1
    thank you for your answer. I have tried utilizing `PYTHON_CONFIGURE_OPTS` and `PYTHON_MAKE_OPTS`, but they resulted in compiling errors during the Python installation via `pyenv`. – skyork Mar 18 '15 at 03:02