Troublesome PIL Installation

[Christian Lundh]

Thanks for your help John,

Unfortunately this wasn't the cause. The error related to an
uncomplete Python installation, which actually left the
lib/python2.1/config directory empty, and therefor PIL couldn't find
it's configuration files.

However, with that problem resolved, another problem appeared. But
that is not related to Python/PIL, but more an issue with HP-UX. It
seems as if the implementation of stdio.h and unistd.h conflicts and
some functions is inconsistantly declared. I have seen a lot of
articles on this issue, but no one I have read so far actually have a
solution for the problem.

But I guess we can close the Makefile.pre.in matter for now.

Thanks again for your help

/Christian Lundh


John Hunter <jdhunter at nitace.bsd.uchicago.edu> wrote in message news:<1rbskzt097.fsf at video.bsd.uchicago.edu>...

> Just a guess, but when I unpacked Imaging yesterday and went through
> the install, I noticed that it unpacked in Imaging-1.1.2 (version
> number included) and the default line in Modules/Setup (
> -IExtensions/Imaging/libImaging   ) has no version numbers.  I made a
> symlink:
> 
>  > cd Extensions
>  > ln -s Imaging-1.1.2 Imaging
> 
> but you could also edit Modules/Setup to point to your Imaging
> distribution.
> 
> Hope this helps,
> John Hunter