[pypy-dev] How to get PIL to install?

[Jacob Finkelman]

If it involves translating pypy, then I am stuck. This laptop does not have
the resources to translate pypy.

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.

Jacob
On Mar 4, 2012 9:27 AM, "Jacob Finkelman" <eh2406 at wayne.edu> wrote:

> Thanks.
>
> I feel really dumb for having to ask you this… Where do I find
> .../ffi_common.h? It does not appear to be in my PYPY-1.8 folder.
>
> Jacob
>
> On Sun, Mar 4, 2012 at 8:58 AM, Armin Rigo <arigo at tunes.org> wrote:
> > Hi Jacob,
> >
> > Googling around, I found this thread:
> >
> >
> http://social.msdn.microsoft.com/Forums/en-SG/vcgeneral/thread/6ca96d26-1765-49d8-85fd-d455795fbb7e
> >
> > It seems related.  The basic issue is that "INT8" is already defined,
> > possibly as a #define macro, from somewhere inside PIL; then when it
> > #includes the standard header, crash.  Or maybe it's "UINT8" or
> > "SINT8", which are typedefs from
> > pypy/translator/c/src/libffi_msvc/ffi_common.h.  In the first case,
> > the version of PIL you're using wouldn't compile at all on VC++2008
> > even on CPython, so it looks unlikely (except in some case like
> > Python.h happens not to #include this standard header in CPython, but
> > doing so in PyPy).  To try to fix the second case, try renaming UINT8
> > and SINT8, which are defined in
> > ./translator/c/src/libffi_msvc/ffi_common.h and apparently used only
> > once in ./translator/c/src/libffi_msvc/ffi.c.  (I think I'll rename it
> > anyway to avoid such issues.)
> >
> >
> > A bientôt,
> >
> > Armin.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20120305/0e0caa44/attachment.html>