You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by fu...@apache.org on 2020/05/20 18:58:15 UTC
svn commit: r1877960 - in /subversion/trunk: INSTALL
subversion/bindings/swig/INSTALL
Author: futatuki
Date: Wed May 20 18:58:15 2020
New Revision: 1877960
URL: http://svn.apache.org/viewvc?rev=1877960&view=rev
Log:
* INSTALL (I.C.12): Add Note that non-release mode is required for building
SWIG Python 2 bindings.
* subversion/bindings/swig/INSTALL
(BUILDING SWIG BINDINGS FOR SVN ON UNIX, Step 2): Add description how to
confirm that the ./configure could find SWIG path correctly.
Review by: danielsh
Modified:
subversion/trunk/INSTALL
subversion/trunk/subversion/bindings/swig/INSTALL
Modified: subversion/trunk/INSTALL
URL: http://svn.apache.org/viewvc/subversion/trunk/INSTALL?rev=1877960&r1=1877959&r2=1877960&view=diff
==============================================================================
--- subversion/trunk/INSTALL (original)
+++ subversion/trunk/INSTALL Wed May 20 18:58:15 2020
@@ -506,6 +506,12 @@ I. INTRODUCTION
reached end of life. All users are strongly encouraged to move
to Python 3.
+ Note: If you are using a Subversion distribution tarball and want
+ to build the Python bindings for Python 2, you should rebuild
+ the build environment in non-release mode by running
+ 'sh autogen.sh' before running the ./configure script; see
+ section II.B for more about autogen.sh.
+
13. Perl 5.8 or newer (Windows only) (OPTIONAL)
Modified: subversion/trunk/subversion/bindings/swig/INSTALL
URL: http://svn.apache.org/viewvc/subversion/trunk/subversion/bindings/swig/INSTALL?rev=1877960&r1=1877959&r2=1877960&view=diff
==============================================================================
--- subversion/trunk/subversion/bindings/swig/INSTALL (original)
+++ subversion/trunk/subversion/bindings/swig/INSTALL Wed May 20 18:58:15 2020
@@ -143,6 +143,7 @@ Step 2: Build and Install Subversion.
Make sure that Subversion's ./configure script sees your installed SWIG!
It tries to detect SWIG near the very end of its output.
+ You can find it by running 'grep "^SWIG=" config.log'.
Also make sure that the configure script sees the paths to the perl and/or
python executable you used to configure SWIG as above. If it does not then