On Mon, 13 Apr 2020, Sebastian Ramacher wrote:
This is caused by the ongoing effort to remove Python 3.7. casacore
needs to be rebuilt against the new libboost-python1.67.0
version. But this build fails with:
| -- Looking for python3 specific environment...
| -- Found PythonInterp: /usr/bin/python3.7 (found version "3.7.7")
| -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found version
"3.8.2")
| -- Found Boost: /usr/include (found version "1.67.0")
| CMake Error at
/usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message):
| Could NOT find Boost (missing: python37) (found version "1.67.0")
| Call Stack (most recent call first):
| /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393
(_FPHSA_FAILURE_MESSAGE)
| /usr/share/cmake-3.16/Modules/FindBoost.cmake:2179
(find_package_handle_standard_args)
| python3/CMakeLists-older-cmake.txt:37 (find_package)
| python3/CMakeLists.txt:4 (include)
I guess this depends on CMake finding and trying to use python 3.7 instead
of 3.8, even if python 3.8 libraries are then found and selected. Isn't
there a way to force CMake to use python 3.8? I confess I am more familiar
with autotools than with CMake, but I would be very surprised if there were
not a switch in its config to explicitly select the python to use. I will
try to have a look at the source package and let you know if I find it out.
Thanks anyway, bye
Giacomo
--
_________________________________________________________________
Giacomo Mulas <giacomo.mu...@inaf.it>
_________________________________________________________________
INAF - Osservatorio Astronomico di Cagliari
via della scienza 5 - 09047 Selargius (CA)
tel. +39 070 71180255
mob. : +39 329 6603810
_________________________________________________________________
"When the storms are raging around you, stay right where you are"
(Freddy Mercury)
_________________________________________________________________
