On Mavericks: $ sudo find / -type f -name \*ffi.h /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/usr/include/ffi/ffi.h /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/ffi/ffi.h /Users/taavi/src/pypy/rpython/translator/c/src/libffi_msvc/ffi.h /usr/local/Cellar/libffi/3.0.13/lib/libffi-3.0.13/include/ffi.h
Some quick googling indicates that yes, /usr/include moved into the platform SDK inside the XCode application. Sounds like one can restore it by installing the command-line tools (from http://stackoverflow.com/questions/19531262/cant-phpize-or-configure-an-extension-in-os-x-10-9-mavericks ): xcode-select --install Now I have a /usr/include again! $ ls /usr/include AssertMacros.h cache.h … I haven't tried building pypy since the upgrade though. On Sat, Oct 26, 2013 at 4:25 AM, Maciej Fijalkowski <fij...@gmail.com> wrote: > Hi Kevin, thanks for the feedback! > > Do you have maybe an idea how to improve the docs? > > about libffi.h - Apple removed /usr/include and moved it somewhere > else, no clue where. I also don't have access to Mavericks so I can't > fix it. > > On Sat, Oct 26, 2013 at 7:18 AM, Kevin Burke <k...@inburke.com> wrote: >> Hey everyone, >> I was trying to compile pypy and made the following mistakes: >> >> - On this page: http://pypy.org/download.html I couldn't figure out whether >> I was supposed to run all three of these commands: >> >> pypy ../../rpython/bin/rpython -Ojit targetpypystandalone # get >> the JIT version >> pypy ../../rpython/bin/rpython -O2 targetpypystandalone # get >> the no-jit version >> pypy ../../rpython/bin/rpython -O2 --sandbox targetpypystandalone # get >> the sandbox version >> >> or just one. >> >> - Once I got it installled I didn't realize there was an additional step >> after pypy-c was created. >> >> - I tried running python package.py -h and that didn't do what I expected >> (show help dialog) >> >> - I tried running package.py with the right options and it hung with this >> message (on both Mac and Centos): >> >> sll_os.ll_os_getenv(sPYPY_GENERATIONGC_NURSERY >> >> The only Google search results for this are an IRC channel from 2 years ago. >> It turned out I didn't want the Sandbox option, I think. >> >> - I tried compiling outside the sandbox and got this error: >> >> raise NoTTY("Cannot start the debugger when stdout is captured.") >> >> It turns out this is a red herring and the real error was way above that: >> >> error: ffi.h: No such file or directory >> >> It would be nice if these were more obvious.. of course I expect to run into >> issues but the errors could be more clear when they are. >> >> Continuing the install process now, will post updates here as I have them. >> >> I am happy to help try and fix these where I can, if you can point me in the >> right direction - I have a fair amount of experience working with new users >> at Twilio. I have also made exactly one commit to Pypy source code: >> https://bitbucket.org/pypy/pypy/commits/665baf750859/ Pypy is a lovely >> project and I'd love to try and help make this process easier. >> >> Best, >> Kevin >> >> -- >> Kevin Burke | Twilio >> phone: 925.271.7005 | kev.inburke.com >> >> _______________________________________________ >> pypy-dev mailing list >> pypy-dev@python.org >> https://mail.python.org/mailman/listinfo/pypy-dev >> > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > https://mail.python.org/mailman/listinfo/pypy-dev -- taa /*eof*/ _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
