[GRASSLIST:2311] Re: r.in.gdal : Unresolvable problems? -- Solved

[Paul Kelly]

Hello
I'm not sure what your exact problem was here but I spent some time
investigating the r.in.gdal segmentation fault problem a few months ago
and so can offer some contents.

On Wed, 21 Jan 2004, Carl Brown wrote:

> So is there a working step-by-step procedure?
> I have tried the recommended fixes without success up to this point.
> As I understand it now, I should:
>
> Uninstall gdal, but gdal does not have a "make uninstall".
> What should I delete?

I don't see any reason why you should need to uninstall GDAL. And even if
you are upgrading to a new version just install it in the same place and
it will over write the files. The important thing is the 'gdal-config' for
the installation you wish to use. GRASS uses this during compilation to
tell it the correct names of the GDAL libraries and where to look for them
and the header files.

>
> for gdal:
> CFLAGS=-g ./configure --without-grass

That looks fine I think

>
> For GRASS:
> CFLAGS=-g ./configure --with-gdal=/usr/local/bin  (where gdal-config is located)

That isn't right. If gdal-config is in your PATH then just use
--with-gdal, otherwise the argument after the sign should be the full path
to gdal-config, i.e. in your example above it should be
--with-gdal=/usr/local/bin/gdal-config . But if /usr/local/bin is already
in your path then this is not necessary.

>
> Then build gdal again with:
> CFLAGS=-g ./configure --with-grass=???

Well that won't be necessary for use with GRASS and might even break
things if the installed GDAL is no longer the same as the one you compiled
GRASS against *I'm not 100% sure about that). If you need the libgrass
support in GDAL you could maybe keep two separate GDAL installations, one
(without libgrass support) for use with GRASS and another (with libgrass
support) for use with other programs that needed to read GRASS rasters
through GDAL. The argument to --with-gdal would then be more relevant when
compiling GRASS.

>
> The gdal configure --help says to point it to the "libgrass path", but
> libgrass does not exist.

Well if you haven't installed libgrass and don't need it then don't try to
compile GDAL with libgrass support.

I hope some of the above might help put you on the right track.

Paul K