In article <210217035914.m0144...@mkii.yf.bsdclub.org> futat...@yf.bsdclub.org writes: > However, I don't think it is not an issue of Subversion release tarball > but an issue of FreeBSD ports.
This may be incorrect. It seems it is caused by wrong rule of copy-swig-py: target. > Perhaps symbolic links were missing. "from . import XXX" specifies > relative import from a module. > > [[[ > $ ls -l subversion/bindings/swig/python/libsvn/*.so > lrwxr-xr-x 1 futatuki staff7 19 Feb 17 01:34 > subversion/bindings/swig/python/libsvn/_client.so@ -> ../.libs/_client.so > lrwxr-xr-x 1 futatuki staff7 17 Feb 17 01:34 > subversion/bindings/swig/python/libsvn/_core.so@ -> ../.libs/_core.so > lrwxr-xr-x 1 futatuki staff7 18 Feb 17 01:34 > subversion/bindings/swig/python/libsvn/_delta.so@ -> ../.libs/_delta.so > lrwxr-xr-x 1 futatuki staff7 17 Feb 17 01:34 > subversion/bindings/swig/python/libsvn/_diff.so@ -> ../.libs/_diff.so > lrwxr-xr-x 1 futatuki staff7 15 Feb 17 01:34 > subversion/bindings/swig/python/libsvn/_fs.so@ -> ../.libs/_fs.so > lrwxr-xr-x 1 futatuki staff7 15 Feb 17 01:34 > subversion/bindings/swig/python/libsvn/_ra.so@ -> ../.libs/_ra.so > lrwxr-xr-x 1 futatuki staff7 18 Feb 17 01:34 > subversion/bindings/swig/python/libsvn/_repos.so@ -> ../.libs/_repos.so > lrwxr-xr-x 1 futatuki staff7 15 Feb 17 01:34 > subversion/bindings/swig/python/libsvn/_wc.so@ -> ../.libs/_wc.so > ]]] > > On install, *.so modules will be installed in the same directory in > libsvn/*.py, so I think they works without trouble. > > (I'm sorry, but I didn't try fresh ports tree yet because I'm using custom > ports which support both of Python 2 bindings and Python 3 bindings.) I tried it and found: [[[ $ ls -l subversion/bindings/swig/python/libsvn/*.so lrwxr-xr-x 1 futatuki staff7 13 Feb 17 05:12 subversion/bindings/swig/python/libsvn/*.so@ -> ../.libs/*.so ]]] If copy-swig-py target executed before building subversion/bindings/swig/python/.lib/*.so, this can be occured. Cheers, -- Yasuhito FUTATSUKI <futat...@yf.bsdclub.org>
