Michael, everyone,
The solution I think is to test the original GRASS configure script
on a system that does not meet any of the optional dependencies
and make sure that it does not fail on such a system, but rather
switch off compilation of modules that depend on optional stuff.
This version of the configure script should then go into
GRASS CVS and all extensions.
Unfortunately, I have no experience with the configure syntax.
But I would probably be able to find a very basic Linux setup
to test a minimal configuration on.
Maybe someone else could help with it?
Best,
Benjamin
Michael Barton wrote:
So what's the solution? Is there one?
Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State Universityphone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbartonFrom: Benjamin Ducke <benjamin.ducke@ufg.uni-kiel.de>
Organization: CAU
Date: Wed, 28 Jun 2006 09:36:26 +0200
To: Michael Barton <michael.barton@asu.edu>, GRASS devel
<grass-dev@grass.itc.it>
Subject: Re: Issues with advanced viewshed analysis on MacMichael,
this is to do with the fact that I recently updated
the configure script that ships with all extensions
to the latest version from GRASS cvs.
Unfortunately, this script obviously fails if certain
* optional * dependencies are not met.
I think rather than me trying to fix this in the extension
configure scripts, we should fix it for the global
GRASS cvs configure script. I don't think configuring
should fail for anything optional, including postgresql.Best,
--
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