You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Max Bowsher <ma...@ukf.net> on 2004/07/18 21:54:40 UTC
Python bindings broken on OS X?
I don't have access to OS X, but when I compile the trunk python bindings,
libtool is showing portability warnings, which seem to say that you can't
link loadable modules against loadable modules on Darwin, and so the build
will fail.
It would be extremely helpful if an OS X user could verify whether this
really is a problem, or whether it's just libtool being paranoid.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Python bindings broken on OS X?
Posted by Ben Collins-Sussman <su...@collab.net>.
On Tue, 2004-07-20 at 10:14, Ben Collins-Sussman wrote:
>
> > I will not take ownership of the libaprutil-cannot-open-shared-object
> > problem at this time, as I am unable to reproduce it.
>
> Will show you reproduction info in a separate thread.
Oops, never mind. It was my own stupid error. I ran 'make; make
swig-py; make install-swig-py' from the rc1 tarball. But I forgot to
run plain old 'make install', so of course the bindings failed to find
the libapr they needed at run-time.
The python bindings build and run just fine in the rc1 tarball, AFAICT.
Move along, nothing to see here. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Python bindings broken on OS X?
Posted by Ben Collins-Sussman <su...@collab.net>.
On Mon, 2004-07-19 at 17:51, Max Bowsher wrote:
> > MaxB, are you "owning" this these problems?
>
> I will own the -l_core problem, but won't work on it until I've resolved the
> OS X 1.1 problem.
Thanks.
>
> I will not take ownership of the libaprutil-cannot-open-shared-object
> problem at this time, as I am unable to reproduce it.
Will show you reproduction info in a separate thread.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Python bindings broken on OS X?
Posted by Max Bowsher <ma...@ukf.net>.
Ben Collins-Sussman wrote:
> On Mon, 2004-07-19 at 08:54, Max Bowsher wrote:
>
>> Ah, ok. I was actually speculating about the trunk python bindings, but
if
>> the 1.1.x branch bindings are broken, then trunk certainly will be too
(so
>> don't bother testing trunk yet.)
>>
>> I will work on fixing this, and post again when I have something new to
for
>> you to test.
>
> So it looks like there are two problems here:
Neither of the problems below are related to the ones I was discussing with
Christian Schaffner above.
>
> * 'make install-swig-py' is broken on today's /trunk. (cmpilato and I
> both can reproduce the -l_core link failure on RH9)
I can reproduce on FC1 too.
> * the python bindings install correctly from the 1.1.0-rc1 tarball, but
> fail at runtime:
>
>>>> from svn import fs
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> File "/usr/local/lib/svn-python/svn/fs.py", line 28, in ?
> import libsvn.fs
> File "/usr/local/lib/svn-python/libsvn/fs.py", line 5, in ?
> import _fs
> ImportError: libaprutil-0.so.0: cannot open shared object file: No such
> file or
> directory
>
> So, um, this second problem definitely looks like something to fix for
> rc2, yah? :-)
WFM, FC1.
Can you post more info about it in a seperate thread?
> MaxB, are you "owning" this these problems?
I will own the -l_core problem, but won't work on it until I've resolved the
OS X 1.1 problem.
I will not take ownership of the libaprutil-cannot-open-shared-object
problem at this time, as I am unable to reproduce it.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Python bindings broken on OS X?
Posted by Ben Collins-Sussman <su...@collab.net>.
On Mon, 2004-07-19 at 08:54, Max Bowsher wrote:
> Ah, ok. I was actually speculating about the trunk python bindings, but if
> the 1.1.x branch bindings are broken, then trunk certainly will be too (so
> don't bother testing trunk yet.)
>
> I will work on fixing this, and post again when I have something new to for
> you to test.
So it looks like there are two problems here:
* 'make install-swig-py' is broken on today's /trunk. (cmpilato and I
both can reproduce the -l_core link failure on RH9)
* the python bindings install correctly from the 1.1.0-rc1 tarball, but
fail at runtime:
>>> from svn import fs
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/local/lib/svn-python/svn/fs.py", line 28, in ?
import libsvn.fs
File "/usr/local/lib/svn-python/libsvn/fs.py", line 5, in ?
import _fs
ImportError: libaprutil-0.so.0: cannot open shared object file: No such
file or
directory
So, um, this second problem definitely looks like something to fix for
rc2, yah? :-)
MaxB, are you "owning" this these problems?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Python bindings broken on OS X?
Posted by Max Bowsher <ma...@ukf.net>.
Christian Schaffner wrote:
> Hi Max
>
> On 18.07.2004, at 23:54, Max Bowsher wrote:
>
>> I don't have access to OS X, but when I compile the trunk python
>> bindings,
>> libtool is showing portability warnings, which seem to say that you
>> can't
>> link loadable modules against loadable modules on Darwin, and so the
>> build
>> will fail.
>
> Yes, indeed, the python building seems to fail on Mac OS X. What i use:
>
> libtool 1.5.6
> autoconf 2.59
> automake 1.8.5
>
> it fails with errors about undefined symbols as shown below. I need to
> use autogen.sh because with the configure of the 1.1.0-rc1 tarball
> (built with libtool 1.4.x) the build fails. So i needed libtool 1.5.6
> to rebuild the configure.
>
> Is there anything i can test for you?
>
> Chris.
>
> PS: The build output:
>
...
> ld: Undefined symbols:
> _PyBuffer_FromMemory
...
Ah, ok. I was actually speculating about the trunk python bindings, but if
the 1.1.x branch bindings are broken, then trunk certainly will be too (so
don't bother testing trunk yet.)
I will work on fixing this, and post again when I have something new to for
you to test.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Python bindings broken on OS X?
Posted by Christian Schaffner <ch...@users.sourceforge.net>.
Hi Max
On 18.07.2004, at 23:54, Max Bowsher wrote:
> I don't have access to OS X, but when I compile the trunk python
> bindings,
> libtool is showing portability warnings, which seem to say that you
> can't
> link loadable modules against loadable modules on Darwin, and so the
> build
> will fail.
Yes, indeed, the python building seems to fail on Mac OS X. What i use:
libtool 1.5.6
autoconf 2.59
automake 1.8.5
it fails with errors about undefined symbols as shown below. I need to
use autogen.sh because with the configure of the 1.1.0-rc1 tarball
(built with libtool 1.4.x) the build fails. So i needed libtool 1.5.6
to rebuild the configure.
Is there anything i can test for you?
Chris.
PS: The build output:
./autogen.sh
...
./configure --prefix=/sw --libexecdir='${prefix}/lib/svn'
--mandir='${prefix}/share/man' --infodir='${prefix}/share/info'
--with-neon=/sw --with-apr=/sw --with-apr-util=/sw --enable-shared
--with-apxs=/sw/sbin/apxs --without-apache --disable-mod-activation
--with-jdk=/System/Library/Frameworks/JavaVM.framework/Versions/
CurrentJDK/Home --with-junit=/sw/share/java/junit/junit.jar
--enable-javahl --enable-swig-bindings=java,perl,python --with-swig=/sw
--with-python=/sw/bin/python2.3 --with-perl=perl5.8.1
PYTHON2=/sw/bin/python2.3 PERL=perl5.8.1
...
make
...
make swig-py
mkdir subversion/bindings/java/javahl/classes
mkdir subversion/bindings/java/javahl/include
mkdir subversion/bindings/swig/java/build
/sw/bin/swig -noruntime -python
-I/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/
bindings/swig
-I/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/include
-I/sw/lib/swig1.3 -DSVN_SWIG_VERSION=103020 -I/sw/include/apr-0
-I/sw/include/apr-0 -I/sw/include
-I/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/
bindings/swig
-I/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/include
-I/sw/lib/swig1.3 -DSVN_SWIG_VERSION=103020 -I/sw/include/apr-0
-I/sw/include/apr-0 -I/sw/include -I/sw/include/python2.3
-I/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/
bindings/swig/python/libsvn_swig_py -o
subversion/bindings/swig/python/svn_client.c
/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/bindings/
swig/svn_client.i
/bin/sh /sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/libtool
--silent --mode=compile gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-I/sw/include/db4 -no-cpp-precomp -I/sw/include -DDARWIN
-DSIGPROCMASK_SETS_THREAD_MASK
-I/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/
bindings/swig
-I/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/include
-I/sw/lib/swig1.3 -DSVN_SWIG_VERSION=103020 -I/sw/include/apr-0
-I/sw/include/apr-0 -I/sw/include
-I/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/
bindings/swig
-I/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/include
-I/sw/lib/swig1.3 -DSVN_SWIG_VERSION=103020 -I/sw/include/apr-0
-I/sw/include/apr-0 -I/sw/include -I/sw/include/python2.3
-I/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/
bindings/swig/python/libsvn_swig_py -prefer-pic -c -o
subversion/bindings/swig/python/svn_client.lo
subversion/bindings/swig/python/svn_client.c
In file included from /sw/include/python2.3/Python.h:70,
from subversion/bindings/swig/python/svn_client.c:14:
/sw/include/python2.3/objimpl.h:255: warning: use of `long double'
type; its size may change in a future release
/sw/include/python2.3/objimpl.h:255: warning: (Long double usage is
reported only once for each file.
/sw/include/python2.3/objimpl.h:255: warning: To disable this warning,
use -Wno-long-double.)
/bin/sh /sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/libtool
--silent --mode=compile gcc -I/sw/include/db4 -no-cpp-precomp
-I/sw/include -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -DSWIGPYTHON
-g -O2 -g -O2 -DNEON_ZLIB -DNEON_SSL
-I/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/
bindings/swig
-I/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/include
-I/sw/lib/swig1.3 -DSVN_SWIG_VERSION=103020 -I/sw/include/apr-0
-I/sw/include/apr-0 -I/sw/include -I/sw/include/python2.3
-I/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/
bindings/swig/python/libsvn_swig_py -I./subversion/include
-I./subversion -I/sw/include/neon -I/sw/include/apr-0
-I/sw/include/apr-0 -I/sw/include -o
subversion/bindings/swig/python/libsvn_swig_py/swigutil_py.lo -c
/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/bindings/
swig/python/libsvn_swig_py/swigutil_py.c
In file included from /sw/include/python2.3/Python.h:70,
from
/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/subversion/bindings/
swig/python/libsvn_swig_py/swigutil_py.c:20:
/sw/include/python2.3/objimpl.h:255: warning: use of `long double'
type; its size may change in a future release
/sw/include/python2.3/objimpl.h:255: warning: (Long double usage is
reported only once for each file.
/sw/include/python2.3/objimpl.h:255: warning: To disable this warning,
use -Wno-long-double.)
cd subversion/bindings/swig/python/libsvn_swig_py && /bin/sh
/sw/src/svn-ssl-1.1.0-rc1-11/subversion-1.1.0-rc1/libtool --silent
--mode=link gcc -g -O2 -g -O2 -DNEON_ZLIB -DNEON_SSL -L/sw/lib
-L/sw/lib -rpath /sw/lib -L/sw/lib -o libsvn_swig_py-1.la
-no-undefined swigutil_py.lo -lswigpy
../../../../../subversion/libsvn_subr/libsvn_subr-1.la
../../../../../subversion/libsvn_delta/libsvn_delta-1.la
/sw/lib/libaprutil-0.la -lldap -llber -lgdbm -ldb-4.2 -lexpat -liconv
/sw/lib/libapr-0.la -lresolv -lpthread -lintl
ld: warning -dylib_install_name /sw/lib/libsvn_swig_py-1.0.dylib not
found in segment address table LD_SEG_ADDR_TABLE
/sw/var/lib/fink/prebound/seg_addr_table
ld: warning prebinding disabled because dependent library:
/sw/lib/libswigpy.0.dylib is not prebound
ld: warning multiple definitions of symbol _locale_charset
/sw/lib/libintl.dylib(localcharset.lo) definition of _locale_charset
/sw/lib/libiconv.dylib(localcharset.o) definition of _locale_charset
ld: Undefined symbols:
_PyBuffer_FromMemory
_PyDict_New
_PyDict_SetItemString
_PyErr_NewException
_PyErr_SetObject
_PyErr_SetString
_PyEval_RestoreThread
_PyEval_SaveThread
_PyExc_TypeError
_PyFile_AsFile
_PyFile_Type
_PyInt_AsLong
_PyInt_FromLong
_PyInt_Type
_PyList_Append
_PyList_New
_PyLong_AsLong
_PyLong_Type
_PyObject_CallFunction
_PyObject_CallMethod
_PyObject_SetAttrString
_PySequence_Check
_PySequence_GetItem
_PySequence_Size
_PyString_FromString
_PyString_Type
_PyType_IsSubtype
__Py_NoneStruct
_PyExc_NameError
_PyFloat_FromDouble
_PyModule_GetDict
_PyObject_CallObject
_PyObject_GetAttr
_PyString_AsString
_PyType_Type
_Py_BuildValue
_Py_InitModule4
/usr/bin/libtool: internal link edit command failed
make: ***
[subversion/bindings/swig/python/libsvn_swig_py/libsvn_swig_py-1.la]
Error 1
### execution of make failed, exit code 2
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Python bindings broken on OS X?
Posted by Max Bowsher <ma...@ukf.net>.
Max Bowsher wrote:
> I don't have access to OS X, but when I compile the trunk python bindings,
> libtool is showing portability warnings, which seem to say that you can't
> link loadable modules against loadable modules on Darwin, and so the build
> will fail.
>
> It would be extremely helpful if an OS X user could verify whether this
> really is a problem, or whether it's just libtool being paranoid.
I forgot to mention... trying to build the perl bindings too would also be
useful.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org