Compiling 4.1

  I've taken the plunge and have started to
install GRASS4.1 on our Sun Sparc 2 with OpenWindows2.0.
Compilation stops with src.alpha/display/d.labels. Here is
the GISGEN output:

GISGEN: src.alpha/display/d.labels - Fri Jun 18 17:56:40 CDT 1993

#################################################################
/usr/local/grass4.1/src.alpha/display/d.labels
  mkdir OBJ
  make -f OBJ/make.rules

rm -f OBJ/main.o
cc -O -I/usr/local/grass4.1/src/include -c main.c
mv main.o OBJ/main.o
rm -f OBJ/get_loc.o
cc -O -I/usr/local/grass4.1/src/include -c get_loc.c
mv get_loc.o OBJ/get_loc.o
rm -f OBJ/opencell.o
cc -O -I/usr/local/grass4.1/src/include -c opencell.c
mv opencell.o OBJ/opencell.o
rm -f OBJ/display.o
cc -O -I/usr/local/grass4.1/src/include -c display.c
mv display.o OBJ/display.o
rm -f OBJ/in_window.o
cc -O -I/usr/local/grass4.1/src/include -c in_window.c
mv in_window.o OBJ/in_window.o
rm -f OBJ/check_resp.o
cc -O -I/usr/local/grass4.1/src/include -c check_resp.c
mv check_resp.o OBJ/check_resp.o
rm -f OBJ/show.o
cc -O -I/usr/local/grass4.1/src/include -c show.c
mv show.o OBJ/show.o
rm -f OBJ/where.o
cc -O -I/usr/local/grass4.1/src/include -c where.c
"where.c", line 75: warning: statement not reached
mv where.o OBJ/where.o
rm -f OBJ/modify.o
cc -O -I/usr/local/grass4.1/src/include -c modify.c

  Any suggestions on where to start looking for
the problem?

  Thanks for any advice.

Sharyl Walker
Dept. of Agricultural Engineering
University of Illinois
guernsey@holstein.age.uiuc.edu

In info.grass.user you write:

I've taken the plunge and have started to
install GRASS4.1 on our Sun Sparc 2 with OpenWindows2.0.
Compilation stops with src.alpha/display/d.labels. Here is
the GISGEN output:

...

rm -f OBJ/where.o
cc -O -I/usr/local/grass4.1/src/include -c where.c
"where.c", line 75: warning: statement not reached
mv where.o OBJ/where.o
rm -f OBJ/modify.o
cc -O -I/usr/local/grass4.1/src/include -c modify.c

Any suggestions on where to start looking for
the problem?

Thanks for any advice.

Did you solve your problem? It seems from the output that you did not have an
error. It should not have died from a warning. I would not worry about the
warning message if the binaries are working alright.

- Jim

--
[Jim] pirzyk@uiuc.edu ------------------------------------------
TAC & GrassNet System Administrator, US Army Corps of Engineers
Construction Engineering Research Labs, Champaign IL USA