[GRASSLIST:2168] Re: r.in.gdal : Unresolvable problems?

[Markus Neteler]

Ben,

I have downloaded o36080g5.zip map and imported without
problems using

 - GRASS 5.3-CVS
 - GDAL-CVS
 - compiled GRASS with --with-gdal

My suggestion is to polish the system and eliminate all
GDAL libs. Probably there are different versions in
different directories? Check out for
 - gdal.a
 - libgdal*
 - ogr* 
  etc

Good luck

 Markus

On Thu, Jan 08, 2004 at 03:10:41PM -0500, Ben Logan wrote:
> Hi, folks.
> 
> I've been away from the list and GRASS in general for a little while.
> Last time I used GRASS, I was having problems with r.in.gdal
> segfaulting when I tried to import DEMs.
> 
> I have a renewed interest in GIS and wanted to play around with GRASS
> some more.  I downloaded the binary version of Grass (5.0.2) and
> installed it on Knoppix (a Debian-based Live-CD).  GRASS ran okay, but
> I had the same old segfault problem.  I searched the mailing list and
> found that the solution which has worked for others is to compile
> grass from source with --with-gdal.  I downloaded the source (5.0.3)
> and compiled it on my Redhat 8.0 box--I already had gdal-1.1.9
> installed.  It compiled without errors, but I still had the segfault
> problem.  Here are some things I've tried, all ending with the same
> result:
> 
> * Remove gdal from my system and install the binary version of GRASS.
> * Uninstall the binary version, compile gdal-1.1.8 and compile GRASS
>   5.0.3 with --with-gdal.
> * Uninstall (gdal and GRASS), install gdal-1.1.9 and compile GRASS
>   5.0.3 with --with-gdal
> * At some point, I tried using GRASS 5.0.2, but that didn't work
>   either.
> * Install the binary version of GRASS 5.0.2 and replace (symlink) the
>   GRASS version of libgdal.1.1.so with the one installed with gdal.
> 
> Note that the gdal utility programs seem to work fine.  It's just
> r.in.gdal that crashes and burns.
> 
> Here is an example of a DEM and a DRG each of which crash r.in.gdal:
> ftp://gisweb1.radford.edu/dem/DEMs/36080/36080G5.zip
> ftp://gisweb1.radford.edu/drgs/o36080g5.zip
> 
> And I've attached the output from running strace on r.in.gdal when it
> segfaults.  What are all the windoze-style paths in there for?  (I
> gzipped the output so it wasn't so large.)
> 
> This problem has rendered GRASS relatively useless to me because all
> my data is in formats which need r.in.gdal to import them! :-(  And
> the frustrating thing is that it used to all work.  Many moons ago, I
> compiled 5.0.2 and gdal-1.1.8 from source and r.in.gdal worked.  Then
> it suddenly stopped for some reason and I haven't been able to get it
> to work since.  (I don't think upgraded anything between the time it
> worked and stopped working...but I could be wrong.)
> 
> I'd really 'preciate any help anyone could give.  I've tried
> everything I could think of and find on the lists.
> 
> Thanks,
> Ben
> 
> -- 
> Ben Logan
> Google Answers Researcher
> answers.google.com
> When you're searching for information, Google Answers.
> ==============
> OpenPGP Key ID: A1ADD1F0
> Fingerprint: E32C 1CF9 C2FE DFC9 BB5C  A24F 57DB 5679 A1AD D1F0
> Get it from http://cyclist.wblogan.net/benlogan.gpg





-- 
Markus Neteler     <neteler itc it>       http://mpa.itc.it
ITC-irst -  Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18        -       38050 Povo (Trento), Italy