Re: [Zope] Failure to install PIL on a Linux server
Tino Wildenhain schrieb: Dominik Wezel schrieb: Tino, apt-get install python2.3-imaging ready. Thanks anyway, but you probably didn't read the last section of my mail. Unfortunately, I *have* to find a way to do it manually. FYI: It has to do with the way I set up Zope and various other stuff around it. Unfortunately, back then I needed a very upfront version of Zope as yet unavailable through the debian package system, so I chose to set it up manually; this led to the need for a particular python version not available through the debian package system, so I set it up manually. Now the customer needs PIL on this manual setup. Albeit I tried to apt-get it, it didn't integrate at all with the other stuff. Needlesds to say I don't want to setup another python version on the same server, as mass storage capacity *is* an issue here). Hm. You can perfectly run a source build of Zope on package-python from debian. Testing has 2.3.5-6, which is perfectly usable. Ah and stable has 2.3.5 too. Btw. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Failure to install PIL on a Linux server
Dominik Wezel schrieb: Tino, apt-get install python2.3-imaging ready. Thanks anyway, but you probably didn't read the last section of my mail. Unfortunately, I *have* to find a way to do it manually. FYI: It has to do with the way I set up Zope and various other stuff around it. Unfortunately, back then I needed a very upfront version of Zope as yet unavailable through the debian package system, so I chose to set it up manually; this led to the need for a particular python version not available through the debian package system, so I set it up manually. Now the customer needs PIL on this manual setup. Albeit I tried to apt-get it, it didn't integrate at all with the other stuff. Needlesds to say I don't want to setup another python version on the same server, as mass storage capacity *is* an issue here). Hm. You can perfectly run a source build of Zope on package-python from debian. Testing has 2.3.5-6, which is perfectly usable. Thats why I'm using debian too - to save me from all the hassle with source depencies while using source where I really want it :-) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Failure to install PIL on a Linux server
Tino, apt-get install python2.3-imaging ready. Thanks anyway, but you probably didn't read the last section of my mail. Unfortunately, I *have* to find a way to do it manually. FYI: It has to do with the way I set up Zope and various other stuff around it. Unfortunately, back then I needed a very upfront version of Zope as yet unavailable through the debian package system, so I chose to set it up manually; this led to the need for a particular python version not available through the debian package system, so I set it up manually. Now the customer needs PIL on this manual setup. Albeit I tried to apt-get it, it didn't integrate at all with the other stuff. Needlesds to say I don't want to setup another python version on the same server, as mass storage capacity *is* an issue here). Doing it right just now would be a hazard to a running server; I'm going to wait for a necessary release change and then maybe set it up the debian way. For now, I need to go the way manually (or rather by foot =:) -- So long, Dominik ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Failure to install PIL on a Linux server
Dominik Wezel schrieb: Hi all I'm aware that PIL is not easy to install, primarily due to the prerequisites. I've studied and applied as well as possible http://mail.zope.org/pipermail/zope/2002-December/128364.html and http://www.zope.org/Members/regebro/PIL_zope/, both of which seem slightly medieval: the setup and test processes are very different today. I didn't find any other information pertaining to my problem, so I considered this posting. I hope I'm on the right list here. Setup = - debian 3.1 (sarge) on a UML (user mode linux) dedicated ZOPE instance apt-get install python2.3-imaging ready. - /usr/src/Imaging-1.1.5 (from Imaging-1.1.5.tar.gz, 2005-03-28) - /usr/src/freetype-2.1.10 (from freetype-2.1.10.tar.bz2, 2005-06-12) - /usr/src/jpeg-6b (from jpegsrc.v6b.tar.gz, 2005-03-28) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Failure to install PIL on a Linux server
Hi all
I'm aware that PIL is not easy to install, primarily due to the
prerequisites. I've studied and applied as well as possible
http://mail.zope.org/pipermail/zope/2002-December/128364.html and
http://www.zope.org/Members/regebro/PIL_zope/, both of which seem
slightly medieval: the setup and test processes are very different
today. I didn't find any other information pertaining to my problem, so
I considered this posting. I hope I'm on the right list here.
Setup
=
- debian 3.1 (sarge) on a UML (user mode linux) dedicated ZOPE instance
- /usr/src/Imaging-1.1.5 (from Imaging-1.1.5.tar.gz, 2005-03-28)
- /usr/src/freetype-2.1.10 (from freetype-2.1.10.tar.bz2, 2005-06-12)
- /usr/src/jpeg-6b (from jpegsrc.v6b.tar.gz, 2005-03-28)
Symptom
===
[EMAIL PROTECTED]:/usr/src/Imaging-1.1.5# python setup.py build_ext -i
|running build_ext
|
|PIL 1.1.5 BUILD SUMMARY
|
|version 1.1.5
|platform linux2 2.3.5 (#1, Apr 22 2005, 15:12:06)
| [GCC 3.3.5 (Debian 1:3.3.5-8)]
|
|*** TKINTER support not available
|--- JPEG support ok
|--- ZLIB (PNG/ZIP) support ok
|--- FREETYPE2 support ok
|
|To add a missing option, make sure you have the required
|library, and set the corresponding ROOT variable in the
|setup.py script.
|
|To check the build, run the selftest.py script.
[EMAIL PROTECTED]:/usr/src/Imaging-1.1.5# python selftest.py
|*
|Failure in example: _info(Image.open("Images/lena.jpg"))
|from line #24 of selftest.testimage
|Exception raised:
|Traceback (most recent call last):
| File "./doctest.py", line 499, in _run_examples_inner
|exec compile(source, "", "single") in globs
| File "", line 1, in ?
| File "./selftest.py", line 21, in _info
|im.load()
| File "PIL/ImageFile.py", line 180, in load
|d = Image._getdecoder(self.mode, d, a, self.decoderconfig)
| File "PIL/Image.py", line 328, in _getdecoder
|raise IOError("decoder %s not available" % decoder_name)
|IOError: decoder jpeg not available
|1 items had failures:
| 1 of 55 in selftest.testimage
|***Test Failed*** 1 failures.
|*** 1 tests of 55 failed.
It looks like JPEG support is enabled, but still the selftest doesn't
find the decoder.
Additional Info
===
In /usr/src/Imaging-1.1.5/setup.py
#
# Library pointers.
#
FREETYPE_ROOT = "/usr/local/lib"
JPEG_ROOT = "/usr/lib"
TIFF_ROOT = None
ZLIB_ROOT = None
TCL_ROOT = None
[EMAIL PROTECTED]:/usr/src/Imaging-1.1.5# ls /usr/local/lib
|total 4168
|-rw-r--r-- 1 root staff 2544356 Jun 27 18:08 libfreetype.a
|-rwxr-xr-x 1 root staff 824 Jun 27 18:08 libfreetype.la
|lrwxrwxrwx 1 root staff 20 Jun 27 18:08 libfreetype.so ->
libfreetype.so.6.3.8
|lrwxrwxrwx 1 root staff 20 Jun 27 18:08 libfreetype.so.6 ->
libfreetype.so.6.3.8
|-rwxr-xr-x 1 root staff 1546147 Jun 27 18:08 libfreetype.so.6.3.8
|-rw-r--r-- 1 root staff 162324 Aug 23 09:37 libjpeg.a
|drwxr-sr-x 2 root staff 80 Jun 27 18:08 pkgconfig
|drwxrwsr-x 3 root staff 80 Jun 17 16:05 python2.3
[EMAIL PROTECTED]:/usr/src/Imaging-1.1.5# ls /usr/local/lib
|
|-rw-r--r-- 1 root root 161160 Mar 2 13:26 libjpeg.a
|-rw-r--r-- 1 root root802 Mar 2 13:26 libjpeg.la
|lrwxrwxrwx 1 root root 17 Aug 18 15:26 libjpeg.so ->
libjpeg.so.62.0.0
|lrwxrwxrwx 1 root root 17 Jun 17 17:54 libjpeg.so.62 ->
libjpeg.so.62.0.0
|-rwxr-xr-x 1 root root 140022 Jun 17 17:54 libjpeg.so.62.0.0
|
[EMAIL PROTECTED]:/usr/src/Imaging-1.1.5# ld -L/usr/lib -ljpeg -nostdlib
|ld: warning: libc.so.6, needed by /usr/lib/libjpeg.so, not found (try
|using -rpath or -rpath-link)
|ld: warning: cannot find entry symbol _start; not setting start address
|/usr/lib/libjpeg.so: undefined reference to [EMAIL PROTECTED]'
|/usr/lib/libjpeg.so: undefined reference to [EMAIL PROTECTED]'
|/usr/lib/libjpeg.so: undefined reference to [EMAIL PROTECTED]'
|/usr/lib/libjpeg.so: undefined reference to [EMAIL PROTECTED]'
|/usr/lib/libjpeg.so: undefined reference to [EMAIL PROTECTED]'
|/usr/lib/libjpeg.so: undefined reference to [EMAIL PROTECTED]'
|/usr/lib/libjpeg.so: undefined reference to [EMAIL PROTECTED]'
|/usr/lib/libjpeg.so: undefined reference to [EMAIL PROTECTED]'
|/usr/lib/libjpeg.so: undefined reference to [EMAIL PROTECTED]'
|/usr/lib/libjpeg.so: undefined reference to [EMAIL PROTECTED]'
|/usr/lib/libjpeg.so: undefined reference to [EMAIL PROTECTED]'
|/usr/lib/libjpeg.so: undefined reference to [EMAIL PROTECTED]'
|/usr/lib/libjpeg.so: undefined reference to [EMAIL PROTECTED]'
|/usr/lib/libjpeg.so: undefined reference to [EMAIL PROTECTED]'
[EMAIL PROTECTED]:/usr/src/Imaging-1.1.5#
