Hi,
Following the instructions for reporting a bug, I write to this list.
I'm not subscribed to the list, so thanks for CCing me when replying.
I'm Pierre Labastie, one of the maintainers of BLFS [1]. I use the build
method described in the BLFS development book.
Please ask if you need further details.
Here are the last lines of the output of configure for
subversion-1.11.1, with apr-1.7.0 installed:
--------------
checking for swig... none
configure: Configuring python swig binding
checking for Python includes... -I/usr/include/python3.7m
checking for compiling Python extensions... gcc -pthread -fPIC
checking for linking Python extensions... gcc -pthread -shared
checking for linking Python libraries...
checking for apr_int64_t Python/C API format string...
configure: error: failed to recognize APR_INT64_T_FMT on this platform
-------------
Now, with apr-1.6.5 installed, here is the corresponding bit of
configure output:
-------------
checking for swig... none
configure: Configuring python swig binding
checking for Python includes... -I/usr/include/python3.7m
checking for compiling Python extensions... gcc -pthread -fPIC
checking for linking Python extensions... gcc -pthread -shared
checking for linking Python libraries...
checking for apr_int64_t Python/C API format string... l
checking perl version... 5028001
checking for ctypesgen.py... none
[...]
------------
I think it is because apr.h now defines APR_INT64_T_FMT as PRId64,
instead of formerly %ld. I've not found anything related in the subversion
repository, nor in the bug tracker. Please forgive me if this has
already been reported.
Side note: why is it that python swig bindings are configured when swig
is 'none'?
Anyway, even if swig is present, the build failure still exists...
Regards
P. Labastie
[1] http://www.linuxfromscratch.org/blfs/read.html
Received on 2019-04-09 17:34:12 CEST