[geos-devel] Problem with building 3.0.0rc

[Sean Gillies]

John Cartwright wrote:
> The release version
> (http://geos.refractions.net/downloads/geos-3.0.0.tar.bz2) seems to work
> OK for me w/o the python SWIG bindings.  My system is 64bit RHEL 5.
> 

It was released? Did I miss something?

> By the way what is the status of the python bindings at 3.0?  I couldn't
> get them to compile and recall that they were not actively maintained.
> Can someone confirm?
> 
> Thanks!
> 
> --john
> 

I don't know what the status is.

Sean

> 
> Sean Gillies wrote:
>> I'm encountering a problem with the 3.0 release candidate that blocks a
>> build on my Ubuntu 6.10 i686.
>>
>> "configure --prefix=/tmp; make; make install" bails out here:
>>
>> ...
>> Making install in swig
>> make[1]: Entering directory `/tmp/geos-3.0.0rc5/swig'
>> Making install in python
>> make[2]: Entering directory `/tmp/geos-3.0.0rc5/swig/python'
>> Making install in tests
>> make[3]: Entering directory `/tmp/geos-3.0.0rc5/swig/python/tests'
>> make[4]: Entering directory `/tmp/geos-3.0.0rc5/swig/python/tests'
>> make[4]: Nothing to be done for `install-exec-am'.
>> make[4]: Nothing to be done for `install-data-am'.
>> make[4]: Leaving directory `/tmp/geos-3.0.0rc5/swig/python/tests'
>> make[3]: Leaving directory `/tmp/geos-3.0.0rc5/swig/python/tests'
>> make[3]: Entering directory `/tmp/geos-3.0.0rc5/swig/python'
>> make[4]: Entering directory `/tmp/geos-3.0.0rc5/swig/python'
>> /bin/bash ../../mkinstalldirs
>> /bin/bash ../../mkinstalldirs
>> shift: 49: can't shift that many
>> make[4]: *** [install-pkgpythonPYTHON] Error 2
>> make[4]: Leaving directory `/tmp/geos-3.0.0rc5/swig/python'
>> make[3]: *** [install-am] Error 2
>> make[3]: Leaving directory `/tmp/geos-3.0.0rc5/swig/python'
>> make[2]: *** [install-recursive] Error 1
>> make[2]: Leaving directory `/tmp/geos-3.0.0rc5/swig/python'
>> make[1]: *** [install-recursive] Error 1
>> make[1]: Leaving directory `/tmp/geos-3.0.0rc5/swig'
>> make: *** [install-recursive] Error 1
>>
>> I don't understand why the install-pkgpythonPYTHON target is attempted
>> when I haven't enabled the swig python bindings. Any idea what's up here?
>>
>> Sean
>>