Index of /grass50/binary/solaris_sun

[ICO]NameLast modifiedSizeDescription

[PARENTDIR]Parent Directory  -  
[   ]BUGS2001-06-01 15:38 4.8K 
[   ]COPYING2000-12-07 00:58 1.8K 
[TXT]NEWS.html2003-11-06 05:56 62K 
[TXT]README.html2007-12-10 14:29 5.8K 
[TXT]REQUIREMENTS.html2003-11-08 21:09 6.3K 
[TXT]WARNING.html2001-11-24 12:22 4.5K 

This README describes how to unpack and install the pkg file on
a SUN Solaris 8 computer.

For general information is also includes a description of the steps used
make the packed file.

There is some discussion about which installation directory to use.
Personally I favour /usr/local, in line with the policy of
Others like /opt, whihc may be more in line with the policy of SUN at least until Solaris 2.6

Thus two versions were made, with the filename indicating which installation directory is used.
grass-XXX-sol8-sparc-local (goes into /usr/local)
grass-XXX-sol8-sparc-opt (goes into /opt/GNUgrass)

In case of the /usr/local installation you need to add /usr/local/bin to your path,
while for the /opt installation you need to add /opt/GNUgrass/bin to your path.


1) get the file, in this case grass-5.0.0-sol8-sparc-local.gz

2) unzip it:
gunzip grass-5.0.0-sol8-sparc-local.gz

3) Install it using the pkgadd installation program from Sun
pkgadd -d grass-5.0.0-sol8-sparc-local

4) Add /usr/local/bin to you $path

5) Run the command "rehash" to get the new commands active in your shell

6) Run grass5

PREREQUSITES (they may not all be needed for running GRASS, but if you want to recompile they should be there)

Several other packages needs to be installed on the Solaris computer
in order to run (all) the Grass5 modules.

application fftw           FFTW
application unixODBC       unixODBC
application PostgSQL       PostgreSQL
application SMCautoc       autoconf
application SMCautom       automake
application SMCbinut       binutils
application SMCbison       bison
application SMCflex        flex
application SMCgcc302      gcc
application SMCm4          m4
application SMCmake        make
application SMCmysql       mysql
application SMCtar         tar       ***************** A must: throw away the build in SUN version of tar
application SMCtcl         tcl
application SMCtk          tk
application SMCtkinfo      tkinfo
application SMCprl561      perl
application SMCgdbm        gdbm

With 3 exceptions, I got the precompiled packaged from the

The exceptions are:
FFTW, unixODBC, PostgreSQL
which I made in a similar way as Grass5. I have informed the organisations and
you may be able to get the SUN packages from them, ie. from

or you could try our software website ( though it is still experimental.


In broad terms the procedure was as follows:

Got the sources, then:
gunzip grass5.0.0.tar.gz
tar xf grass5.0.0.tar
cd grass5.0.0

Before configuring and compiling, several packages need to be sorrectly installed,
among them fftw, PostgreSQL, unixODBC (which we had to compile from scratch),
and several others like Binutils, dbm etc (which are available as packages from
the free sun compilations). When some software was missing, configure complained and
we then added the package.

1. untar source code of grass
2. in main directory: configure --prefix=/sd5/local --with-postgres-includes=/usr/local/include/postgresql
3. make
4. make install
5. cd /sd5/local
5A chown -R root * ; chgrp -R bin *
6. find . -print | pkgproto > prototype
7. add "i pkginfo=./pkginfo" on the first line in prototype
7A rm last line refereing to the "prototype" file itself, if it is there
8. edit protype by changing group and owner to bin
9. create pkginfo (by manually editing a file with the necessary fields)
Now to get the package in /usr/local in the end, the following has to be done:
9A. in main directory: configure --prefix=/usr/local --with-gcc
9B. make; make install
9C. cp prototype pkginfo /usr/local
9D. cd /usr/local
10. pkgmk -r `pwd`
11. cd /var/spool/pkg
12. pkgtrans -s `pwd` /tmp/grass5.0.0-sol8-sparc-local
13. gzip /tmp/grass5.0.0-sol8-sparc-local
Then clean up:
14. cd /var/spool/pkg; rm -r *
15. cd "main source directory": make uninstall
16. Then install the package with pkgadd -d filename

Palle Haastrup (
January 2002

Paint driver notes:

1) If you have local paint devices, you will need 
move the appropriate files from 
$GISBASE/etc/paint/driver.uninst to the 
in the same directory.  In addition, you must create 
a symbolic link (using the 'ln -s' command) from 
/dev/[paint driver name] to /dev/ttya or /dev/ttyb 
(or whichenver system device your print device is 
plugged in too).  For example, if you have a 
xerox4020 connected to /dev/ttya, use

        % cd $GISBASE/etc/paint/driver.uninst
        % mv xerox4020 ../
        % ln -s /dev/ttya /dev/xerox4020
        % chmod 0666 /dev/xerox4020

You will have to be root to create the symbolic 
link in /dev.

2) If you have a paint device which exists on a 
remote host whose GISBASE is difference from the 
local GISBASE you will need to update the value 
of GISBASE in etc/paint/driver.rsh.

3) If you plan to use v.digit and have any  
digitizers copy the file etc/digcap.sampl to 
etc/digcap and edit it accordingly.


The binary version does not come with any data or 
documentation (except for on-line man pages).  You will
need to acquire whatever documents you like from the GRASS 
Development Team FTP server.  Sample data is also available 
from the FTP site, or you may use data from previous
versions of GRASS if you have it available.


If you experience any problems, please email
us at:
 International GRASS Users Mailing list

Please help us and report eventually bugs:
Bug report form:
go here!

Get this file.