[gdal-dev] Makefile problem in GDAL?

2017-03-06 Thread Dr Rainer Woitok
Greetings, having checked out the bookmark "remote/tags/2.1.3" (2017-01-20 08:19:14 + even.roua...@mines-paris.org), I configured GDAL and the ran "make install" just to produce the following error: libtool: compile: g++ -I/home/Rainer/repo/gdal/gdal/port -I/home/Rainer/repo/gdal/gdal/gc

Re: [gdal-dev] Unable to compile Gdal under Cygwin

2015-11-03 Thread Dr Rainer Woitok
Even, On Monday, 2015-11-02 11:14:37 +0100, you wrote: > ... > No, you should point to the directory where "make install" has put the > files, > ie the one that has include and lib subdirectories Ok, here this directory is named "proj4/" and contains (among other things): $ ls proj4/bin

Re: [gdal-dev] Unable to compile Gdal under Cygwin

2015-11-02 Thread Dr Rainer Woitok
Even, On Sunday, 2015-11-01 16:37:42 +0100, you wrote: > ... > As I said before, I'd rather suggest you use --with-static-proj4 instead, > which contrary to what its name suggest, does classic library linking > (dynamic > or static depending on what is available) Am I understanding that corre

Re: [gdal-dev] Unable to compile Gdal under Cygwin

2015-10-11 Thread Dr Rainer Woitok
Hi, On Saturday, 2015-10-10 16:31:50 +0200, I myself wrote: > ... > And lo and behold! the compilation succeeded. Now on to testing: plenty of tests failing due to ERROR 6: Unable to load PROJ.4 library (cygproj-0.dll) Well, the real PROJ.4 library is meanwhile na

Re: [gdal-dev] Unable to compile Gdal under Cygwin

2015-10-10 Thread Dr Rainer Woitok
Even, On Friday, 2015-10-09 19:10:53 +0200, you wrote: > ... > It seems the error is linked to the Python GNM module when GDAL is not > configured --with-gnm. Ok, I thought, if the missing "--with-gnm" option spoils my compilation, I could as well add it. And lo and behold! the compilation suc

[gdal-dev] Unable to compile Gdal under Cygwin

2015-10-09 Thread Dr Rainer Woitok
Greetings, yesterday I cloned the Gdal source repository from https://github.com/OSGeo/gdal.git and converted it to a Mercurial repository, simply because that's the version control software I'm at home with. In Mercurial the most recent commit of the repository looks like this 2015-1