You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Nicholas Riley <nj...@uiuc.edu> on 2002/12/12 18:48:09 UTC

[PATCH] Fix for libsvn_swig_py namespace issue on OS X

* build.conf
  (libsvn_swig_py): swigutil_py.h declares SWIG_NewPointerObj and
  SWIG_TypeQuery, and expects to find them at runtime in one of the
  loaded Subversion Python modules (_fs.so, _ra.so, etc.).  This fails
  with Python 2.3 (and patched 2.2.x) on Mac OS X because they import
  Python modules into a private namespace.  Link against libswigpy so
  libsvn_swig_py will have direct access to these functions.  See
  <http://www.swig.org/Doc1.3/Advanced.html> for more information on
  this technique.

Index: build.conf
===================================================================
--- build.conf	(revision 4103)
+++ build.conf	(working copy)
@@ -233,7 +233,7 @@
 type = lib
 path = subversion/bindings/swig
 sources = swigutil_py.c
-libs = $(SVN_APRUTIL_LIBS) $(SVN_APR_LIBS)
+libs = $(SVN_APRUTIL_LIBS) $(SVN_APR_LIBS) -lswigpy
 install = swig-py-lib
 # need special build rule to include -DSWIGPYTHON
 custom = swig-py

-- 
=Nicholas Riley <nj...@uiuc.edu> | <http://www.uiuc.edu/ph/www/njriley>
        Pablo Research Group, Department of Computer Science and
  Medical Scholars Program, University of Illinois at Urbana-Champaign

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: [PATCH] Fix for libsvn_swig_py namespace issue on OS X

Posted by Sander Roobol <ph...@wanadoo.nl>.
On Thu, Dec 12, 2002 at 12:48:09PM -0600, Nicholas Riley wrote:
> * build.conf
>   (libsvn_swig_py): swigutil_py.h declares SWIG_NewPointerObj and
>   SWIG_TypeQuery, and expects to find them at runtime in one of the
>   loaded Subversion Python modules (_fs.so, _ra.so, etc.).  This fails
>   with Python 2.3 (and patched 2.2.x) on Mac OS X because they import
>   Python modules into a private namespace.  Link against libswigpy so
>   libsvn_swig_py will have direct access to these functions.  See
>   <http://www.swig.org/Doc1.3/Advanced.html> for more information on
>   this technique.

Is this still a problem? Is this patch still valid?

Sander

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org