On 09/04/2019 16:19, Pierre Labastie via lfs-dev wrote:
Running configure as per the book, I get:
-----
[...]
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
-----
Downgrading apr to 1.6.5, I get:
-----
[...]
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
[...]
-----
Note that there must be something wrong in configure, since python
swig bindings shouldn't be configured if swig is none...
Actually, Adding the following sed allows configure to pass:
----
sed '/PYTHON".!=/s/"none"/& -a "$SWIG" != "none"/' -i configure
----
Note that the above sed will not be effective if swig is present. In
this case, --without-swig would be needed in addition to the sed.
And in any case, python bindings cannot be built... It's a change in
/usr/include/apr-1/apr.h, which cannot easily be worked around.
I'll try to report upstream.
Maybe it's better to downgrade to apr-1.6.5 until subversion is fixed.
Pierre
Oops, I just realized I sent this to the wrong list... Moving to
blfs-dev. Sorry
Pierre
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
