Michael Pilato wrote on Fri, 13 Mar 2020 12:53 +00:00:
> > https://home.apache.org/~danielsh/subversion-20200311_001/subversion-nightly-r1875088.tar.gz
> > https://home.apache.org/~danielsh/subversion-20200311_001/subversion-nightly-r1875088.tar.gz.asc
> >
> > For future reference, that's the output of «release.py build-env trunk-nightly &&
> > release.py roll trunk-nightly $(svn info --show-item=revision -- $REPOS_URL)»
> > in a plain Debian stable VM with the following packages installed:
> > subversion python-yaml pax gettext m4
> >
> > You may need to pass PYTHON=python3 to configure.
>
> Daniel, thanks for this -- the filedrop *and* the education. I've
> gotten farther along in my auxiliary work with this than I was getting
> without it. (I couldn't managed to get "release.py build-env" to
> succeed. Shoulda tried a clean VM.)
>
> One thing that appears to be different about this tarball than a
> typical release tarball is the absence of the swig-generated wrapper
> files (...python/svn_client.c, etc.). I'm going to take a crack at
> replicating your release environment (the Debian VM, etc.), but is
> there a flag or package or something that was omitted that would
> obviously have resulted in the missing SWIG-generated files?
>
In addition to futatuki's point about SWIG_PY_OPTS, I wonder if the fact
there wasn't a swig installed in the default $PATH made autogen.sh think
swig isn't installed and silently skip generating the swig files.
(release.py downloads and builds its own swig — see SwigDep — and ought
to point autogen.sh to it, but perhaps it neglects to do so.) This
could be tested by installing the swig (and, for good measure,
py3c-dev) packages prior to rolling and seeing if that changes the outcome.
> Thanks, again.
You're welcome.
Daniel
Received on 2020-03-13 17:15:03 CET