Very nice work!!
GRASSbeta4 has been a pleasure to workwith (now already 6 hours
nonstop).However, I already bumped into a bug...
in the linux binary edition (published this morning)
---grass5beta4_linuxbin.tar---r.in.tiff - gives a core dumped no matter what
Hi Juhana,
reason might be that r.in.tiff *should* accept 24bit now.
It seems there is still abug in the code.
Thanks for notifying it.
Markus
To DU 64bit users and developers,
I post in attachment to this mail the errors
and fixes I had to do in order to compile grass5beta4
on Digital Unix alpha.
I had to modify the source code in many places. I do
not actualy know how much of these changes are specific
to the particular system I installed grass on, or to
*my choice* of using cc instead of gcc. Anyhow
I hope these help if somebody runs into troubles in
compiling on a 64bit system
Luca
--
--> Luca Palmeri - Dip. Proc. Chimici dell'Ingengeria
Universita' di Padova TEL: +390498275527 -------
------------------------- FAX: +390498275528 -------
--> Think holistic @ the end of the 2nd millenium <--
duALPHA.txt (5.98 KB)
On Tue, Oct 26, 1999 at 07:41:20PM +0200, Luca Palmeri wrote:
I post in attachment to this mail the errors
and fixes I had to do in order to compile grass5beta4
on Digital Unix alpha.
Thanks. I couldn't get the source fast enough to start with it.
I had to modify the source code in many places. I do
not actualy know how much of these changes are specific
to the particular system I installed grass on, or to
*my choice* of using cc instead of gcc. Anyhow
I hope these help if somebody runs into troubles in
compiling on a 64bit system
You should create a patch (running diff -u)
on the changed files. This would applying your changes easier.
before compile, after doing ./configure
0) Changed "gcc" -> "cc" and "-g" -> "-g3" in src/CMD/head/head
cc likes very much the -g3 optimization with debugging symbols
But this is not necessary.
And usually you can give options to configure, like
CC=cc CFLAGS="-std1 -O -g3" ./configure .....
2) changed "-lncurses" -> "-lcurses" in src/CMD/head/head. I do not
have SOs ncurses on my system and had some unresolved symbols.
configure should have taken care of this.
Maybe you have ncurses installed somewhere.
7) in the file src/mapdev/v.in.tig.lndmk/globals.h commented the definition of
"dirname" due to the following error:
cc: Error: globals.h, line 77: In this declaration, the type of
"dirname" is not compatible with the type of a previous declaration of
"dirname" at line number 165 in file /usr/include/string.h.
extern char dirname[250]; /* base directory/file name for Tiger files */
This dirname can be removed totally. (It is in myt last patch.)
11) in file src/scripts/contrib/Gmakefile delete the 2nd line
# $(GMAKE) tiger.info
even if that is commented make on DU seems not allowing comented lines
like that in makefile, it complains saying something about files not found.
I would recommend to install gnumake and bison/flex.
It doesn't take that much space, and really helps.
I will go for the compile soon.
Bernhard
--
Research Assistant, Geog Dept UM-Milwaukee, USA. (www.uwm.edu/~bernhard)
Free Software Projects and Consulting (www.intevation.de)
Association for a Free Informational Infrastructure (ffii.org)
Hi Bernhard,
Bernhard Reiter wrote:
> 0) Changed "gcc" -> "cc" and "-g" -> "-g3" in src/CMD/head/head
> cc likes very much the -g3 optimization with debugging symbols
But this is not necessary.
And usually you can give options to configure, like
CC=cc CFLAGS="-std1 -O -g3" ./configure .....
Yes, sorry it is a little bit inelegant, but I did like that just to see
what where the guess of ./configure on CC and related options.
What you mean by unecessary ?
If you mean that gcc is the samte as cc, this is not true. Some
broken modules (like i.points3) are compiled without problems with
gcc, while with cc are not. Then the -g3 option, I do not know if it helps
really, but at least with that cc do not warns you so much.
> 2) changed "-lncurses" -> "-lcurses" in src/CMD/head/head. I do not
> have SOs ncurses on my system and had some unresolved symbols.configure should have taken care of this.
Maybe you have ncurses installed somewhere.
Yes in fact, but I do not have a libcurses.so
Is that necessary to use ncurses ? I think so, I am not sure
but anyway I didn't find any other way to compile.
See in the bottom what gives me a find / -name *curses*
I would recommend to install gnumake and bison/flex.
It doesn't take that much space, and really helps.
I will do that tomorrow.
Thanks
Luca
find / -name *curses* gives
/usr/shlib/osf.1/libcurses.so
/usr/ccs/lib/libcurses.a
/usr/include/curses.h
/usr/lib/libcurses.a
/usr/opt/obsolete/usr/lib/libcurses.a
/usr/opt/obsolete/usr/shlib/libcurses.so
/export/venus6a/usr_local_du40d/lib/libncurses.a
/export/venus6a/usr_local_du40d/lib/libdcurses.a
/export/venus6a/usr_local_du40d/lib/libpcurses.a
/export/venus6a/usr_local_du40d/lib/gcc-lib/alpha-dec-osf2.0/2.6.3/include/curses.h
/export/venus6a/usr_local_du40d/lib/gcc-lib/alpha-dec-osf3.2/2.7.2.1/include/curses.h
/export/venus6a/usr_local_du40d/lib/gcc-lib/alphaev56-dec-osf4.0d/2.8.0/include/curses.h
/export/venus6a/usr_local_du40d/lib/ncurses
/export/venus6a/usr_local_du40d/lib/perl4/curses.ph
/export/venus6a/usr_local_du40d/lib/tin-1.1/curses.c
/export/venus6a/usr_local_du40d/lib/tin-1.1/curses.o
/export/venus6a/usr_local_du40d/man/man3/ncurses.3x
/export/venus6a/usr_local_du40d/man/cat3/ncurses.3x
/export/venus6a/usr_local_du40d/include/ncurses.h
--
--> Luca Palmeri - Dip. Proc. Chimici dell'Ingengeria
Universita' di Padova TEL: +390498275527 -------
------------------------- FAX: +390498275528 -------
--> Think holistic @ the end of the 2nd millenium <--
On Tue, Oct 26, 1999 at 09:07:11PM +0200, Luca Palmeri wrote:
Hi Bernhard,
Bernhard Reiter wrote:
> > 0) Changed "gcc" -> "cc" and "-g" -> "-g3" in src/CMD/head/head
> > cc likes very much the -g3 optimization with debugging symbols> But this is not necessary.
> And usually you can give options to configure, like
>
> CC=cc CFLAGS="-std1 -O -g3" ./configure .....Yes, sorry it is a little bit inelegant, but I did like that just to see
what where the guess of ./configure on CC and related options.
What you mean by unecessary ?
Oh that you can give it to ./configure as I showed above.
Yes in fact, but I do not have a libcurses.so
Is that necessary to use ncurses ? I think so, I am not sure
but anyway I didn't find any other way to compile.
It should work without ncurses, IMO.
The compile is running, because
I had "-std1 -w0" flags given, I get a bit more error msgs.
Bernhard
--
Research Assistant, Geog Dept UM-Milwaukee, USA. (www.uwm.edu/~bernhard)
Free Software Projects and Consulting (intevation.de)
Association for a Free Informational Infrastructure (ffii.org)