GRASS 5.0.2 ebuild is not compiled with any gdal libs. Running r.in.gdal fails. Reproducible: Always Steps to Reproduce: 1. Use r.in.gdal 2. 3. Actual Results: GBBridgeInitialize() failed to find an suitable GDAL .DLL/.so file. The following filenames were searched for: o libgdal.1.1.so o gdal.1.0.so o gdal.so.1.0 o libgdal.so.1 The following locations were searched: o /usr/local/grass5/lib o System default locations. System default locations may be influenced by: LD_LIBRARY_PATH = /usr/local/grass5/lib ERROR: Unable to initialize GDAL bridge Expected Results: Import of a raster map.
i just fixed the motif stuff in grass...
ok. mholzer bumped it last.
The only recommended way to compile GRASS with GDAL support is the use of the flag --with-gdal: configure --with-gdal=/usr/local/bin/gdal-config This flag disables the "GDAL bridge" code and uses the functional interface. In recent GRASS versions (5.3-CVS, 5.7-CVS) the "GDAL bridge" is already disabled and will be removed completely. Hope this helps Markus Neteler GRASS Development Team
hmm, I'm waiting for the Grass 5.7 ebuild ;-)
This is fixed with the latest gdal and grass ebuilds; if I get the chance, I may go back and try some older grass versions (in between).
in current stable gentoo, grass and gdal have a cross dependency that breaks the emerge. Specifically, if have grass and gdal in make.conf then "emerge -u gdal" will attempt to first install grass because of the grass flag, but grass cannot emerge because the gdal flag tells it to go use gdal, which does not yet exist. I find the earlier comments a little confusing re whether it is recommended to NOT use the gdal flag for grass. I'd appreciate someone coming along and clearly noting what the recommended setup/flags are. Thanks.
