[26136] in CVS-changelog-for-Kerberos-V5
svn rev #25476: trunk/doc/rst_source/krb_build/
daemon@ATHENA.MIT.EDU (ghudson@mit.edu)
Tue Nov 15 12:31:11 2011
Date: Tue, 15 Nov 2011 12:31:09 -0500
From: ghudson@mit.edu
Message-Id: <201111151731.pAFHV9Of015146@drugstore.mit.edu>
To: cvs-krb5@mit.edu
Reply-To: krbdev@mit.edu
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cvs-krb5-bounces@mit.edu
http://src.mit.edu/fisheye/changelog/krb5/?cs=25476
Commit By: ghudson
Log Message:
Adjust "make check" constraints in rst docs
Recopy the text from the texinfo build docs into the rst version,
describing --disable-rpath and avoiding an erroneous reference to make
fake-install.
Changed Files:
U trunk/doc/rst_source/krb_build/doing_build.rst
Modified: trunk/doc/rst_source/krb_build/doing_build.rst
===================================================================
--- trunk/doc/rst_source/krb_build/doing_build.rst 2011-11-15 02:42:58 UTC (rev 25475)
+++ trunk/doc/rst_source/krb_build/doing_build.rst 2011-11-15 17:31:09 UTC (rev 25476)
@@ -120,9 +120,14 @@
* Configure and build Kerberos with Tcl support. Tcl is used to drive the test suite.
This often means passing *--with-tcl* to configure to tell it the location of the Tcl configuration script. (See :ref:`options2configure`.)
- * You have to run *make install* before running *make check*, or the test suite will often pick up the installed version of Kerberos
- rather than the newly built one. You can install into a prefix that isn't in the system library search path, though.
- Alternatively, you can run *make fake-install* ( need more info).
+ * On some operating systems, you have to run *make install* before
+ running *make check*, or the test suite will pick up installed
+ versions of Kerberos libraries rather than the newly built ones.
+ You can install into a prefix that isn't in the system library
+ search path, though. Alternatively, you can configure with
+ *--disable-rpath*, which renders the build tree less suitable
+ for installation, but allows testing without interference from
+ previously installed libraries.
* In order to test the RPC layer, the local system has to be running the *portmap* daemon and
it has to be listening to the regular network interface (not just localhost).
_______________________________________________
cvs-krb5 mailing list
cvs-krb5@mit.edu
https://mailman.mit.edu/mailman/listinfo/cvs-krb5