<p>If it involves translating pypy, then I am stuck. This laptop does not have the resources to translate pypy.</p>
<p>The website has said that pil is " known to work " for several releases now. I thought that meant it would be pretty trivial to install.</p>
<p>Jacob</p>
<div class="gmail_quote">On Mar 4, 2012 9:27 AM, "Jacob Finkelman" <<a href="mailto:eh2406@wayne.edu">eh2406@wayne.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks.<br>
<br>
I feel really dumb for having to ask you this… Where do I find<br>
.../ffi_common.h? It does not appear to be in my PYPY-1.8 folder.<br>
<br>
Jacob<br>
<br>
On Sun, Mar 4, 2012 at 8:58 AM, Armin Rigo <<a href="mailto:arigo@tunes.org">arigo@tunes.org</a>> wrote:<br>
> Hi Jacob,<br>
><br>
> Googling around, I found this thread:<br>
><br>
> <a href="http://social.msdn.microsoft.com/Forums/en-SG/vcgeneral/thread/6ca96d26-1765-49d8-85fd-d455795fbb7e" target="_blank">http://social.msdn.microsoft.com/Forums/en-SG/vcgeneral/thread/6ca96d26-1765-49d8-85fd-d455795fbb7e</a><br>
><br>
> It seems related. The basic issue is that "INT8" is already defined,<br>
> possibly as a #define macro, from somewhere inside PIL; then when it<br>
> #includes the standard header, crash. Or maybe it's "UINT8" or<br>
> "SINT8", which are typedefs from<br>
> pypy/translator/c/src/libffi_msvc/ffi_common.h. In the first case,<br>
> the version of PIL you're using wouldn't compile at all on VC++2008<br>
> even on CPython, so it looks unlikely (except in some case like<br>
> Python.h happens not to #include this standard header in CPython, but<br>
> doing so in PyPy). To try to fix the second case, try renaming UINT8<br>
> and SINT8, which are defined in<br>
> ./translator/c/src/libffi_msvc/ffi_common.h and apparently used only<br>
> once in ./translator/c/src/libffi_msvc/ffi.c. (I think I'll rename it<br>
> anyway to avoid such issues.)<br>
><br>
><br>
> A bientôt,<br>
><br>
> Armin.<br>
</blockquote></div>