On 2019-08-04 21:21, Ken Moffat via blfs-dev wrote:
I think that we had something related to either fixing, or not
building, the subversion python2 bindings in 1.12.0, but on the face
of it they can be built in 1.12.2. I hit this a day ago, at that
point I wondered if my version of swig was old (it isn't) and went
ahead without the perl bindings.
I see that the book mentions -j1 at several places, so I gave it
another try today, but it still fails (reformatted when I pasted it)
:
/usr/bin/swig -I/scratch/working/subversion-1.12.2/subversion
-I/scratch/working/subversion-1.12.2/subversion/include
-I/scratch/working/subversion-1.12.2/subversion/bindings/swig
-I/scratch/working/subversion-1.12.2/subversion/bindings/swig/include
-I/scratch/working/subversion-1.12.2/subversion/bindings/swig/proxy
-I/scratch/working/subversion-1.12.2/subversion/bindings/swig/proxy
-I/usr/include/apr-1 -I/usr/include/apr-1 -I/usr/include -python
-classic -o subversion/bindings/swig/python/svn_client.c
./subversion/bindings/swig/svn_client.i
Deprecated command line option: -classic. This option is no longer
supported.
make: *** [build-outputs.mk:292:
subversion/bindings/swig/python/svn_client.c] Error 1
I am, of course, happy to not build these bindings - but the book
appears to be broken. Or, again, maybe it's just me.
Hi Ken,
That's most definitely not you. I think the seds were removed
prematurely.
Can you try these:
sed -i '/define.*MEMORY/a#define SWIG_POINTER_NO_NULL 0x4' \
subversion/bindings/swig/proxy/swigrun.swg &&
sed -i 's/classic/nofastunpack/' build.conf
And see if that allows it to build? Also, the tests for the Python
bindings are most likely still broken (it'll fail right away with a
failed import)
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
