Thank you, thank you so much.
I think I figured out what went wrong.
Even though I clean up the multiple swig version and rebuild subversion
with 'make clean ; make; make swig-py; make install-swig-py', the
process never rebuild the svn*.c file generated by SWIG. After I remove
the whole subversion and start over from the clean subversion,
everything is working now.
I'm a very happy user. It just took me about a week to figure out the
whole thing.
Thanks again,
Tun Tun
>-----Original Message-----
>From: John Szakmeister [mailto:john@szakmeister.net]
>Sent: Wednesday, February 23, 2005 4:07 AM
>To: Tun Tun Naing
>Cc: users@subversion.tigris.org
>Subject: Re: swig py binding
>
>
>On Tuesday 22 February 2005 20:58, Tun Tun Naing wrote:
>> I really appreciate your help.
>>
>> >This line is showing something different. If you followed the
>> >default install, libsvn/_core.so would be in
>/usr/local/lib. Are you
>> >sure you don't have a couple of things all mixed together here?
>>
>> I followed the default install and all the lib files are on
>> /usr/local/lib/svn-python. But when you run python, you
>can't find svn
>> module even if I put the /usr/local/lib/svn-python in
>PYTHONPATH. So I
>> created a link called libsvn and svn under
>> /usr/local/lib/python2.3/site-packages.
>
>echo /usr/local/lib/svn-python \
> > /usr/local/lib/python2.3/site-packages/svn.pth
>
>This does the trick nicely.
>
>> ldd /usr/local/lib/svn-python/libsvn/_core.so
>> libswigpy.so.0 => /usr/local/lib/libswigpy.so.0
>> libsvn_swig_py-1.so.0 => /usr/local/lib/libsvn_swig_py-1.so.0
>> libsvn_delta-1.so.0 => /usr/local/lib/libsvn_delta-1.so.0
>> libsvn_diff-1.so.0 => /usr/local/lib/libsvn_diff-1.so.0
>> libsvn_subr-1.so.0 => /usr/local/lib/libsvn_subr-1.so.0
>> libapr-0.so.0 => /usr/local/apr/lib/libapr-0.so.0
>> libsendfile.so.1 => /lib/libsendfile.so.1
>> librt.so.1 => /lib/librt.so.1
>> libm.so.1 => /lib/libm.so.1
>> libnsl.so.1 => /lib/libnsl.so.1
>> libresolv.so.2 => /lib/libresolv.so.2
>> libpthread.so.1 => /lib/libpthread.so.1
>> libdl.so.1 => /lib/libdl.so.1
>> libsocket.so.1 => /lib/libsocket.so.1
>> libc.so.1 => /lib/libc.so.1
>> libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1
>> libaprutil-0.so.0 => /usr/local/apr/lib/libaprutil-0.so.0
>> libdb-4.2.so => /usr/local/BerkeleyDB.4.2/lib/libdb-4.2.so
>> libexpat.so.0 => /usr/local/apr/lib/libexpat.so.0
>> libaio.so.1 => /lib/libaio.so.1
>> libmd5.so.1 => /lib/libmd5.so.1
>> libmp.so.2 => /lib/libmp.so.2
>> libthread.so.1 => /lib/libthread.so.1
>> /usr/platform/SUNW,Sun-Fire-280R/lib/libc_psr.so.1
>> /usr/platform/SUNW,Sun-Fire-280R/lib/libmd5_psr.so.1
>>
>> >check 'ldd
>/usr/local/lib/python2.3/site-packages/libsvn/_core.so'.
>> >Does it point to the correct SWIG libraries?
>>
>> Yes, it does.
>
>I'm at a loss here. I'm not certain why this would be
>failing. The only
>other tidbit of information that comes to mind is memories different
>versions of libtool not working correctly on Solaris. Do you have any
>other old libraries hanging around?
>
>-John
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 24 17:55:42 2005