On 2021/02/17 6:17, Lev Serebryakov wrote:
> On 16.02.2021 23:52, Yasuhito FUTATSUKI wrote:
>>
>
>>> 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:
On 16.02.2021 23:52, Yasuhito FUTATSUKI wrote:
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.
Yep, it is wrong in case of multi-job build. It works
On 16.02.2021 21:59, Yasuhito FUTATSUKI wrote:
Thank you! That is immensely helpful. Now we can check when and why
that change was introduced.
However, I don't think it is not an issue of Subversion release tarball
but an issue of FreeBSD ports.
This issue is result to update to 1.14.1. I
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
In article
hartman.nat...@gmail.com writes:
> Are you building from a distribution tarball? (As opposed to a
> checkout or export of the 1.14.1 tag in our repository...) If so, did
> you run autogen.sh? I noticed some changes in
> subversion/bindings/swig/INSTALL on trunk that haven't been
In article
hartman.nat...@gmail.com writes:
> On Tue, Feb 16, 2021 at 12:32 PM Lev Serebryakov
> wrote:
> > I found cause, but as I'm not python programmer, I don't understand it.
> >
> > Old "import _XXX" (like "import _core" in
> > subversion/bindings/swig/python/core.py) works, new "from
Nathan Hartman wrote on Tue, 16 Feb 2021 17:15 +00:00:
> You can generate a diff to view the changes with:
>
> $ svn diff \
> https://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/swig/INSTALL\
>
On Tue, Feb 16, 2021 at 12:32 PM Lev Serebryakov
wrote:
> I found cause, but as I'm not python programmer, I don't understand it.
>
> Old "import _XXX" (like "import _core" in
> subversion/bindings/swig/python/core.py) works, new "from . import XXX"
> doesn't.
>
>I've patched these lines
On 16.02.2021 20:15, Nathan Hartman wrote:
Update to 1.14.1 break out-of-tree build of python bindings (with python
3.7).
Are you building from a distribution tarball? (As opposed to a
checkout or export of the 1.14.1 tag in our repository...) If so, did
you run autogen.sh? I noticed
On 16.02.2021 19:51, Yasuhito FUTATSUKI wrote:
Update to 1.14.1 break out-of-tree build of python bindings (with python
3.7).
1.14.0 works with same options, makefiles, etc. 1.14.1 fails to build
bindings when libraries are installed and swig is not installed (bindings are
built as
On Tue, Feb 16, 2021 at 10:05 AM Lev Serebryakov
wrote:
>
>
>Update to 1.14.1 break out-of-tree build of python bindings (with python
> 3.7).
Are you building from a distribution tarball? (As opposed to a
checkout or export of the 1.14.1 tag in our repository...) If so, did
you run
Hi,
On 2021/02/17 0:04, Lev Serebryakov wrote:
>
> Update to 1.14.1 break out-of-tree build of python bindings (with python
> 3.7).
> 1.14.0 works with same options, makefiles, etc. 1.14.1 fails to build
> bindings when libraries are installed and swig is not installed (bindings are
>
Update to 1.14.1 break out-of-tree build of python bindings (with python 3.7).
1.14.0 works with same options, makefiles, etc. 1.14.1 fails to build
bindings when libraries are installed and swig is not installed (bindings are
built as separate ntity, not together with subversion
13 matches
Mail list logo
