Problems with swig extensions

[rb...@apache.org]

I have been trying to get the swig extensions to work for the last few
days, but not being a python programmer, I am not making much progress.

The first error I got was about the -noproxy flag that is being passed to
swig.  I am using swig 1.3.16, which doesn't understand the -noproxy flag
according to the package I have.  I fixed this by removing that flag, but
I don't understand why that was required.

Once I did finally get things built, I have tried using svnlook.py, but I
received this error:

Traceback (most recent call last):
  File "./svnlook.py", line 23, in ?
    from svn import fs, util, delta, _repos
  File "/usr/local/lib/python2.2/site-packages/svn/fs.py", line 19, in ?
    import _fs
ImportError: dynamic module does not define init function (init_fs)


I looked at this briefly, but I haven't made much progress.  The best I
have found so far is that init_fs isn't an exported symbol, but init__fs
is.

Can anybody help me out?

Ryan


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

Re: Problems with swig extensions

[rb...@apache.org]

On 21 Nov 2002, Edward S. Marshall wrote:

> On Thu, 2002-11-21 at 20:01, rbb@apache.org wrote:
> > The first error I got was about the -noproxy flag that is being passed to
> > swig.  I am using swig 1.3.16, which doesn't understand the -noproxy flag
> > according to the package I have.  I fixed this by removing that flag, but
> > I don't understand why that was required.
>
> It sounds to me like you might be picking up another copy of swig in
> your path. Any chance of multiple copies being installed? Also, what
> version of subversion are you dealing with (a particular release, a
> particular repository version, etc), version of python, platform, etc?

repository version is head of the trunk, python 2.2, swig 1.3.16.  I meant
to put all of this in my initial message.  I am tyring to make this work
on linux.

Ryan


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

Re: Problems with swig extensions

["Edward S. Marshall" <es...@logic.net>]

On Thu, 2002-11-21 at 20:01, rbb@apache.org wrote:
> The first error I got was about the -noproxy flag that is being passed to
> swig.  I am using swig 1.3.16, which doesn't understand the -noproxy flag
> according to the package I have.  I fixed this by removing that flag, but
> I don't understand why that was required.

It sounds to me like you might be picking up another copy of swig in
your path. Any chance of multiple copies being installed? Also, what
version of subversion are you dealing with (a particular release, a
particular repository version, etc), version of python, platform, etc?

> Traceback (most recent call last):
>   File "./svnlook.py", line 23, in ?
>     from svn import fs, util, delta, _repos
>   File "/usr/local/lib/python2.2/site-packages/svn/fs.py", line 19, in ?
>     import _fs
> ImportError: dynamic module does not define init function (init_fs)

This is similar to the kind of stuff I was running into when I was
trying to get the bindings built for multiple versions of python
(necessitating multiple swig installations). It sure sounds like you
might be bumping into another version of a swig/python combination that
you built against, and are now trying to run it with a different version
(or the build simply failed completely, and you have shared objects that
can't be loaded).

> I looked at this briefly, but I haven't made much progress.  The best I
> have found so far is that init_fs isn't an exported symbol, but init__fs
> is.

init_fs is exported in the version I built. This really sounds like you
built using an older (or "different" ;-) version of swig.

-- 
Edward S. Marshall <es...@logic.net>
http://esm.logic.net/