Hi Richard,
I have encountered a couple of problems with installing GroupServer
on AMD64. First is an issue with the dependencies that we specify for
GroupServer. The second is with configuration of the PIL buildout. I
would like your advice on both, but the dependencies is the biggest
issue.
On AMD64 one of the dependencies for GroupServer is wrong; more
accurately, the zlib libraries on Ubuntu are a bit odd. I think
zlib1g-dev is either the 32-bit or 64-bit library, depending on
if you are on a 32-bit or 64-bit architecture. I came to this
conclusion after seeing the library lib64z1-dev does not exist on
AMD64, however a 32-bit library lib32z1-dev does. The table below
reflects my understanding:
βββββββββββββββββββββββββββββββββββββββ
zlib-dev in Natty on IA32 and AMD64
IA32 AMD64
βββββββββββββββββββββββββββββββββββββββ
32-bit zlib zlib1g-dev lib32z1-dev
64-bit zlib lib64z1-dev zlib1g-dev
βββββββββββββββββββββββββββββββββββββββ
Do you think the zlib libraries are necessary? If so, we will need to
specify the two alternative sets of dependencies to get GroupServer
installed correctly on AMD64.
β§
On my AMD64 box I originally carried on with only zlib1g-dev. However,
I then encountered a problem with "reportlab", which was called from
some client-specific code. After *much* wailing and gnashing of
teeth I managed to figure out the problem, and the solution. However,
I would appreciate a sanity-check.
My Python Imaging Library (PIL) failed to support⦠what are they
called⦠*images*. Well, just PNG images, to be fair. This is a Bad
Thingβ’, and quite how it ever worked before is a mystery to me. My
solution was to
* Bump the version number,
* Switch the source to the PIL version used by Plone, and
* Add the zlib, which GroupServer builds, to the list of directories
that zc.recipe.custom uses to build.
The PIL specification in dependencies.cfg now looks like this. Is it
sane?
[pil]
recipe = zc.recipe.egg:custom
egg = PIL==1.1.7
find-links = http://dist.plone.org/thirdparty/PIL-1.1.7.tar.gz
include-dirs = ${libjpeg:location}/include
${zlib:location}/include
library-dirs = ${libjpeg:location}/lib
${zlib:location}/lib
rpath = ${libjpeg:location}/lib
${zlib:location}/lib
When I rebuilt GroupServer PIL built with the following:
*** TKINTER support not available
--- JPEG support available
--- ZLIB (PNG/ZIP) support available
*** FREETYPE2 support not available
*** LITTLECMS support not available
My client-specific code now works βΊ
I have encountered a couple of problems with installing GroupServer
on AMD64. First is an issue with the dependencies that we specify for
GroupServer. The second is with configuration of the PIL buildout. I
would like your advice on both, but the dependencies is the biggest
issue.
On AMD64 one of the dependencies for GroupServer is wrong; more
accurately, the zlib libraries on Ubuntu are a bit odd. I think
zlib1g-dev is either the 32-bit or 64-bit library, depending on
if you are on a 32-bit or 64-bit architecture. I came to this
conclusion after seeing the library lib64z1-dev does not exist on
AMD64, however a 32-bit library lib32z1-dev does. The table below
reflects my understanding:
βββββββββββββββββββββββββββββββββββββββ
zlib-dev in Natty on IA32 and AMD64
IA32 AMD64
βββββββββββββββββββββββββββββββββββββββ
32-bit zlib zlib1g-dev lib32z1-dev
64-bit zlib lib64z1-dev zlib1g-dev
βββββββββββββββββββββββββββββββββββββββ
Do you think the zlib libraries are necessary? If so, we will need to
specify the two alternative sets of dependencies to get GroupServer
installed correctly on AMD64.
β§
On my AMD64 box I originally carried on with only zlib1g-dev. However,
I then encountered a problem with "reportlab", which was called from
some client-specific code. After *much* wailing and gnashing of
teeth I managed to figure out the problem, and the solution. However,
I would appreciate a sanity-check.
My Python Imaging Library (PIL) failed to support⦠what are they
called⦠*images*. Well, just PNG images, to be fair. This is a Bad
Thingβ’, and quite how it ever worked before is a mystery to me. My
solution was to
* Bump the version number,
* Switch the source to the PIL version used by Plone, and
* Add the zlib, which GroupServer builds, to the list of directories
that zc.recipe.custom uses to build.
The PIL specification in dependencies.cfg now looks like this. Is it
sane?
[pil]
recipe = zc.recipe.egg:custom
egg = PIL==1.1.7
find-links = http://dist.plone.org/thirdparty/PIL-1.1.7.tar.gz
include-dirs = ${libjpeg:location}/include
${zlib:location}/include
library-dirs = ${libjpeg:location}/lib
${zlib:location}/lib
rpath = ${libjpeg:location}/lib
${zlib:location}/lib
When I rebuilt GroupServer PIL built with the following:
*** TKINTER support not available
--- JPEG support available
--- ZLIB (PNG/ZIP) support available
*** FREETYPE2 support not available
*** LITTLECMS support not available
My client-specific code now works βΊ