On 2020/06/03 16:39, Yasuhito FUTATSUKI wrote:
> On 2020/06/02 14:52, Yasuhito FUTATSUKI wrote:
>> On 2020/06/02 6:01, Karl Berry wrote:
>
>>> Also, py3c is apparently necessary. Again it would be nice if configure
>>> bailed out if it's not present.
>>
>> In this case it should also stop with the
On 2020/06/02 14:52, Yasuhito FUTATSUKI wrote:
> On 2020/06/02 6:01, Karl Berry wrote:
>> Also, py3c is apparently necessary. Again it would be nice if configure
>> bailed out if it's not present.
>
> In this case it should also stop with the message:
>
> SWIG python disabled at configure ti
On 2020/06/02 20:54, Yasuhito FUTATSUKI wrote:
> On 2020/06/02 14:52, Yasuhito FUTATSUKI wrote:
>
>> The 1.14.0 release tarball contains also '.swig_pl_checked' and
>> '.swig_rb_checked' files. Should they omit from release tarball?
>
> These .swig_*_checked files are created by 'sh autogen.sh --
If you really used Python 2.6 (not Python 2.7)
You are right, I (that is, CentOS 7) has python 2.7.5.
Sorry about misstatement. -k
On 2020/06/02 14:52, Yasuhito FUTATSUKI wrote:
> The 1.14.0 release tarball contains also '.swig_pl_checked' and
> '.swig_rb_checked' files. Should they omit from release tarball?
These .swig_*_checked files are created by 'sh autogen.sh --release',
when it runs 'make -f autogen-standalone.mk aut
Hi,
(Cc: dev@)
On 2020/06/02 6:01, Karl Berry wrote:
> With svn-1.14.0, if "python" is Python 2 (it's still 2.6.6 on CentOS7),
> and --with-swig is given, make swig-py succeeds, but check-swig-py fails
> with:
>
> cd /usr/local/src/subversion-1.14.0/subversion/bindings/swig/python; \
> /us
6 matches
Mail list logo
