Aha, looks like I needed to point C_INCLUDE_PATH to the directory with my custom sqlite.h, all is well on Centos now
-- Kevin Burke | Twilio phone: 925.271.7005 | kev.inburke.com On Sat, Oct 26, 2013 at 7:53 AM, Kevin Burke <k...@inburke.com> wrote: > Hi Maciej, > I should note - I'm on Mountain Lion so libffi.h is not the issue at the > moment - currently trying to compile this on Centos get the #include > <sqlite3.h> in _sqlite3.py to find my custom sqlite3.h and not the one in > /usr/lib. > > Here is the compile script I am using: > > https://gist.github.com/kevinburke/7170273 > > > -- > Kevin Burke | Twilio > phone: 925.271.7005 | kev.inburke.com > > > On Sat, Oct 26, 2013 at 7:46 AM, Armin Rigo <ar...@tunes.org> wrote: > >> Hi Kevin, >> >> Thanks for this report ! A quick note though: >> >> On Sat, Oct 26, 2013 at 7:18 AM, Kevin Burke <k...@inburke.com> wrote: >> > - Once I got it installled I didn't realize there was an additional step >> > after pypy-c was created. >> >> Note that this step, "package.py", is not required to run the pypy-c >> executable. It's merely a tool that packs all files needed for >> system-wide installation. It also prebuilds a few cffi modules. The >> alternative is to simply use the pypy-c where it is (pypy/goal/pypy-c) >> instead, if you don't need it to be installed system-wide. Symlinks >> pointing to pypy/goal/pypy-c work fine. >> >> >> A bientôt, >> >> Armin. >> > >
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev