On Wed, Apr 1, 2009 at 6:22 PM, James McManus wrote:
> gdalinfo knows where the /usr/lib64 directory is located, but it is
> expecting files with a .so suffix. I installed libgrass using fedora's yum.
> It does not produce grass libraries with a .so suffix.
As a GRASS developer I confirm Frank's
gdalinfo knows where the /usr/lib64 directory is located, but it is
expecting files with a .so suffix. I installed libgrass using fedora's yum.
It does not produce grass libraries with a .so suffix.
Trying a different approach, I installed grass on /usr/local and recompiled
gdal setting --with-gr
On Wed, Apr 1, 2009 at 4:24 PM, Frank Warmerdam wrote:
> James McManus wrote:
...
>> When I attempt to compile libgrass from source at:
>>
>> http://home.gdal.org/projects/grass/
...
> That libgrass is quite ancient now and I don't think it is suitable for
> use with modern GRASS or even perhaps
James McManus wrote:
When I use gdalinfo on a GRASS raster file I get the following error
message:
error while loading shared libraries: libgrass_dgl.so: cannot open
shared object file: No such file or directory
The libgrass libraries are installed in /usr/lib64 but they all have
.so.6.3.0
When I use gdalinfo on a GRASS raster file I get the following error
message:
error while loading shared libraries: libgrass_dgl.so: cannot open shared
object file: No such file or directory
The libgrass libraries are installed in /usr/lib64 but they all have
.so.6.3.0 suffix's. When I attempt t
