Hi Timo,
On 2022-11-24 22:51, Timo Röhling wrote:
It took me a while, but I found the problem: starting with version
3.15, CMake introduced a new search strategy, so my tests with
cmake_minimum_required(VERSION 3.25)
worked fine, but as soon as you go below 3.15 it breaks again.
I'll upload a
Hi Andrius,
* Andrius Merkys [2022-11-24 13:25]:
find_package(Python 3.6 REQUIRED COMPONENTS Interpreter Development)
However, CMake output is the following:
-- Found Python: /usr/bin/python3.11 (found suitable version "3.11.0",
minimum required is "3.6") found components: Interpreter
Control: reopen -1
Control: found -1 3.25.0-2
Hello,
The bug still remains in 3.25.0-2. I am attempting to build promod3
3.2.1+ds-6 which has:
find_package(Python 3.6 REQUIRED COMPONENTS Interpreter Development)
However, CMake output is the following:
-- Found Python: /usr/bin/python3.11
Hi,
On 2022-11-22 15:20, Timo Röhling wrote:
I have an improved patch committed to Salsa, I'm just waiting for the
FTP team to approve the split of emacs-cmake-mode. I'm going to give
them a few more days before I consider releasing the bugfix on its
own, if you don't mind.
Thanks for prompt
Control: tags -1 + pending
* Andrius Merkys [2022-11-22 14:38]:
Due to the added support for Python 3.11, CMake's FindPython.cmake no
longer returns the default Python version (3.10 currently), but
returns the latest one (3.11 currently). Due to this, some packages
FTBFS (for example,
Package: cmake-data
Version: 3.25.0-1
Severity: important
Control: affects -1 src:openstructure
Control: affects -1 src:promod3
Dear Maintainer,
Due to the added support for Python 3.11, CMake's FindPython.cmake no
longer returns the default Python version (3.10 currently), but returns
the
6 matches
Mail list logo
