Hamish wrote: > Benjamin Ducke wrote: >> 2. However, the README is not clear on whether GRASS first needs to be >> compiled w/o GDAL support firdst, but I assume it has to, because it >> won't be able to find GDALOpen and the configure script aborts: > .. >> 3. Fair enough, BUT: with the current CVS version, it seems impossible >> to compile GRASS without GDAL support, as compilation in >> lib/vector/Vlib aborts, even if I specify --without-gdal: > > GDAL is now a formal dependency. compiling without it is a bad idea. > > > the order should be: > 1. compile & install GDAL without grass support > 2. compile & install GRASS linking to the new GDAL > 3. compile & install GDAL's GRASS plugin linking to the new GRASS.
Step 1: OK Step 2: Fails: checking for gdal-config... /usr/local/bin/gdal-config checking for GDALOpen... no checking for GDALOpen... no configure: error: *** couldn't find GDAL Would this be the time to remove --without-gdal from the configure script? Best, Benjamin -- Benjamin Ducke, M.A. Archäoinformatik (Archaeoinformation Science) Institut für Ur- und Frühgeschichte (Inst. of Prehistoric and Historic Archaeology) Christian-Albrechts-Universität zu Kiel Johanna-Mestorf-Straße 2-6 D 24098 Kiel Germany Tel.: ++49 (0)431 880-3378 / -3379 Fax : ++49 (0)431 880-7300 www.uni-kiel.de/ufg _______________________________________________ grass-dev mailing list [email protected] http://grass.itc.it/mailman/listinfo/grass-dev
