Skip to content
Prev 15901 / 29559 Next

cannot install rgeos

On Sat, 18 Aug 2012, Martin Ivanov wrote:

            
Both require C++ libraries, and require that they are the same versions as 
the GEOS and GDAL binaries, as well as the rgeos and rgdal binaries. It 
looks as though C++ isn't deployed across the cluster consistently, and 
isn't the same as on your local machine. Start by getting rgdal and rgeos 
installed and running correctly locally.

An alternative is to try to build static binary packages, by removing the 
gdal and geos shared objects, so that the rgeos and rgdal configure steps 
revert to static - read the rgdal/configure.ac file for some indications. 
You'll need GDAL only static, with PROJ.4 static-linked; the same for 
GEOS. This is what is done for OSX; Windows package binaries are also 
static, but do not use configure.ac. For rgeos, you may need to add 
-lstdc++ manually. This isn't at all easy.

For GEOS, despite our using the C API consistently, the structure of GEOS 
itself requires linkage to the C++ GEOS ABI, and to libstdc++, so without 
static linkage, care is required. With rgdal, we do use the C++ API/ABI, 
but argably should go for a GSoC next year to move it to the C API, which 
is less problematic (hopefully).

I'm also curious that cluster use is important, given that neither of the 
packages is multithreaded nor parallelizable. Are you going to run 
simulations? Won't it be easier to re-jig your workflow to pre-process and 
post-process data on a single machine?

Roger