[gdal-dev] GDAL / Python and PPC

[Sean Gillies]

Brian Hamlin wrote:
> 
> On Jan 5, 2008, at 6:01 PM, Sean Gillies wrote:
> 
>> Brian Hamlin wrote:
>>> ...no python...
>>
>> [ setuptools install instructions....]
>>
>> Howard has put a ton of work into it. Should just plain work and build
>> numpy for you as well.
>>
> 
> well, that sounded good, but, no go..
> 
> ===========
> pbg42-2;/users/shared/srcs/gdal-trunk jspace4 sudo python -m
> easy-install 'gdal'
> password;
> searching for gdal
> reading http;//cheeseshop.python.org/pypi/gdal/
> reading http;//www.gdal.org
> reading http;//cheeseshop.python.org/pypi/gdal/1.5.0
> best match; gdal 1.5.0
> downloading
> http;//pypi.python.org/packages/source/g/gdal/gdal-1.5.0.tar.gz3md5=a7fcc5ec9c1719aa7b3aba1cd7c9c1e7
> 
> processing gdal-1.5.0.tar.gz
> running gdal-1.5.0/setup.py -q bdist-egg --dist-dir
> /tmp/easy-install-078ffx/gdal-1.5.0/egg-dist-tmp-ctpbwq
> numpy include
> /library/frameworks/python.framework/versions/2.5/lib/python2.5/site-packages/numpy/core/include
> 

Like William said, easy_install won't work if GDAL is installed in a
non-standard location that isn't also specified in the package's
setup.cfg file. The way my Gdawg buildout
(http://zcologia.com/news/638/replicable-python-geoprocessing-environments/)
works is to fetch the GDAL package from PyPI and then modify the
setup.cfg file. In your case you'll need to either do that, adding your
own particular header locations to the include-dirs parameter and your
library locations to the library-dirs parameter -- or use William's
binaries.

There were other warnings and errors in your post that I didn't
recognize, so I can't guarantee that the above will work. Could be some
other issues as well.

Sean