robotpkg/wip/py-osqp bulk build results

=> Checking for clear installation ===> Installing bootstrap dependencies for py314-osqp-0.6.1 => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/Ubuntu-26.04-x86_64/All/digest-20080510.tgz => Installing /opt/robotpkg/var/lib/robotpkg/packages/bsd/Ubuntu-26.04-x86_64/All/tnftp-20151004~ssl.tgz ===> Checking bootstrap dependencies for py314-osqp-0.6.1 => Required robotpkg package digest>=20080510: digest-20080510 found => Required robotpkg package tnftp>=20130505~ssl: tnftp-20151004~ssl found => Required system package gnupg>=1: gnupg-2.4.8 found => Required system package gzip: gzip-1.14 found => Required system package pax and tar archivers: pax found => Required system package pkg_install>=20110805.12: pkg_install-20211115.4 found => Required system package pkgrepo2deb>=1.9: pkgrepo2deb-1.16 found ===> Done bootstrap-depends for py314-osqp-0.6.1 ===> Installing full dependencies for py314-osqp-0.6.1 => Dependency digest-20080510 already installed => Dependency tnftp-20151004~ssl already installed ===> Checking build options for py314-osqp-0.6.1 => Building with no option. ===> Checking alternatives for py314-osqp-0.6.1 => Use the GNU C++ compiler: c++-compiler provided by g++>=3 => Use the GNU C compiler: c-compiler provided by gcc>=3 => Use python-3.14: python>=2.5 provided by python314>=3.14<3.15 ===> Checking dependencies for py314-osqp-0.6.1 => Required system package g++>=3: g++-15.2.0 found => Required system package gcc>=3: gcc-15.2.0 found => Required system package libstdc++: libstdc++ found => Required system package py314-numpy>=1: py314-numpy-2.3.5 found => Required system package py314-scipy>=0.17.0: py314-scipy-1.16.3 found => Required system package py314-setuptools: py314-setuptools found => Required system package python314>=3.14<3.15: python314-3.14.4 found ===> Done depends for py314-osqp-0.6.1 ===> Extracting for py314-osqp-0.6.1 => SHA1 checksums OK => RMD160 checksums OK ===> Configuring for py314-osqp-0.6.1 ===> Building for py314-osqp-0.6.1 /usr/lib/python3/dist-packages/setuptools/__init__.py:94: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! ******************************************************************************** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. ******************************************************************************** !! dist.fetch_build_eggs(dist.setup_requires) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'osqp.codegen.files_to_generate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'osqp.codegen.files_to_generate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'osqp.codegen.files_to_generate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'osqp.codegen.files_to_generate' to be distributed and are already explicitly excluding 'osqp.codegen.files_to_generate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'osqp.codegen.sources.configure' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'osqp.codegen.sources.configure' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'osqp.codegen.sources.configure' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'osqp.codegen.sources.configure' to be distributed and are already explicitly excluding 'osqp.codegen.sources.configure' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'osqp.codegen.sources.include' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'osqp.codegen.sources.include' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'osqp.codegen.sources.include' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'osqp.codegen.sources.include' to be distributed and are already explicitly excluding 'osqp.codegen.sources.include' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'osqp.codegen.sources.src' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'osqp.codegen.sources.src' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'osqp.codegen.sources.src' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'osqp.codegen.sources.src' to be distributed and are already explicitly excluding 'osqp.codegen.sources.src' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) warning: build_py: byte-compiling is disabled, skipping. CMake Error at CMakeLists.txt:2 (cmake_minimum_required): Compatibility with CMake < 3.5 has been removed from CMake. Update the VERSION argument <min> value. Or, use the <min>...<max> syntax to tell CMake that the project requires at least <min> but has been updated to work with policies introduced by <max> or earlier. Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway. Error: could not find CMAKE_PROJECT_NAME in Cache error: [Errno 2] No such file or directory: 'osqp_sources/build/out/libosqp.a' An unexpected error occured. The last 10 log lines are shown below. | -- Configuring incomplete, errors occurred! | Update the VERSION argument <min> value. Or, use the <min>...<max> syntax | to tell CMake that the project requires at least <min> but has been updated | to work with policies introduced by <max> or earlier. | | Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway. | | | Error: could not find CMAKE_PROJECT_NAME in Cache | error: [Errno 2] No such file or directory: 'osqp_sources/build/out/libosqp.a' For details or bug reports, check the complete log file in: /local/robotpkg/var/tmp/robotpkg/wip/py-osqp/work/build.log make[3]: *** [../../mk/sysdep/py-setuptools.mk:48: do-build-setuptools(/local/robotpkg/var/tmp/robotpkg/wip/py-osqp/work/osqp-0.6.1)] Error 1 make[2]: *** [/local/robotpkg/var/lib/robotpkg/mk/pkg/package.mk:42: pkg-check-installed] Error 2 => Marking py314-osqp-0.6.1 as broken ERROR: make: *** [package] Error 2 ===> Deinstalling for py314-osqp Removed digest-20080510 Removed tnftp-20151004~ssl