A better question is why isn't the buildout's lib path explicitly in the env
already?

I would've expected buildout to have done the equivalent of:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<buildout's python lib path>

So, in your case:

export
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/maurits/buildout/python/python-2.4/lib


Or even better:

export
LD_LIBRARY_PATH=/home/maurits/buildout/python/python-2.4/lib:$LD_LIBRARY_PATH

since we probably want buildout bits to get used before system bits.


This is basically the philosophy that's already in play with python's
sys.path, for everything in the buildout's /bin dir.


I.e. buildout's telling python specifically how it should look for python
modules.  Why shouldn't it also tell python how it should look for libs?


...or am I missing something?


regards,

David



On Wed, May 26, 2010 at 11:09, Andreas Jung <[email protected]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Maurits van Rees wrote:
> > Hi all,
> >
> > So, the latest Ubuntu 10.04 (Lucid Lynx) no longer has python2.4
> > packages.  Luckily we have the python buildout, advertised more for the
> > Mac but working on Linux quite well too:
> > http://svn.plone.org/svn/collective/buildout/python
> >
> > PIL even gets installed.  Plone 3 starts up fine when you create a
> > buildout with the python2.4 executable created in this way.  But
> > uploading a jpeg file will work but fail to create a thumbnail, preview,
> > etcetera.  This is because the _imaging module cannot be imported
> > because libjpeg cannot be found:
> >
>
> Are you using the PIL/PilwoTK egg or tried to compile PIL manually?
>
> Andreas
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkv9OZ4ACgkQCJIWIbr9KYyn4ACg2rH85atRu8LwC5Vg0OxsP9mr
> nkwAoJYElIOztVXfkrZ2uMoaQe94Ce4j
> =+0a5
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Product-Developers mailing list
> [email protected]
> http://lists.plone.org/mailman/listinfo/product-developers
>
>
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers

Reply via email to