Group #-1 to Group nobody

If you have already been using apache2, MAKE SURE that you backup any files in the conf, htdocs, modules, or other subdirectories of /usr/local/apache2 where you might have changed or added files so that installing the updated apache2 will not cause your configuration or other files to be lost.

The configuration step for this package was

./configure --prefix=/usr/local/apache2 --enable-mods-shared=all --enable-ssl=shared --enable-ssl --with-ssl=/usr/local/ssl --enable-proxy --enable-proxy-connect --enable-proxy-ftp --enable-proxy-http

The modules that were compiled with this package can be found in /usr/local/apache2/modules. You may also need to set up startup scripts to begin the httpd processes at boot up. See the appropriate link for your level of Solaris in openssh.html where you can determine how to set up the randomness features required when using openssl.

If you have already been using apache2, MAKE SURE that you backup any files in the conf, htdocs, modules, or other subdirectories of /usr/local/apache2 where you might have changed or added files so that installing the updated apache2 will not cause your configuration or other files to be lost.

The configuration step for this package was

./configure --prefix=/usr/local/apache2 --enable-mods-shared=all --enable-ssl=shared --enable-ssl --with-ssl=/usr/local/ssl --enable-proxy --enable-proxy-connect --enable-proxy-ftp --enable-proxy-http --with-ldap --enable-ldap --enable-authnz-ldap

The modules that were compiled with this package can be found in /usr/local/apache2/modules. You may also need to set up startup scripts to begin the httpd processes at boot up. See the appropriate link for your level of Solaris in openssh.html where you can determine how to set up the randomness features required when using openssl.

\[        cut        false    ls      pathchk   sha224sum  sync      unexpand 
base64    date       fmt      md5sum  pinky     sha256sum  tac       uniq 
basename  dd         fold     mkdir   pr        sha384sum  tail      unlink 
cat       df         groups   mkfifo  printenv  sha512sum  tee       uptime 
chcon     dir        head     mknod   printf    shred      test      users 
chgrp     dircolors  hostid   mktemp  ptx       shuf       timeout   vdir 
chmod     dirname    id       mv      pwd       sleep      touch     wc 
chown     du         install  nice    readlink  sort       tr        who 
chroot    echo       join     nl      rm        split      true      whoami 
cksum     env        kill     nohup   rmdir     stat       truncate  yes 
comm      expand     link     nproc   runcon    stdbuf     tsort 
cp        expr       ln       od      seq       stty       tty 
csplit    factor     logname  paste   sha1sum   sum        uname

so that programs like gimp, which depend on dbus, will start properly.

Note that this version of gcc was created on build 60 of Solaris 10. If you are using a higher version, you will need to redo some of the header files. This is done by doing the following steps:

cd /usr/local/lib/gcc-lib/sparc-sun-solaris2.10/3.3.2/install-tools/

Put the line SHELL=/bin/sh on the first line of the mkheaders.conf
file.  Then run

./mkheaders

This will correct some files and make the build 60 gcc usable on 
higher builds.  I have tested this on build 72 and it works fine.

Please also read the detail on how the gcc packages are created which can be found at Comments on gcc. The documentation is in /usr/local/doc/gcc, /usr/local/man, and /usr/local/info.

Once you install the gtk and other dependency packages, it is important that you test gtk+. This can be done by running the gtk-demo program and seeing if the various examples work. Generally, the gtk-demo, and other programs you build with gtk+, will only work if your font cache is set up properly. This is done by editing the /usr/local/etc/fonts/fonts.conf file so that the font directory list is something like

        <dir>/usr/share/fonts</dir>
        <dir>/usr/openwin/lib/X11/fonts</dir>
        <dir>~/.fonts</dir>

/usr/local/bin/fc-cache -f -v

as root, which can take many hours, but when it finishes will give you a succeeded message.

libgcc_s.so
libgcc_s.so.1
libstdc++.so
libstdc++.so.6
libstdc++.so.6.0.3

Since these files are part of the gcc 3.4.6 package, you may not need to install it if you already have gcc 3.4.6 installed. This package is created because some programs will not run without these libraries - installs in /usr/local/lib. Earlier versions of the files in libgcc can be found at libgcc-3.3 or in the ftp archive.

libgcc_s.so    libstdc++.a   libstdc++.so    libstdc++.so.5.0.5  
libgcc_s.so.1  libstdc++.la  libstdc++.so.5  sparcv9

./sparcv9:
libgcc_s.so.1        libstdc++.a   libstdc++.so    libstdc++.so.5.0.5
libgcc_s_sparcv9.so  libstdc++.la  libstdc++.so.5

Since these files are part of the gcc package, you may not need to install it if you already have gcc 3.3 installed. This package is created because some programs will not run without these libraries - installs in /usr/local/lib.

To fix this, you will need to update to a newer version of Solaris 10 or upgrade the SUNWcsl and SUNWcslr packages.

Among the executables (in /usr/local/bin) are: 

 pine   The Pine mailer. Once compiled this should work just fine on
        your system with no other files than this binary, and no
        modifications to your system. Optionally you may create two
        configuration files, /usr/local/lib/pine.conf and 
        /usr/local/lib/pine.info. See the documentation for details.
 
 pico   The standalone editor similar to the Pine message composer.
        This is a very simple straight forward text editor.
 
 pilot  The standalone file system navigator.
 
 imapd  The IMAP daemon. If you want to run Pine in client/server mode,
        this is the daemon to run on the server. Installing this
        requires system privileges and modifications to /etc/services.
        See doc/tech-notes for more details. (in /usr/local/sbin along
        with ipop3d and ipop2d)
 
 mtest  The test IMAP client, an absolutely minimal mail client, useful
        for debugging.

 rpload Utility for uploading a local pinerc or address book to an IMAP
        server.

 rpdump Utility for downloading a pinerc or address book to the
        local machine.

 mailutil 
        Utility for performing various operations on mailboxes,
        be they local or remote.

Many of the demos and example programs may depend on:
bzip2-1.0.6,
openssl-1.0.0g,
gdbm-1.9.1,
ncurses-5.4,
readline-5.2,
tcl-8.5.10,
tk-8.5.10,
zlib-1.2.5,
xft-2.1.2,
xrender-0.8.3,
expat-2.0.1,
fontconfig-2.8.0,
freetype-2.4.2,
If you have an older version of python and python applications installed, you may need to edit your PYTHONPATH environment variable to include both old and new python directories. Also, some modules or demos may not exist or work with all levels of Solaris.

        setenv QTDIR /usr/local/qt
        setenv PATH $QTDIR/bin:$PATH
        setenv MANPATH $QTDIR/doc/man:$MANPATH
        setenv LD_LIBRARY_PATH $QTDIR/lib:$LD_LIBRARY_PATH

        QTDIR=/usr/local/qt
        PATH=$QTDIR/bin:$PATH
        MANPATH=$QTDIR/doc/man:$MANPATH
        LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH

********************************************************
* WARNING:
* Plugins are being installed into /usr/local/lib/sasl2,
* but the library will look for them in /usr/lib/sasl2.
* You need to make sure that the plugins will eventually
* be in /usr/lib/sasl2 -- the easiest way is to make a
* symbolic link from /usr/lib/sasl2 to /usr/local/lib/sasl2,
* but this may not be appropriate for your site, so this
* installation procedure won't do it for you.
*
* If you don't want to do this for some reason, you can
* set the location where the library will look for plugins
* by setting the environment variable SASL_PATH to the path
* the library should use.
********************************************************