Cool. That fixed it. I think I am getting slowly to the point where I understand all the details of the MinGW compile process. I hope I'll be able to report back with some debugging news concerning the Win32 DBF.EXE deadlocks soon.
Best, Benjamin Paul Kelly wrote: > On Thu, 14 Jun 2007, Benjamin Ducke wrote: > >> I just tried installing the GDAL version contained in the >> wingrass-extralibs package: >> >> http://grass.gdf-hannover.de/wiki/WinGRASS_Current_Status >> >> following the precise steps as outlined here: >> >> http://grass.gdf-hannover.de/wiki/WinGRASS_Current_Status >> >> With a fresh update of GRASS CVS >> >> Still the same configure error: >> >> checking for gdal-config... /usr/local/bin/gdal-config >> checking for GDALOpen... no >> checking for GDALOpen... no >> configure: error: *** couldn't find GDAL >> >> What am I doing wrong? > > Look in config.log to see what the error is and you should be able to > work it out from there. However I suspect you may need to change the > paths at the top of the gdal-config script to match where you have > actually installed it, rather than where I installed it before I > generated wingrass-extralibs.tar.gz. It's not designed to be fool-proof, > just a help to save effort in compiling all the other libraries. > Although maybe long-term we could move away from using the gdal-config > command in the configure script to get away from problems like this. I > think everything its used for should probably be able to be achieved > without it. > > Paul > > -- 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
