glfs/postlfs/security/tripwire/tripwire-exp.xml
Tushar Teredesai ff42aadfca PPP, GCC and Tripwire fixes
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1335 af4574ff-66df-0310-9fd7-8a98e5e911e0
2003-10-06 23:44:46 +00:00

29 lines
1.1 KiB
XML

<sect2>
<title>Command explanations</title>
<para><screen><command>export PATH_HOLD=$PATH &amp;&amp;
export PATH=/opt/gcc-2.95.3/bin:$PATH</command></screen>These
instructions save the current <envar>PATH</envar> and then places
<application><acronym>GCC</acronym>-2.95.3</application> at the head of
the path. This is done because <application>Tripwire</application> will
not compile with the newer
<application><acronym>GCC</acronym></application>.</para>
<para><command>ln -s make /usr/bin/gmake</command>: The reason we create the
<command>gmake</command> symlink is that <application>Tripwire</application>
will only install if the symlink is present. It may be safely removed after
installation.</para>
<para><command>gmake release</command>: This command creates the
<application>Tripwire</application> binaries.</para>
<para><command>cp install.{sh,cfg} .</command>: These are copied to the main
<application>Tripwire</application> directory so that the script can be used to
install the package.</para>
<para><command>cp policy/*.txt /usr/share/doc/tripwire</command>: This command
installs the documentation.</para>
</sect2>