[GRASS5] 5.1: autoconf problem with undefined macro

Paul Kelly paul-grass at stjohnspoint.co.uk
Thu Apr 10 04:54:23 EDT 2003

Hello Markus

On Thu, 10 Apr 2003, Markus Neteler wrote:

> Hi,
> currently I am merging the recent PROJ4 updates into GRASS 5.1.
> Due to the requirements of PROJ4/CVS we had to upgrade 'autoconf'.

An interesting anecdote: when I added the PROJ options to the configure
script for 5.0 it was my first experience using autoconf. Any 2.5x
versions I tried ran OK (sometimes there were warnings though) but the
configure script they generated wouldn't run; had errors somewhere halfway
down nowhere near my changes. So I downgraded to 2.13 as I could see it had
been used in the current configure script in CVS and it worked fine.

I didn't merge all my changes into 5.1 because I wasn't sure about the
different Makefile system. I actually think it would be a good idea to
remove the local copy of PROJ.4 from 5.1 and make the requirement of an
external libproj an absolute dependency. The Makefile for the proj library
in 5.1 would be quite simple then and only need to compile get_proj.c and
do_proj.c I think, along with the datum shift files and any other stuff.
We wouldn't need to set GPROJLIBOBJS and USE_PROJ in the configure script
then. And we wouldn't need the separate gproj_api.h; gprojects.h would
just unconditionally include proj_api.h from the external PROJ.4

Does this sound like a good idea? I can have a look at fixing it up after
the configure script is sorted out.


More information about the grass-dev mailing list