<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <HTML> <HEAD> <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9"> <TITLE>StarOffice 3.1 Mini-HOWTO: Installation of StarOffice</TITLE> <LINK HREF="StarOffice-4.html" REL=next> <LINK HREF="StarOffice-2.html" REL=previous> <LINK HREF="StarOffice.html#toc3" REL=contents> </HEAD> <BODY> <A HREF="StarOffice-4.html">Next</A> <A HREF="StarOffice-2.html">Previous</A> <A HREF="StarOffice.html#toc3">Contents</A> <HR> <H2><A NAME="s3">3. Installation of <CODE>StarOffice</CODE></A></H2> <P>Installation of StarOffice consists of: <UL> <LI>Untarring the distribution files as root in <CODE>/usr/local</CODE></LI> <LI>running the <CODE>setup</CODE> program as a user</LI> <LI>sourcing the <CODE>.sd.sh</CODE> or <CODE>.sd.csh</CODE></LI> <LI>reading section 3.5!!! (do this)</LI> </UL> <P> <H2><A NAME="ss3.1">3.1 Libc Issues and Fixes</A> </H2> <P>StarOffice is linked with <CODE>libc 5.4.4</CODE>. <P>StarOffice 3.1 *will* work on <CODE>Libc 5.3.x</CODE>. Unfortunately, the setup program requires 5.4.4 or higher. If you have <CODE>libc 5.3.x</CODE>, you might be able to get around this by acquiring a copy of <CODE>libc 5.4.4+</CODE> and adding it to your LD_LIBRARY_PATH environment variable before executing the <CODE>setup</CODE> script. I haven't tried this, however, so you're on your own. <P>If you attempt to run the <CODE>setup</CODE> script on a libc older than 5.4.4, you will get the following error message: <P> <BLOCKQUOTE><CODE> line 1: Syntax error at token 'I' expected declarator; i.e. File ... </CODE></BLOCKQUOTE> <P> <P>To upgrade your libc, FTP to <CODE> <A HREF="ftp://sunsite.unc.edu">sunsite.unc.edu</A></CODE> and look in the directory <CODE> <A HREF="ftp://sunsite.unc.edu/pub/Linux/GCC">/pub/Linux/GCC</A></CODE> for the file <CODE>libc-5.4.33.bin.tar.gz</CODE> (or whatever the latest libc is). Extract the contents of this file in a temporary directory. A new lib/ directory will be created. Su to root and copy the file <CODE>libc.so.5.4.33</CODE> from this directory to your /lib directory. Now, make the symlink from <CODE>libc.so.5</CODE> to <CODE>libc.5.4.33</CODE> with the command: <P> <BLOCKQUOTE><CODE> ln -sf /lib/libc.so.5.4.33 /lib/libc.so.5 </CODE></BLOCKQUOTE> then run the <CODE>ldconfig</CODE> command. <P> <P>Dr. Romano Giannetti <CODE>( <A HREF="mailto:romano@iet.unipi.it">romano@iet.unipi.it</A> )</CODE> says: <P> <BLOCKQUOTE> <P>...I want only to add that I could install (like you suggested) StarWriter in a redhat 4.2 system which has a libc5.3, without doing the upgrade. <P> <P>The exact steps are: <P> <P>1. get a libc.so.5.4.x. If you have a redhat rpm package (as the one you find in the contrib directory), you can extract the library by going in a scratch directory and doing: <CODE>rpm2cpio libc.so.5.4.x-y.rpm | cpio --extract --make-directories</CODE> The library will appear in ./lib subdirectory <P> <P>2. move libc.so.5.4.x in your home directory. Then (assuming a sh-like shell): <CODE>ln -s libc.so.5.4.x libc.so.5</CODE> <CODE>export LD_LIBRARY_PATH=$HOME:/lib:/usr/lib</CODE> <P> <P>3. Now you can run setup. </BLOCKQUOTE> <P> <H2><A NAME="ss3.2">3.2 Installing the tar Files</A> </H2> <P>After downloading StarOffice, su or login as root and place the archives in <CODE>/usr/local/</CODE>. Change directory to <CODE>/usr/local/</CODE> and extract the files. An example command to decompress a gzipped tar file would be: <P> <BLOCKQUOTE><CODE> tar -xzvf filename.tar </CODE></BLOCKQUOTE> <P>Older systems may require you first use the <CODE>gzip -d</CODE> command to unzip the file, then use the <CODE>tar -xvf</CODE> command to untar it. <P>The files will extract to their locations within the newly created <CODE>usr/local/StarOffice-3.1</CODE> tree. <P> <H2><A NAME="ss3.3">3.3 Setup und Configuration</A> </H2> <P>After you have extracted the StarOffice files as root, you will need to login with your userid. Change directory to <CODE>/usr/local/StarOffice-3.1</CODE> and execute the <CODE>setup</CODE> program. This program will install non-shared files and symlinks needed for each individual user. The standard installation is recommended. There *could* be problems if you do not accept the default installation path. <P>StarOffice makes use of environment variables. The files <CODE>.sd.sh</CODE> (formatted for the Bourne Shell) and <CODE>.sd.csh</CODE> (formatted for the C Shell) provide the environment variable settings for StarOffice. These files are located in your home directory. <P>If you use <CODE>bash</CODE>, edit your <CODE>.bashrc</CODE> and add the line: <BLOCKQUOTE><CODE> source /.sd.sh </CODE></BLOCKQUOTE> <P>After doing this, restart <CODE>bash</CODE> to bring the environment variables into effect. <P>If you use a different shell, consult that shell's man page for information on sourcing a file. <P> <H2><A NAME="ss3.4">3.4 COL (Caldera OpenLinux) setup bug</A> </H2> <P>Phil Reardon (<CODE> <A HREF="mailto:pcr@busprod.com">pcr@busprod.com</A></CODE> ) says: <BLOCKQUOTE> " I found a bug in the setup script for StarOffice that came with my Caldera COL standard release. It produces // in a path where there should only be one /. To fix it, remove the first slash from this line: <BLOCKQUOTE><CODE> exec ${pfad:='.'}/linux-x86/bin/$name;; </CODE></BLOCKQUOTE> There should be no / before linux-x86." </BLOCKQUOTE> <H2><A NAME="ss3.5">3.5 Fixing the LANG variable problem</A> </H2> <P>The <CODE>.sd.sh</CODE> and <CODE>.sd.csh</CODE> files set the LANG variable. This causes problems with perl and man. Man will give the error message <P> <BLOCKQUOTE> " Failed to open the message catalog man on the path NLSPATH=" </BLOCKQUOTE> Perl will give the error message <BLOCKQUOTE> " warning: setlocale(LC_CTYPE, "")..." </BLOCKQUOTE> <P>The <CODE>.sd.sh</CODE> file contains a line that sets LANG=us and another that exports a bunch of variables, including LANG. Remove the LANG=us line and remove LANG from the list of variables, and this will be fixed. <P>In the <CODE>.sd.csh</CODE> file (which is formatted for the c shell), you need to remove the line that says "setenv LANG us". <P>Thanks to Adam L. Klein (<CODE> <A HREF="mailto:alklein@adelphia.net">alklein@adelphia.net</A></CODE>) for informing me of this fix. <P> <HR> <A HREF="StarOffice-4.html">Next</A> <A HREF="StarOffice-2.html">Previous</A> <A HREF="StarOffice.html#toc3">Contents</A> </BODY> </HTML>