Grass&Solaris:Solution????

  Hi Dear Grass's Users,

    As you knows, I, and many others people, have
  found many trobles in many programs in binary version
  for GRASS4.1 and solaris....(i.e)

  d.what.rast
  d.where
  r.mapcalc
  r.in.poly
  r.out.poly
  s.menu
  d.3d
  g.region
  etc....

    For many time we are looking for a solution, between
  the Grass comunity.. however there's not a effective response
  for this requeriment....

    Well, I think that a good person, what has compiled Grass
  under solaris in his own machine could send us these program,
  (in GISBASE/etc/bin) .... if somebody migth do this...please
  e-mail me to
  nsegura@halcon.dpi.udec.cl

  hmmm... please report any other dificultate in solaris version
  to the same address

  thnank you

as a general trend (especially with linux users, and now
with solaris users), I see people more and more wanting binary versions.

What's wrong with getting the source code and compiling it?
Do people generally find the process too cumbersome or daunting?

I'm genuinely curious.

- The compilation process has gotten much easier over the past
  4 or 5 years - most things (everything?) in the src/ dir
  compiles without a hitch/warning. Is the process too difficult?
  Are there too many steps involved?
  
- With increased speeds of workstations,
  compilation time has decreased by at least 50% (probably more,
  but then grass has increased in size). Is time a problem?
  
- With the availability of gcc, compiler availability is
  *not* a problem.
  
- There's a step-by-step document on "how-to" for those
  unfamiliar with the process. Is the documentation difficult
  to understand?

Are there suggestions for making the process easier?

--Darrell