[GRASS-user] updating from GRASS from svn Unable to locate curses includes

GRASS GRASS user
1

Hi,

I have installed grass63 fro les-ejk repo on a gutsy. I then checkout
from svn the releasebranch_6_3 rev. 31664

Know doing:
./configure ...

I get this error:
Unable to locate curses includes.

Any ideas?

maning

--
|---------|----------------------------------------------------------|
| __.-._ |"Ohhh. Great warrior. Wars not make one great." -Yoda |
| '-._"7' |"Freedom is still the most radical idea of all" -N.Branden|
| /'.-c |Linux registered user #402901, http://counter.li.org/ |
| | /T |http://esambale.wikispaces.com|
| _)_/LI
|---------|----------------------------------------------------------|

2

the config.log says:

configure:5411: checking whether to use Curses
configure:5430: checking for curses.h
configure:5438: gcc -E conftest.c >/dev/null 2>conftest.out
configure:5434:20: error: curses.h: No such file or directory
configure: failed program was:
#line 5433 "configure"
#include "confdefs.h"
#include <curses.h>

On Tue, Jun 10, 2008 at 6:21 PM, maning sambale
<emmanuel.sambale@gmail.com> wrote:

Hi,

I have installed grass63 fro les-ejk repo on a gutsy. I then checkout
from svn the releasebranch_6_3 rev. 31664

Know doing:
./configure ...

I get this error:
Unable to locate curses includes.

Any ideas?

maning

--
|---------|----------------------------------------------------------|
| __.-._ |"Ohhh. Great warrior. Wars not make one great." -Yoda |
| '-._"7' |"Freedom is still the most radical idea of all" -N.Branden|
| /'.-c |Linux registered user #402901, http://counter.li.org/ |
| | /T |http://esambale.wikispaces.com|
| _)_/LI
|---------|----------------------------------------------------------|

--
|---------|----------------------------------------------------------|
| __.-._ |"Ohhh. Great warrior. Wars not make one great." -Yoda |
| '-._"7' |"Freedom is still the most radical idea of all" -N.Branden|
| /'.-c |Linux registered user #402901, http://counter.li.org/ |
| | /T |http://esambale.wikispaces.com|
| _)_/LI
|---------|----------------------------------------------------------|

3

maning sambale

> I have installed grass63 fro les-ejk repo on a gutsy.
> I then checkout from svn the releasebranch_6_3 rev. 31664
>
> Know doing:
> ./configure ...
>
> I get this error:
> Unable to locate curses includes.

...

the config.log says:

configure:5411: checking whether to use Curses
configure:5430: checking for curses.h
configure:5438: gcc -E conftest.c >/dev/null
2>conftest.out
configure:5434:20: error: curses.h: No such file or
directory
configure: failed program was:
#line 5433 "configure"
#include "confdefs.h"
#include <curses.h>

you are missing the curses -dev package:

debian$ apt-file search include/curses.h
libncurses5-dev: usr/include/curses.h

more generally you will need all the "Build-depends" packages:
http://svn.debian.org/wsvn/pkg-grass/packages/grass/trunk/debian/control?op=file

Hamish

4

Thanks Hamish.

Following the link

http://svn.debian.org/wsvn/pkg-grass/packages/grass/trunk/debian/control?op=file

I installed all dependencies from hardy's default repo.

The configure logs this tells me:
configure:8436: checking whether to use Tcl/Tk
configure:8456: checking for location of Tcl/Tk includes
configure:8482: checking for tcl.h
configure:8490: gcc -E conftest.c >/dev/null 2>conftest.out
configure:8486:17: error: tcl.h: No such file or directory

AFAIK, I installed tcl/tk 8.4 and dev

cheers,

maning

--
|---------|----------------------------------------------------------|
| __.-._ |"Ohhh. Great warrior. Wars not make one great." -Yoda |
| '-._"7' |"Freedom is still the most radical idea of all" -N.Branden|
| /'.-c |Linux registered user #402901, http://counter.li.org/ |
| | /T |http://esambale.wikispaces.com|
| _)_/LI
|---------|----------------------------------------------------------|

5

maning:

Following the link
http://svn.debian.org/wsvn/pkg-grass/packages/grass/trunk/debian/control?op=file
I installed all dependencies from hardy's default repo.

The configure logs this tells me:
configure:8436: checking whether to use Tcl/Tk
configure:8456: checking for location of Tcl/Tk includes
configure:8482: checking for tcl.h
configure:8490: gcc -E conftest.c >/dev/null
2>conftest.out
configure:8486:17: error: tcl.h: No such file or directory

AFAIK, I installed tcl/tk 8.4 and dev

for debian/ubuntu ./configure look in the "rules" file:
http://svn.debian.org/wsvn/pkg-grass/packages/grass/trunk/debian/rules?op=file

from that you can put together that you need --with-tcltk-includes=

fwiw this is what I use on debian/etch:

renice +17 -p $$
CFLAGS="-ggdb -Wall -Werror-implicit-function-declaration" \
  ./configure \
    --with-tcltk-includes=/usr/include/tcl8.4 --with-cairo \
    --with-motif --with-python=/usr/bin/python2.4-config \
    --with-readline --with-cxx --with-odbc --with-sqlite \
    --with-freetype --with-freetype-includes=/usr/include/freetype2 \
    --without-postgres --with-proj-share=/usr/share/proj \
    --with-ffmpeg --with-ffmpeg-includes=/usr/include/ffmpeg \
    2>&1 | tee config_log.txt
make

using the .deb buildpackage tools is probably much much easier. I do it by hand because I'm recompiling little bits of the code lots.

these instructions should help:
http://grass.osgeo.org/wiki/Compile_and_Install#Platform_Specific_Notes

one thing there I don't understand: it recommends to do:
  CFLAGS="-g" LDFLAGS="-s" ./configure

-g adds debugging hooks, but -s strips away debug messages. ???
(to quote tom waits: the large print giveth and the small print taketh away)

Hamish

6

Hamish wrote:

these instructions should help:
http://grass.osgeo.org/wiki/Compile_and_Install#Platform_Specific_Notes

one thing there I don't understand: it recommends to do:
  CFLAGS="-g" LDFLAGS="-s" ./configure

-g adds debugging hooks, but -s strips away debug messages. ???
(to quote tom waits: the large print giveth and the small print taketh away)

The LDFLAGS=-s part is bogus.

It used to be a common recommendation to counteract the fact that
configure defaults to "-g -O2" if the compiler is gcc. You wouldn't
use -s if you actually want the debug info.

Also, stripping the debug info is a false economy unless you're
seriously short of hard disk space. If you have your own PC (and it
doesn't belong in a museum), your disk space is likely to be measured
in hundreds of gigabytes, of which binaries (libraries and
executables) might account for around a gigabyte if *everything* is
built with debug info.

The only cases where stripping debug info makes sense is if you're
using a shared server with a miniscule quota, or if you're building a
binary distribution and you really need to minimise the size (FWIW, I
keep the debug info for the Cygwin packages).

For normal use, stick with "-g -O2". That produces optimised binaries
but keeps the debug info just in case you need to do minimal debugging
(e.g. make sense of a core file). If you want to actually debug the
program (set breakpoints, single step, examine variables etc), then
you need to drop the -O2, as it will result in object code which bears
little relation to the actual source code, and can only be debugged in
the most superficial sense.

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

7

Wohoo! Now it running.

One last question, I have checked out from svn the grass-addons
particularly the imagery. How do I add them in the compilation?

cheers,
maning

On Wed, Jun 11, 2008 at 12:28 PM, Glynn Clements
<glynn@gclements.plus.com> wrote:

Hamish wrote:

these instructions should help:
http://grass.osgeo.org/wiki/Compile_and_Install#Platform_Specific_Notes

one thing there I don't understand: it recommends to do:
  CFLAGS="-g" LDFLAGS="-s" ./configure

-g adds debugging hooks, but -s strips away debug messages. ???
(to quote tom waits: the large print giveth and the small print taketh away)

The LDFLAGS=-s part is bogus.

It used to be a common recommendation to counteract the fact that
configure defaults to "-g -O2" if the compiler is gcc. You wouldn't
use -s if you actually want the debug info.

Also, stripping the debug info is a false economy unless you're
seriously short of hard disk space. If you have your own PC (and it
doesn't belong in a museum), your disk space is likely to be measured
in hundreds of gigabytes, of which binaries (libraries and
executables) might account for around a gigabyte if *everything* is
built with debug info.

The only cases where stripping debug info makes sense is if you're
using a shared server with a miniscule quota, or if you're building a
binary distribution and you really need to minimise the size (FWIW, I
keep the debug info for the Cygwin packages).

For normal use, stick with "-g -O2". That produces optimised binaries
but keeps the debug info just in case you need to do minimal debugging
(e.g. make sense of a core file). If you want to actually debug the
program (set breakpoints, single step, examine variables etc), then
you need to drop the -O2, as it will result in object code which bears
little relation to the actual source code, and can only be debugged in
the most superficial sense.

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

--
|---------|----------------------------------------------------------|
| __.-._ |"Ohhh. Great warrior. Wars not make one great." -Yoda |
| '-._"7' |"Freedom is still the most radical idea of all" -N.Branden|
| /'.-c |Linux registered user #402901, http://counter.li.org/ |
| | /T |http://esambale.wikispaces.com|
| _)_/LI
|---------|----------------------------------------------------------|

8

Got it working now including the add-ons thanks to all your help. It
seems the compile and install page says it all:
http://grass.osgeo.org/wiki/Compile_and_Install#Configure_options_and_their_meanings

I just need to understand how it works.

cheers,
maning

On Wed, Jun 11, 2008 at 1:05 PM, maning sambale
<emmanuel.sambale@gmail.com> wrote:

Wohoo! Now it running.

One last question, I have checked out from svn the grass-addons
particularly the imagery. How do I add them in the compilation?

cheers,
maning

On Wed, Jun 11, 2008 at 12:28 PM, Glynn Clements
<glynn@gclements.plus.com> wrote:

Hamish wrote:

these instructions should help:
http://grass.osgeo.org/wiki/Compile_and_Install#Platform_Specific_Notes

one thing there I don't understand: it recommends to do:
  CFLAGS="-g" LDFLAGS="-s" ./configure

-g adds debugging hooks, but -s strips away debug messages. ???
(to quote tom waits: the large print giveth and the small print taketh away)

The LDFLAGS=-s part is bogus.

It used to be a common recommendation to counteract the fact that
configure defaults to "-g -O2" if the compiler is gcc. You wouldn't
use -s if you actually want the debug info.

Also, stripping the debug info is a false economy unless you're
seriously short of hard disk space. If you have your own PC (and it
doesn't belong in a museum), your disk space is likely to be measured
in hundreds of gigabytes, of which binaries (libraries and
executables) might account for around a gigabyte if *everything* is
built with debug info.

The only cases where stripping debug info makes sense is if you're
using a shared server with a miniscule quota, or if you're building a
binary distribution and you really need to minimise the size (FWIW, I
keep the debug info for the Cygwin packages).

For normal use, stick with "-g -O2". That produces optimised binaries
but keeps the debug info just in case you need to do minimal debugging
(e.g. make sense of a core file). If you want to actually debug the
program (set breakpoints, single step, examine variables etc), then
you need to drop the -O2, as it will result in object code which bears
little relation to the actual source code, and can only be debugged in
the most superficial sense.

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

--
|---------|----------------------------------------------------------|
| __.-._ |"Ohhh. Great warrior. Wars not make one great." -Yoda |
| '-._"7' |"Freedom is still the most radical idea of all" -N.Branden|
| /'.-c |Linux registered user #402901, http://counter.li.org/ |
| | /T |http://esambale.wikispaces.com|
| _)_/LI
|---------|----------------------------------------------------------|

--
|---------|----------------------------------------------------------|
| __.-._ |"Ohhh. Great warrior. Wars not make one great." -Yoda |
| '-._"7' |"Freedom is still the most radical idea of all" -N.Branden|
| /'.-c |Linux registered user #402901, http://counter.li.org/ |
| | /T |http://esambale.wikispaces.com|
| _)_/LI
|---------|----------------------------------------------------------|