[GRASS-user] Error building 6.2.0rc2

[Glynn Clements]

Luca Casagrande wrote:

> > > I am building 6.0.2rc2, but in the make log, i found some error; 
> > > as it says i went to the module folder, and issued make.
> > > This is the output:
> > > 
> > > localhost g.access # make
> > > gcc
> > > -L/var/tmp/portage/grass-6.2.0_rc2/work/grass-6.2.0RC2/dist.i386-pc-linux-gnu/lib
> > > -Wl,--export-dynamic
> > > -Wl,-rpath-link,/var/tmp/portage/grass-6.2.0_rc2/work/grass-6.2.0RC2/dist.i386-pc-linux-gnu/lib
> > > -DPACKAGE=\""grassmods"\"
> > > -o /var/tmp/portage/grass-6.2.0_rc2/work/grass-6.2.0RC2/dist.i386-pc-linux-gnu/bin/g.access
> > > OBJ.i386-pc-linux-gnu/exp_perms.o OBJ.i386-pc-linux-gnu/get_perms.o
> > > OBJ.i386-pc-linux-gnu/main.o OBJ.i386-pc-linux-gnu/set_perms.o
> > > -lgrass_gis -lgrass_datetime -lz     -lgrass_vask -lbsd-compat -lm
> > 
> > I would expect to see -lncurses or -lcurses between -lgrass_vask and
> > -lbsd-compat.
> > 
> > What is CURSES set to in include/Make/Platform.make?
> > 
> > -- 
> > Glynn Clements <glynn at gclements.plus.com>
> 
> Thanks for your answer!
> 
> Platfom.make:
> 
> CURSES              =  $(COMPATLIB)
> USE_CURSES          =

Did you use --without-curses? That will cause a lot of modules to fail
to compile.

Although curses can be disabled, it isn't really optional, in the
sense that disabling it will cause a lot of modules to fail to
compile, some of which are fairly important.

The ability to disable curses is included partly for specialised
applications (e.g. web (CGI) applications, where the missing
functionality is either unneeded or replaced with an
application-specific equivalent), and partly for use as an interim
measure when porting GRASS to platforms which don't have curses (e.g. 
native MS-Windows).

If you don't use --without-curses, failure to detect a working curses
library should result in a fatal error from the configure script.

-- 
Glynn Clements <glynn at gclements.plus.com>