Index of /grass50/binary/irix

[ICO]NameLast modifiedSizeDescription

[PARENTDIR]Parent Directory  -  
[   ]COPYING2001-02-04 11:53 1.8K 
[   ]ChangeLog2003-11-06 05:56 803K 
[TXT]NEWS.html2003-11-06 05:56 62K 
[TXT]README.html2008-03-27 14:33 3.5K 
[TXT]REQUIREMENTS.html2003-11-08 21:09 6.3K 
[   ]grass5.0.2_irix-o32_bin.tar.gz2003-05-29 05:43 59M 
[TXT]grass5_irix-o32_install.sh2003-05-29 05:15 13K 

This directory contains the SGI/IRIX binary code for
GRASS 5.0.X in gzipped tar format.  


1. get the large (65 MB) file 
   which is the whole binary in a single file.  
2. get the installation script

Then you only need to type the following after
you downloaded it (example!):

  sh grass5.0.0_IRIX_bin.tar.gz [dest_dir] [bin_dir]

This will create the necessary directories and
files for you to run GRASS. The default install path is

To install in a different directory, specify it in the
command line.

Usage:  sh grass_binpackage.tar.gz [dest_dir] [bin_dir]

        grass_binpackage : name of GRASS 5 binary package
        [dest_dir] - optional: FULL path name to the installation directory
                     (default: /usr/local/grass5/)
        [bin_dir] - optional: FULL path name to the grass binary directory
                     (default: /usr/local/bin/)
                     Notes: 1) Only the grass executable file is stored here
                            2) If you want to change the binary directory only
                               then you need to specify the destination
                               directory as well

You may need login as root for installation.

Example (changing the destdir, keeping the bindir):
  sh grass5.0.0_IRIX_bin.tar.gz /opt/grass5

After installation start GRASS with


To get help, enter

   grass5 -help

The user interface is started within GRASS:

Note: If you are starting from beginning, you have 
to define your project area within GRASS before 
accessing the "tcltkgrass" user interface.

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 web server/FTP site.  Sample data is also
available from the site, or you may use data from previous
versions of GRASS if you have it available.

Please help us and report bugs using the bug report form at:
go here!

If you experience any problems, please email us at:    

 International GRASS Users Mailing list


Get this file.