Installing AbiWord on Solaris

The current version of AbiWord (0.7.9) should install and run properly one any Solaris 7 system with has a Sparc32 processor. AbiWord is available in both Solaris " pkg " format and gzipped tar format.

The Solaris "pkg "  format installation is quite simple, and will be familiar to users of Solaris.

1. Download the distribution files ( abisuite.0.7.9.sparc32.SunOS.5.5.1.pkg.tar.gz , 2.6MB).
2. Copy the files to a directory writable by you and open the files:

      gunzip - c abisuite.0.7.9.sparc32.SunOS.5.5.1.pkg.tar.gz |
   tar xvf -

   ... or, if your tar command supports the ' z' flag:

      tar xvzf abisuite.0.7.9.sparc32.SunOS.5.5.1.pkg.tar.gz

   Both these commands will create the directory abisuite .
3. Become superuser,  and enter the command:

      pkgadd - d.  abisuite

4. By default, this will install AbiWord and supporting files to the /usr/local/AbiSuite on your hard drive. You will be given the opportunity to changes this if you wish.
5. You will also be given the option to create links to the executable in a common bin directory. By default, this is /usr/local/bin .
6. Please consult the README file for additional details.

1. Download the distribution files ( abisuite-0.7.9-SunOS_sparc32_dynamic.tar.gz , 2.6MB).
2. Copy the files to a directory writable by you and open the files:

      gunzip - C abisuite-0.7.9-SunOS_sparc32_dynamic.tar.gz | tar
   xvf -

   ... or, if your tar command supports the ' z' flag:

      tar xvzf abisuite-0.7.9-SunOS_sparc32_dynamic.tar.gz

   Both these commands will create the directory abisuite-0.7.9-SunOS_sparc32_dynamic .
3. Change to that directory and become superuser.
4. Run the install script:

      /install.sh

5. By default, this will install AbiWord and supporting files to the /usr/local/AbiSuite on your hard drive. You will be given the opportunity to changes this if you wish.
6. You will also be given the option to create links to the executable in a common bin directory. By default, this is /usr/local/bin .
7. Please consult the README file for additional details.