Author: hartmannathan
Date: Fri Nov 13 14:18:22 2020
New Revision: 1883386
URL: http://svn.apache.org/viewvc?rev=1883386&view=rev
Log:
In 'staging': 1.14 release notes: Fix/expand info about --without-swig
* docs/release-notes/1.14.html:
(issues-other-without-swig): Fix incorrect statements about 'configure'
automatically skipping the SWIG version check. Expand and rearrange the
text to hopefully make it more helpful.
Found by: futatuki
Review by: futatuki
Modified:
subversion/site/staging/docs/release-notes/1.14.html
Modified: subversion/site/staging/docs/release-notes/1.14.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.14.html?rev=1883386&r1=1883385&r2=1883386&view=diff
==============================================================================
--- subversion/site/staging/docs/release-notes/1.14.html (original)
+++ subversion/site/staging/docs/release-notes/1.14.html Fri Nov 13 14:18:22
2020
@@ -1363,24 +1363,41 @@ as of 1.14.1. See <a href="http://svn.ap
</div> <!-- issues-other-c90compat -->
<div class="h4" id="issues-other-without-swig">
-<h4>Cannot build SWIG Python bindings without SWIG
+<h4>Installed SWIG prevents building Subversion's Python 3 bindings
<a class="sectionlink" href="#issues-other-without-swig"
title="Link to this section">¶</a>
</h4>
-<p>When building Subversion from a 1.14.0 release archive, it is not possible
-to build Subversion's SWIG Python bindings if SWIG is not installed. This is a
-bug because the sources generated by SWIG are included with the release. The
-failure is due to Subversion's build system attempting to check the version of
-SWIG, which fails if SWIG is not available.</p>
-
-<p>This issue is fixed as 1.14.1. The SWIG version check is automatically
-skipped if the SWIG-generated files are present when <tt>configure</tt> is
-run. Also, the check can be skipped explicitly by passing the
+<p>When building Subversion from a 1.14.0 distribution tarball, you may not be
+able to build Subversion's language bindings for Python 3 if
+<tt>configure</tt> detects an unsuitable version of SWIG on your system. This
+is a bug because the sources generated by SWIG for Python 3 bindings are
+included with the release.</p>
+
+<p>For this situation, a workaround is available as of 1.14.1: pass the
<tt>--without-swig</tt> option to <tt>configure</tt>.</p>
<p>See <a href="http://svn.apache.org/r1876662";>r1876662</a>.</p>
+<p>The workaround does not apply in the following situations:</p>
+
+<ul>
+ <li>building Subversion from sources checked out from the repository, where
+ the SWIG-generated files are not included</li>
+ <li>building Subversion's SWIG bindings for Python 2.x, in which case SWIG
+ is needed to regenerate the language bindings because the included ones
+ target Python 3</li>
+</ul>
+
+<p>In these cases, you will need a suitable version of SWIG:</p>
+
+<ul>
+ <li>To target Python 2: SWIG 2.0.0 through 3.x. (Note that
+ <tt>configure</tt> will allow SWIG 1.3.24 through 3.x, but SWIG 4.0.0 or
+ later are not supported for Python 2.)</li>
+ <li>To target Python 3: SWIG 3.0.10 or later.</li>
+</ul>
+
</div> <!-- issues-other-without-swig -->
</div> <!-- issues-other -->
