[GRASS5] [bug #1837] (grass) redhat-9 incompataibility with all versions of grass5.x.x.x

[Glynn Clements]

Request Tracker wrote:

> Subject: redhat-9 incompataibility with all versions of grass5.x.x.x

> grass-5.0.0

> configure: error: *** Unable to locate PostgreSQL includes.

> grass-5.0.1

> configure: error: *** Unable to locate PostgreSQL includes.

Both of these versions used an "internal" PostgreSQL header which, for
later versions of PostgreSQL, required that you add an additional
directory to the --with-postgres-includes= switch.

This dependency has been removed in 5.0.2. And both 5.0.0 and 5.0.1
can be compiled *if* you use the correct configure switches.

> grass-5.0.2
> ./configure:
> 
> checking for SQLConnect in -lodbc... yes
> checking whether to use FFTW... yes
> checking for location of FFTW includes...
> checking for fftw.h... no
> checking for dfftw.h... no
> configure: error: *** Unable to locate FFTW includes.

Do you have FFTW installed? If not, either install it, or use
--without-fftw (this will disable i.fft, i.zc, i.shape and
r.surf.fractal, all of which need the FFTW library).

> grass-5.0.2
> precompiled for linux:

> GRASS:~ > d.mon start=x1
> ERROR: In main.c: Couldn't get socket path.
> Failed to get socket name for monitor <x1>.
> Problem selecting x1. Will try once more
> Failed to get socket name for monitor <x1>.
> *********************************************************

It's hard to be sure why this is happenning, but possible reasons are
if GRASS is unable to determine your username, or if it can't create
the directory /tmp/grass-<username>, or if the directory exists but it
can't set the permissions correctly.

> grass-5.1.0
> precompiled for linux:

5.1 is a development version, and should be considered "alpha".

> GRASS 5.1.0-cvs:~ > Error in startup script: ps.map: error while loading shared libraries: libpq.so.2: cannot open shared object file: No such file or directory

Either you don't have the PostgreSQL client library, or you don't have
a version which is compatible with the pre-compiled binary package.

-- 
Glynn Clements <glynn.clements at virgin.net>