Update for recent developments (C++, shlib), minor fixes

diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml
index 35457d020ac8936f4a67c0115553e88a8ce9d0ee..0ab49667aaa499f0968fbeb695e6f01dbfb75eed 100644 (file)
--- a/doc/src/sgml/installation.sgml
+++ b/doc/src/sgml/installation.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  <![%flattext-install-include[<productname>PostgreSQL</> ]]>Installation Instructions
@@ -7,7 +7,7 @@
   Short Version
 
   
-<programlisting>
+<synopsis>
 ./configure
 gmake
 gmake install
@@ -17,7 +17,7 @@ su - postgres
 /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data >logfile 2>&1 &
 /usr/local/pgsql/bin/createdb test
 /usr/local/pgsql/bin/psql test
-programlisting>
+synopsis>
    The long version is the rest of this
    
    
@@ -149,8 +149,8 @@ su - postgres
 
   
    The internal data storage format changes with new releases of
-   PostgreSQL. Therefore, if you are upgrading an existing installation
-   that does not have a version number
+   PostgreSQL. Therefore, if you are upgrading an
+   existing installation that does not have a version number
    &majorversion;.x, you must back up and restore your
    data as shown here. These instructions assume that your existing
    installation is under the /usr/local/pgsql directory,
@@ -207,9 +207,9 @@ su - postgres
      On systems which have PostgreSQL started at boot time, there is
      probably a start-up file that will accomplish the same thing. For
      example, on a Redhat Linux system one might find that
-<programlisting>
-/etc/rc.d/init.d/postgres.init stop
-programlisting>
+<screen>
+/etc/rc.d/init.d/postgres.init stop
+screen>
      works.
     
    
@@ -265,7 +265,7 @@ su - postgres
     The first step of the installation procedure is to configure the
     source tree for your system and choose the options you would like.
     This is done by running the configure script. For a
-    default installation simply type
+    default installation simply enter
 
 ./configure
 
@@ -283,7 +283,7 @@ su - postgres
    
 
    
-    You can customize the build and installation process by giving one
+    You can customize the build and installation process by supplying one
     or more of the following command line options to
     configure:
 
@@ -507,11 +507,7 @@ su - postgres
        --with-CXX
        
         
-         Build the C++ interface library. configure will
-         automatically pick the C++ compiler that goes with the C
-         compiler you are using. It is not recommended or supported to
-         use C and C++ compilers of different origin in the same
-         build.
+         Build the C++ interface library.
         
        
       
@@ -693,11 +689,14 @@ su - postgres
    
 
    
-    You can set the CC environment variable to choose the C
-    compiler to use. If you don't then configure will
-    look for one. For example:
+    If you prefer a C or C++ compiler different from the one
+    configure picks then you can set the
+    environment variables CC and CXX,
+    respectively, to the program of your choice.  Similarly, you can
+    override the default compiler flags with the CFLAGS
+    and CXXFLAGS variables.  For example:
 
-CC=/opt/bin/gcc ./configure
+env CC=/opt/bin/gcc CFLAGS='-02 -pipe' ./configure
 
    
     
@@ -825,12 +824,19 @@ All of PostgreSQL is successfully made. Ready to install.
   
    Shared Libraries
    
-    On most systems that have shared libraries (which most systems do)
+    On some systems that have shared libraries (which most systems do)
     you need to tell your system how to find the newly installed
-    shared libraries. How to do this varies between platforms, but the
-    most widely usable method is to set the environment variable
-    LD_LIBRARY_PATH like so: In Bourne shells (sh, ksh,
-    bash, zsh)
+    shared libraries.  The systems on which this is
+    not necessary include FreeBSD, HP/UX, Irix,
+    Linux, NetBSD, OpenBSD, OSF/1 (Digital Unix, Tru64 UNIX), and
+    Solaris.
+   
+
+   
+    The method to set the shared library search path varies between
+    platforms, but the most widely usable method is to set the
+    environment variable LD_LIBRARY_PATH like so: In Bourne
+    shells (sh, ksh, bash, zsh)
 
 LD_LIBRARY_PATH=/usr/local/pgsql/lib
 export LD_LIBRARY_PATH
@@ -842,9 +848,19 @@ setenv LD_LIBRARY_PATH /usr/local/pgsql/lib
     Replace /usr/local/pgsql/lib with whatever you set
     --libdir to in .
     You should put these commands into a shell start-up file such as
-    /etc/profile or ~/.bash_profile.
+    /etc/profile or ~/.bash_profile.  Some
+    good information about the caveats associated with the method can
+    be found at 
+    url="http://www.visi.com/~barr/ldpath.html">http://www.visi.com/~barr/ldpath.html.
+   
+
+   
+    On some systems it might be preferrable to set the environment
+    variable LD_RUN_PATH before
+    building.
    
 
+
    
-    If in doubt, refer to the manual pages of your system. If you later
+    If in doubt, refer to the manual pages of your system (perhaps
+    ld.so or rld). If you later
     on get a message like
 
 psql: error in loading shared libraries
@@ -864,7 +881,6 @@ libpq.so.2.1: cannot open shared object file: No such file or directory
 
     then this step was necessary.  Simply take care of it then.
    
-
   
 
   
@@ -921,12 +937,13 @@ MANPATH=$MANPATH:/usr/local/pgsql/man
   
    
     
-     Create the PostgreSQL server account. This is the user the server
-     will run as. For production use you should create a separate,
-     unprivileged account (postgres is commonly used). If
-     you do not have root access or just want to play around, your own
-     user account is enough, but running the server as root is a
-     security risk and therefore not allowed.
+     Create a user account for the PostgreSQL
+     server. This is the user the server will run as. For production
+     use you should create a separate, unprivileged account
+     (postgres is commonly used). If you do not have root
+     access or just want to play around, your own user account is
+     enough, but running the server as root is a security risk and
+     will not work.
 
 adduser postgres