2025-09-14T09:27:20,950 Created temporary directory: /tmp/pip-build-tracker-kgk8an7e 2025-09-14T09:27:20,951 Initialized build tracking at /tmp/pip-build-tracker-kgk8an7e 2025-09-14T09:27:20,951 Created build tracker: /tmp/pip-build-tracker-kgk8an7e 2025-09-14T09:27:20,951 Entered build tracker: /tmp/pip-build-tracker-kgk8an7e 2025-09-14T09:27:20,951 Created temporary directory: /tmp/pip-wheel-vx03i0po 2025-09-14T09:27:20,954 Created temporary directory: /tmp/pip-ephem-wheel-cache-bc2xxy04 2025-09-14T09:27:21,011 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2025-09-14T09:27:21,014 2 location(s) to search for versions of libhupf: 2025-09-14T09:27:21,014 * https://pypi.org/simple/libhupf/ 2025-09-14T09:27:21,014 * https://www.piwheels.org/simple/libhupf/ 2025-09-14T09:27:21,014 Fetching project page and analyzing links: https://pypi.org/simple/libhupf/ 2025-09-14T09:27:21,014 Getting page https://pypi.org/simple/libhupf/ 2025-09-14T09:27:21,015 Found index url https://pypi.org/simple/ 2025-09-14T09:27:21,166 Fetched page https://pypi.org/simple/libhupf/ as application/vnd.pypi.simple.v1+json 2025-09-14T09:27:21,169 Skipping link: No binaries permitted for libhupf: https://files.pythonhosted.org/packages/23/78/61fac0f6143f3d78ce089f3269b9533ecf2852d5ef7bbaafb0eb5542534f/libhupf-0.1-py2.py3-none-win32.whl (from https://pypi.org/simple/libhupf/) 2025-09-14T09:27:21,170 Skipping link: No binaries permitted for libhupf: https://files.pythonhosted.org/packages/03/25/92fca6ccac0d0dd1a35c7e6fca4b2a153e6b40e92765c9345ea9cc0c1f26/libhupf-0.1-py2.py3-none-win_amd64.whl (from https://pypi.org/simple/libhupf/) 2025-09-14T09:27:21,170 Found link https://files.pythonhosted.org/packages/96/5b/9b2dfdb0ceaabc9c0de2d37e552f5e4aaa2ef213b636527434b8a616e167/libhupf-0.1.tar.gz (from https://pypi.org/simple/libhupf/), version: 0.1 2025-09-14T09:27:21,170 Skipping link: No binaries permitted for libhupf: https://files.pythonhosted.org/packages/4d/b9/c7c4bae3869f8b4fda2475423146c0770258572b82e2710ffbd2c1a31d32/libhupf-0.11-py2.py3-none-win32.whl (from https://pypi.org/simple/libhupf/) 2025-09-14T09:27:21,171 Skipping link: No binaries permitted for libhupf: https://files.pythonhosted.org/packages/26/f2/8c2d0bfb55a8ad64a3f9d2744f455e483caeafdb072e74260a6911ddfdd9/libhupf-0.11-py2.py3-none-win_amd64.whl (from https://pypi.org/simple/libhupf/) 2025-09-14T09:27:21,171 Found link https://files.pythonhosted.org/packages/86/c2/d6858f8c3c171cfe3f3def2ffe5ee7bebdfb0b3f439002ce31db50a2fe16/libhupf-0.11.tar.gz (from https://pypi.org/simple/libhupf/), version: 0.11 2025-09-14T09:27:21,172 Fetching project page and analyzing links: https://www.piwheels.org/simple/libhupf/ 2025-09-14T09:27:21,172 Getting page https://www.piwheels.org/simple/libhupf/ 2025-09-14T09:27:21,174 Found index url https://www.piwheels.org/simple/ 2025-09-14T09:27:21,272 Fetched page https://www.piwheels.org/simple/libhupf/ as text/html 2025-09-14T09:27:21,273 Skipping link: No binaries permitted for libhupf: https://archive1.piwheels.org/simple/libhupf/libhupf-0.1-py3-none-any.whl#sha256=304ccba53f08bd5d264ae6d527609f3bb904283cb7d159514516badb7cc7ab24 (from https://www.piwheels.org/simple/libhupf/) 2025-09-14T09:27:21,274 Skipping link: not a file: https://www.piwheels.org/simple/libhupf/ 2025-09-14T09:27:21,274 Skipping link: not a file: https://pypi.org/simple/libhupf/ 2025-09-14T09:27:21,298 Given no hashes to check 1 links for project 'libhupf': discarding no candidates 2025-09-14T09:27:21,299 Collecting libhupf==0.11 2025-09-14T09:27:21,300 Created temporary directory: /tmp/pip-unpack-kbykfbqg 2025-09-14T09:27:21,440 Downloading libhupf-0.11.tar.gz (45 kB) 2025-09-14T09:27:21,489 Added libhupf==0.11 from https://files.pythonhosted.org/packages/86/c2/d6858f8c3c171cfe3f3def2ffe5ee7bebdfb0b3f439002ce31db50a2fe16/libhupf-0.11.tar.gz to build tracker '/tmp/pip-build-tracker-kgk8an7e' 2025-09-14T09:27:21,490 Running setup.py (path:/tmp/pip-wheel-vx03i0po/libhupf_3e48f9efe53c4cdea44f23395554b33d/setup.py) egg_info for package libhupf 2025-09-14T09:27:21,491 Created temporary directory: /tmp/pip-pip-egg-info-bi7ks71k 2025-09-14T09:27:21,491 Preparing metadata (setup.py): started 2025-09-14T09:27:21,492 Running command python setup.py egg_info 2025-09-14T09:27:22,703 running egg_info 2025-09-14T09:27:22,778 creating /tmp/pip-pip-egg-info-bi7ks71k/libhupf.egg-info 2025-09-14T09:27:22,778 writing /tmp/pip-pip-egg-info-bi7ks71k/libhupf.egg-info/PKG-INFO 2025-09-14T09:27:22,779 writing dependency_links to /tmp/pip-pip-egg-info-bi7ks71k/libhupf.egg-info/dependency_links.txt 2025-09-14T09:27:22,780 writing top-level names to /tmp/pip-pip-egg-info-bi7ks71k/libhupf.egg-info/top_level.txt 2025-09-14T09:27:22,780 writing manifest file '/tmp/pip-pip-egg-info-bi7ks71k/libhupf.egg-info/SOURCES.txt' 2025-09-14T09:27:23,004 reading manifest file '/tmp/pip-pip-egg-info-bi7ks71k/libhupf.egg-info/SOURCES.txt' 2025-09-14T09:27:23,004 reading manifest template 'MANIFEST.in' 2025-09-14T09:27:23,010 writing manifest file '/tmp/pip-pip-egg-info-bi7ks71k/libhupf.egg-info/SOURCES.txt' 2025-09-14T09:27:23,121 Preparing metadata (setup.py): finished with status 'done' 2025-09-14T09:27:23,126 Source in /tmp/pip-wheel-vx03i0po/libhupf_3e48f9efe53c4cdea44f23395554b33d has version 0.11, which satisfies requirement libhupf==0.11 from https://files.pythonhosted.org/packages/86/c2/d6858f8c3c171cfe3f3def2ffe5ee7bebdfb0b3f439002ce31db50a2fe16/libhupf-0.11.tar.gz 2025-09-14T09:27:23,126 Removed libhupf==0.11 from https://files.pythonhosted.org/packages/86/c2/d6858f8c3c171cfe3f3def2ffe5ee7bebdfb0b3f439002ce31db50a2fe16/libhupf-0.11.tar.gz from build tracker '/tmp/pip-build-tracker-kgk8an7e' 2025-09-14T09:27:23,129 Created temporary directory: /tmp/pip-unpack-1emq5qxr 2025-09-14T09:27:23,129 Created temporary directory: /tmp/pip-unpack-puit4kg2 2025-09-14T09:27:23,129 Building wheels for collected packages: libhupf 2025-09-14T09:27:23,131 Created temporary directory: /tmp/pip-wheel-pu1dqmug 2025-09-14T09:27:23,131 DEPRECATION: Building 'libhupf' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'libhupf'. Discussion can be found at https://github.com/pypa/pip/issues/6334 2025-09-14T09:27:23,132 Building wheel for libhupf (setup.py): started 2025-09-14T09:27:23,133 Destination directory: /tmp/pip-wheel-pu1dqmug 2025-09-14T09:27:23,133 Running command python setup.py bdist_wheel 2025-09-14T09:27:24,190 running bdist_wheel 2025-09-14T09:27:24,480 running build 2025-09-14T09:27:24,480 running build_py 2025-09-14T09:27:24,555 creating build/lib.linux-armv7l-cpython-313/libhupf 2025-09-14T09:27:24,556 copying libhupf/__init__.py -> build/lib.linux-armv7l-cpython-313/libhupf 2025-09-14T09:27:24,556 running egg_info 2025-09-14T09:27:24,627 writing libhupf.egg-info/PKG-INFO 2025-09-14T09:27:24,628 writing dependency_links to libhupf.egg-info/dependency_links.txt 2025-09-14T09:27:24,629 writing top-level names to libhupf.egg-info/top_level.txt 2025-09-14T09:27:24,703 reading manifest file 'libhupf.egg-info/SOURCES.txt' 2025-09-14T09:27:24,705 reading manifest template 'MANIFEST.in' 2025-09-14T09:27:24,711 writing manifest file 'libhupf.egg-info/SOURCES.txt' 2025-09-14T09:27:24,713 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'libhupf.gcc' is absent from the `packages` configuration. 2025-09-14T09:27:24,713 !! 2025-09-14T09:27:24,713 ******************************************************************************** 2025-09-14T09:27:24,713 ############################ 2025-09-14T09:27:24,713 # Package would be ignored # 2025-09-14T09:27:24,713 ############################ 2025-09-14T09:27:24,713 Python recognizes 'libhupf.gcc' as an importable package[^1], 2025-09-14T09:27:24,713 but it is absent from setuptools' `packages` configuration. 2025-09-14T09:27:24,714 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-14T09:27:24,714 package, please make sure that 'libhupf.gcc' is explicitly added 2025-09-14T09:27:24,714 to the `packages` configuration field. 2025-09-14T09:27:24,714 Alternatively, you can also rely on setuptools' discovery methods 2025-09-14T09:27:24,714 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-14T09:27:24,714 instead of `find_packages(...)`/`find:`). 2025-09-14T09:27:24,714 You can read more about "package discovery" on setuptools documentation page: 2025-09-14T09:27:24,714 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-14T09:27:24,715 If you don't want 'libhupf.gcc' to be distributed and are 2025-09-14T09:27:24,715 already explicitly excluding 'libhupf.gcc' via 2025-09-14T09:27:24,715 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-14T09:27:24,715 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-14T09:27:24,715 combination with a more fine grained `package-data` configuration. 2025-09-14T09:27:24,715 You can read more about "package data files" on setuptools documentation page: 2025-09-14T09:27:24,715 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-14T09:27:24,716 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-14T09:27:24,716 even if it does not contain any `.py` files. 2025-09-14T09:27:24,716 On the other hand, currently there is no concept of package data 2025-09-14T09:27:24,716 directory, all directories are treated like packages. 2025-09-14T09:27:24,716 ******************************************************************************** 2025-09-14T09:27:24,716 !! 2025-09-14T09:27:24,716 check.warn(importable) 2025-09-14T09:27:24,716 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'libhupf.inc.hupf' is absent from the `packages` configuration. 2025-09-14T09:27:24,716 !! 2025-09-14T09:27:24,717 ******************************************************************************** 2025-09-14T09:27:24,717 ############################ 2025-09-14T09:27:24,717 # Package would be ignored # 2025-09-14T09:27:24,717 ############################ 2025-09-14T09:27:24,717 Python recognizes 'libhupf.inc.hupf' as an importable package[^1], 2025-09-14T09:27:24,717 but it is absent from setuptools' `packages` configuration. 2025-09-14T09:27:24,717 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-14T09:27:24,717 package, please make sure that 'libhupf.inc.hupf' is explicitly added 2025-09-14T09:27:24,717 to the `packages` configuration field. 2025-09-14T09:27:24,718 Alternatively, you can also rely on setuptools' discovery methods 2025-09-14T09:27:24,718 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-14T09:27:24,718 instead of `find_packages(...)`/`find:`). 2025-09-14T09:27:24,718 You can read more about "package discovery" on setuptools documentation page: 2025-09-14T09:27:24,718 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-14T09:27:24,718 If you don't want 'libhupf.inc.hupf' to be distributed and are 2025-09-14T09:27:24,718 already explicitly excluding 'libhupf.inc.hupf' via 2025-09-14T09:27:24,718 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-14T09:27:24,719 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-14T09:27:24,719 combination with a more fine grained `package-data` configuration. 2025-09-14T09:27:24,719 You can read more about "package data files" on setuptools documentation page: 2025-09-14T09:27:24,719 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-14T09:27:24,719 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-14T09:27:24,719 even if it does not contain any `.py` files. 2025-09-14T09:27:24,719 On the other hand, currently there is no concept of package data 2025-09-14T09:27:24,720 directory, all directories are treated like packages. 2025-09-14T09:27:24,720 ******************************************************************************** 2025-09-14T09:27:24,720 !! 2025-09-14T09:27:24,720 check.warn(importable) 2025-09-14T09:27:24,720 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'libhupf.inc.hupf.rrp' is absent from the `packages` configuration. 2025-09-14T09:27:24,720 !! 2025-09-14T09:27:24,720 ******************************************************************************** 2025-09-14T09:27:24,720 ############################ 2025-09-14T09:27:24,720 # Package would be ignored # 2025-09-14T09:27:24,720 ############################ 2025-09-14T09:27:24,721 Python recognizes 'libhupf.inc.hupf.rrp' as an importable package[^1], 2025-09-14T09:27:24,721 but it is absent from setuptools' `packages` configuration. 2025-09-14T09:27:24,721 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-14T09:27:24,721 package, please make sure that 'libhupf.inc.hupf.rrp' is explicitly added 2025-09-14T09:27:24,721 to the `packages` configuration field. 2025-09-14T09:27:24,721 Alternatively, you can also rely on setuptools' discovery methods 2025-09-14T09:27:24,721 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-14T09:27:24,721 instead of `find_packages(...)`/`find:`). 2025-09-14T09:27:24,722 You can read more about "package discovery" on setuptools documentation page: 2025-09-14T09:27:24,722 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-14T09:27:24,722 If you don't want 'libhupf.inc.hupf.rrp' to be distributed and are 2025-09-14T09:27:24,722 already explicitly excluding 'libhupf.inc.hupf.rrp' via 2025-09-14T09:27:24,722 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-14T09:27:24,722 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-14T09:27:24,722 combination with a more fine grained `package-data` configuration. 2025-09-14T09:27:24,722 You can read more about "package data files" on setuptools documentation page: 2025-09-14T09:27:24,723 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-14T09:27:24,723 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-14T09:27:24,723 even if it does not contain any `.py` files. 2025-09-14T09:27:24,723 On the other hand, currently there is no concept of package data 2025-09-14T09:27:24,723 directory, all directories are treated like packages. 2025-09-14T09:27:24,723 ******************************************************************************** 2025-09-14T09:27:24,723 !! 2025-09-14T09:27:24,724 check.warn(importable) 2025-09-14T09:27:24,724 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'libhupf.inc.hupf.rrr' is absent from the `packages` configuration. 2025-09-14T09:27:24,724 !! 2025-09-14T09:27:24,724 ******************************************************************************** 2025-09-14T09:27:24,724 ############################ 2025-09-14T09:27:24,724 # Package would be ignored # 2025-09-14T09:27:24,724 ############################ 2025-09-14T09:27:24,724 Python recognizes 'libhupf.inc.hupf.rrr' as an importable package[^1], 2025-09-14T09:27:24,724 but it is absent from setuptools' `packages` configuration. 2025-09-14T09:27:24,725 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-14T09:27:24,725 package, please make sure that 'libhupf.inc.hupf.rrr' is explicitly added 2025-09-14T09:27:24,725 to the `packages` configuration field. 2025-09-14T09:27:24,725 Alternatively, you can also rely on setuptools' discovery methods 2025-09-14T09:27:24,725 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-14T09:27:24,725 instead of `find_packages(...)`/`find:`). 2025-09-14T09:27:24,725 You can read more about "package discovery" on setuptools documentation page: 2025-09-14T09:27:24,725 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-14T09:27:24,726 If you don't want 'libhupf.inc.hupf.rrr' to be distributed and are 2025-09-14T09:27:24,726 already explicitly excluding 'libhupf.inc.hupf.rrr' via 2025-09-14T09:27:24,726 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-14T09:27:24,726 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-14T09:27:24,726 combination with a more fine grained `package-data` configuration. 2025-09-14T09:27:24,726 You can read more about "package data files" on setuptools documentation page: 2025-09-14T09:27:24,726 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-14T09:27:24,727 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-14T09:27:24,727 even if it does not contain any `.py` files. 2025-09-14T09:27:24,727 On the other hand, currently there is no concept of package data 2025-09-14T09:27:24,727 directory, all directories are treated like packages. 2025-09-14T09:27:24,727 ******************************************************************************** 2025-09-14T09:27:24,727 !! 2025-09-14T09:27:24,727 check.warn(importable) 2025-09-14T09:27:24,727 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'libhupf.src' is absent from the `packages` configuration. 2025-09-14T09:27:24,727 !! 2025-09-14T09:27:24,728 ******************************************************************************** 2025-09-14T09:27:24,728 ############################ 2025-09-14T09:27:24,728 # Package would be ignored # 2025-09-14T09:27:24,728 ############################ 2025-09-14T09:27:24,728 Python recognizes 'libhupf.src' as an importable package[^1], 2025-09-14T09:27:24,728 but it is absent from setuptools' `packages` configuration. 2025-09-14T09:27:24,728 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-14T09:27:24,728 package, please make sure that 'libhupf.src' is explicitly added 2025-09-14T09:27:24,728 to the `packages` configuration field. 2025-09-14T09:27:24,729 Alternatively, you can also rely on setuptools' discovery methods 2025-09-14T09:27:24,729 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-14T09:27:24,729 instead of `find_packages(...)`/`find:`). 2025-09-14T09:27:24,729 You can read more about "package discovery" on setuptools documentation page: 2025-09-14T09:27:24,729 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-14T09:27:24,729 If you don't want 'libhupf.src' to be distributed and are 2025-09-14T09:27:24,729 already explicitly excluding 'libhupf.src' via 2025-09-14T09:27:24,729 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-14T09:27:24,729 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-14T09:27:24,730 combination with a more fine grained `package-data` configuration. 2025-09-14T09:27:24,730 You can read more about "package data files" on setuptools documentation page: 2025-09-14T09:27:24,730 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-14T09:27:24,730 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-14T09:27:24,730 even if it does not contain any `.py` files. 2025-09-14T09:27:24,730 On the other hand, currently there is no concept of package data 2025-09-14T09:27:24,730 directory, all directories are treated like packages. 2025-09-14T09:27:24,731 ******************************************************************************** 2025-09-14T09:27:24,731 !! 2025-09-14T09:27:24,731 check.warn(importable) 2025-09-14T09:27:24,731 creating build/lib.linux-armv7l-cpython-313/libhupf/gcc 2025-09-14T09:27:24,731 copying libhupf/gcc/makefile -> build/lib.linux-armv7l-cpython-313/libhupf/gcc 2025-09-14T09:27:24,731 copying libhupf/gcc/makefile64 -> build/lib.linux-armv7l-cpython-313/libhupf/gcc 2025-09-14T09:27:24,731 creating build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf 2025-09-14T09:27:24,731 copying libhupf/inc/hupf/Calculate.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf 2025-09-14T09:27:24,731 copying libhupf/inc/hupf/Complex.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf 2025-09-14T09:27:24,731 copying libhupf/inc/hupf/ForwardKinematics.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf 2025-09-14T09:27:24,732 copying libhupf/inc/hupf/Hyperplane.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf 2025-09-14T09:27:24,732 copying libhupf/inc/hupf/Input.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf 2025-09-14T09:27:24,732 copying libhupf/inc/hupf/KinematicSurface.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf 2025-09-14T09:27:24,732 copying libhupf/inc/hupf/Matrix.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf 2025-09-14T09:27:24,732 copying libhupf/inc/hupf/Polynomial.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf 2025-09-14T09:27:24,732 copying libhupf/inc/hupf/SolveForAngles.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf 2025-09-14T09:27:24,732 copying libhupf/inc/hupf/ik.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf 2025-09-14T09:27:24,732 copying libhupf/inc/hupf/libdef.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf 2025-09-14T09:27:24,732 copying libhupf/inc/hupf/rpoly.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf 2025-09-14T09:27:24,732 creating build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf/rrp 2025-09-14T09:27:24,732 copying libhupf/inc/hupf/rrp/left_rrp.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf/rrp 2025-09-14T09:27:24,733 creating build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf/rrr 2025-09-14T09:27:24,733 copying libhupf/inc/hupf/rrr/left_3r.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf/rrr 2025-09-14T09:27:24,733 copying libhupf/inc/hupf/rrr/right_3r.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf/rrr 2025-09-14T09:27:24,733 copying libhupf/inc/hupf/rrr/t2.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf/rrr 2025-09-14T09:27:24,733 copying libhupf/inc/hupf/rrr/wrist_sol.h -> build/lib.linux-armv7l-cpython-313/libhupf/inc/hupf/rrr 2025-09-14T09:27:24,733 creating build/lib.linux-armv7l-cpython-313/libhupf/src 2025-09-14T09:27:24,733 copying libhupf/src/Calculate.cpp -> build/lib.linux-armv7l-cpython-313/libhupf/src 2025-09-14T09:27:24,733 copying libhupf/src/ik.cpp -> build/lib.linux-armv7l-cpython-313/libhupf/src 2025-09-14T09:27:24,733 running build_ext 2025-09-14T09:27:25,065 building 'libhupf.libhupf' extension 2025-09-14T09:27:25,066 creating build/temp.linux-armv7l-cpython-313/libhupf/src 2025-09-14T09:27:25,066 arm-linux-gnueabihf-g++ -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -fPIC -Ilibhupf/inc -Ilibhupf -I/usr/include/python3.13 -c libhupf/src/Calculate.cpp -o build/temp.linux-armv7l-cpython-313/libhupf/src/Calculate.o -DNDEBUG -DLIBHUPF_EXPORTS -O3 -g -s -Wall -Wextra -m32 -Wno-unknown-pragmas -Wno-deprecated-declarations -Wno-parentheses -Wno-unused-function -fopenmp -std=c++11 2025-09-14T09:27:25,078 arm-linux-gnueabihf-g++: error: unrecognized command-line option ‘-m32’; did you mean ‘-mbe32’? 2025-09-14T09:27:25,079 error: command '/usr/bin/arm-linux-gnueabihf-g++' failed with exit code 1 2025-09-14T09:27:25,232 ERROR: python setup.py bdist_wheel exited with 1 2025-09-14T09:27:25,244 [bold magenta]full command[/]: [blue]/usr/bin/python3 -u -c ' 2025-09-14T09:27:25,244 exec(compile('"'"''"'"''"'"' 2025-09-14T09:27:25,244 # This is -- a caller that pip uses to run setup.py 2025-09-14T09:27:25,244 # 2025-09-14T09:27:25,244 # - It imports setuptools before invoking setup.py, to enable projects that directly 2025-09-14T09:27:25,244 # import from `distutils.core` to work with newer packaging standards. 2025-09-14T09:27:25,244 # - It provides a clear error message when setuptools is not installed. 2025-09-14T09:27:25,244 # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so 2025-09-14T09:27:25,244 # setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning: 2025-09-14T09:27:25,244 # manifest_maker: standard file '"'"'-c'"'"' not found". 2025-09-14T09:27:25,244 # - It generates a shim setup.py, for handling setup.cfg-only projects. 2025-09-14T09:27:25,244 import os, sys, tokenize, traceback 2025-09-14T09:27:25,244 2025-09-14T09:27:25,244 try: 2025-09-14T09:27:25,244 import setuptools 2025-09-14T09:27:25,244 except ImportError: 2025-09-14T09:27:25,244 print( 2025-09-14T09:27:25,244 "ERROR: Can not execute `setup.py` since setuptools failed to import in " 2025-09-14T09:27:25,244 "the build environment with exception:", 2025-09-14T09:27:25,244 file=sys.stderr, 2025-09-14T09:27:25,244 ) 2025-09-14T09:27:25,244 traceback.print_exc() 2025-09-14T09:27:25,244 sys.exit(1) 2025-09-14T09:27:25,244 2025-09-14T09:27:25,244 __file__ = %r 2025-09-14T09:27:25,244 sys.argv[0] = __file__ 2025-09-14T09:27:25,244 2025-09-14T09:27:25,244 if os.path.exists(__file__): 2025-09-14T09:27:25,244 filename = __file__ 2025-09-14T09:27:25,244 with tokenize.open(__file__) as f: 2025-09-14T09:27:25,244 setup_py_code = f.read() 2025-09-14T09:27:25,244 else: 2025-09-14T09:27:25,244 filename = "" 2025-09-14T09:27:25,244 setup_py_code = "from setuptools import setup; setup()" 2025-09-14T09:27:25,244 2025-09-14T09:27:25,244 exec(compile(setup_py_code, filename, "exec")) 2025-09-14T09:27:25,244 '"'"''"'"''"'"' % ('"'"'/tmp/pip-wheel-vx03i0po/libhupf_3e48f9efe53c4cdea44f23395554b33d/setup.py'"'"',), "", "exec"))' bdist_wheel -d /tmp/pip-wheel-pu1dqmug[/] 2025-09-14T09:27:25,244 [bold magenta]cwd[/]: /tmp/pip-wheel-vx03i0po/libhupf_3e48f9efe53c4cdea44f23395554b33d/ 2025-09-14T09:27:25,245 Building wheel for libhupf (setup.py): finished with status 'error' 2025-09-14T09:27:25,245 ERROR: Failed building wheel for libhupf 2025-09-14T09:27:25,246 Running setup.py clean for libhupf 2025-09-14T09:27:25,247 Running command python setup.py clean 2025-09-14T09:27:26,395 running clean 2025-09-14T09:27:26,541 removing 'build/temp.linux-armv7l-cpython-313' (and everything under it) 2025-09-14T09:27:26,541 removing 'build/lib.linux-armv7l-cpython-313' (and everything under it) 2025-09-14T09:27:26,542 'build/bdist.linux-armv7l' does not exist -- can't clean it 2025-09-14T09:27:26,543 'build/scripts-3.13' does not exist -- can't clean it 2025-09-14T09:27:26,543 removing 'build' 2025-09-14T09:27:26,654 Failed to build libhupf 2025-09-14T09:27:26,655 ERROR: Failed to build one or more wheels 2025-09-14T09:27:26,656 Exception information: 2025-09-14T09:27:26,656 Traceback (most recent call last): 2025-09-14T09:27:26,656 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 105, in _run_wrapper 2025-09-14T09:27:26,656 status = _inner_run() 2025-09-14T09:27:26,656 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 96, in _inner_run 2025-09-14T09:27:26,656 return self.run(options, args) 2025-09-14T09:27:26,656 ~~~~~~~~^^^^^^^^^^^^^^^ 2025-09-14T09:27:26,656 File "/usr/lib/python3/dist-packages/pip/_internal/cli/req_command.py", line 68, in wrapper 2025-09-14T09:27:26,656 return func(self, options, args) 2025-09-14T09:27:26,656 File "/usr/lib/python3/dist-packages/pip/_internal/commands/wheel.py", line 180, in run 2025-09-14T09:27:26,656 raise CommandError("Failed to build one or more wheels") 2025-09-14T09:27:26,656 pip._internal.exceptions.CommandError: Failed to build one or more wheels 2025-09-14T09:27:26,660 Removed build tracker: '/tmp/pip-build-tracker-kgk8an7e'