v.support fixes of GRASS 4.15

kang at risca.rs.msu.edu kang at risca.rs.msu.edu
Tue Sep 26 15:50:15 EDT 1995


Hi,
Thanks for the answeres from Bill Brown <brown at gis.uiuc.edu> and Paul Loechl 
<loechl at diego.cecer.army.mil> about my v.support problem with GRASS 4.15.

Although I got if fixed, I am still a little bit confused.  Here is the
summary:
If you recently compiled GRASS4.15 on your own and the v.support doesn't work.
Do the followings:
(1) get level_two.c in the grass/incoming directory from CERL GRASS anonymous
ftp site.
(2) relplace the src/mapdev/level_two.c with the one your get from step (1)
(3) cd to src/mapdev and run gmake4.1
(4) if you also have other programs that use Vlib stuff, then you also want to
recompile them to ensure that your programs will use the update-to-date lib.

The confusing part is from Paul's message:
> The Grass4.1.5 source code has a bug in a program called v.build which is
> used by v.support.  If you have Grass4.1.4 code, you can use the v.build
> program from that in place of the v.build in your 4.1.5 code.  If you
> don't have 4.1.4 code, you can grab a fixed version of v.build off of our
> ftp server, moon (129.229.20.254).  Look for a file called v.build.sun
> under the /grass/incoming directory.

There are two v.build files in the grass/incoming directory:
v.build.sgi.Z		(for Silicon Graphics - ?)
v.build.sun4		(for SUN OS 4.1.x - ?)

I assume that they are binary and platform specific, so that I can't use either
of them with Sun Solaris, Linux, or AIX (or others).  Since my step (1) to (4)
alreay fixed the v.spport problem and I didn't and couldn't apply either of
the fixed v.build, do I still have a bug in v.build which may cause other
problem in the future?

Kang,
   



More information about the grass-user mailing list