2025-12-13T07:28:12,895 Created temporary directory: /tmp/pip-ephem-wheel-cache-tpnoj84y 2025-12-13T07:28:12,897 Created temporary directory: /tmp/pip-build-tracker-brohgzpp 2025-12-13T07:28:12,898 Initialized build tracking at /tmp/pip-build-tracker-brohgzpp 2025-12-13T07:28:12,898 Created build tracker: /tmp/pip-build-tracker-brohgzpp 2025-12-13T07:28:12,899 Entered build tracker: /tmp/pip-build-tracker-brohgzpp 2025-12-13T07:28:12,899 Created temporary directory: /tmp/pip-wheel-umrl098h 2025-12-13T07:28:12,902 DEPRECATION: --no-binary currently disables reading from the cache of locally built wheels. In the future --no-binary will not influence the wheel cache. pip 23.1 will enforce this behaviour change. A possible replacement is to use the --no-cache-dir option. You can use the flag --use-feature=no-binary-enable-wheel-cache to test the upcoming behaviour. Discussion can be found at https://github.com/pypa/pip/issues/11453 2025-12-13T07:28:12,905 Created temporary directory: /tmp/pip-ephem-wheel-cache-nq9mic0t 2025-12-13T07:28:12,929 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2025-12-13T07:28:12,932 2 location(s) to search for versions of seal5: 2025-12-13T07:28:12,932 * https://pypi.org/simple/seal5/ 2025-12-13T07:28:12,932 * https://www.piwheels.org/simple/seal5/ 2025-12-13T07:28:12,933 Fetching project page and analyzing links: https://pypi.org/simple/seal5/ 2025-12-13T07:28:12,934 Getting page https://pypi.org/simple/seal5/ 2025-12-13T07:28:12,935 Found index url https://pypi.org/simple 2025-12-13T07:28:13,152 Fetched page https://pypi.org/simple/seal5/ as application/vnd.pypi.simple.v1+json 2025-12-13T07:28:13,157 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/f8/ae/3ae56a5a2ac729d6f3311105d8d7b1cc9ab6e4a339af6eae6103596f0d86/seal5-0.1.0.dev0-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,157 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/d0/08/f1fb860506eda81695a5029eb9c62527dbe94993334e29ad3ab52f3cc4c9/seal5-0.1.1.dev0-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,158 Found link https://files.pythonhosted.org/packages/f6/32/5093f9d9bade6bd23974f28cd4273badc1775232963333387c2ec4f706a9/seal5-0.1.1.dev0.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.8), version: 0.1.1.dev0 2025-12-13T07:28:13,159 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/1d/63/f1f1bef31ff2df37739f70696e10024e0e78522e0afd7bd2e7471e03969f/seal5-0.1.2-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,160 Found link https://files.pythonhosted.org/packages/08/b5/9f567f298377348179dc738c13e1112ea3802fec8eee6f9340f02ab4230a/seal5-0.1.2.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.8), version: 0.1.2 2025-12-13T07:28:13,161 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/94/d4/a9b1351d4c3be9bf047399e73bdb194b895090c6bb6f0cca2c933b683da7/seal5-0.1.3-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,162 Found link https://files.pythonhosted.org/packages/e6/3c/9880ee9653d2ccda10caa8cb05c3675b079b9aab5c9857bb7ddda237add7/seal5-0.1.3.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.8), version: 0.1.3 2025-12-13T07:28:13,163 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/d3/cb/d5b4c65c3172714979b82ce1f97ece185b072cb00762e474bc2b0cf16e1e/seal5-0.1.4-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,164 Found link https://files.pythonhosted.org/packages/8e/b8/66f18763cd3fc041148d3f1a60d9b34170fac2bb7b554cf28116f40b220d/seal5-0.1.4.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.8), version: 0.1.4 2025-12-13T07:28:13,165 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/23/0f/9d8f3d6a198479d5bfeb21a83fbcf5d63d7ce61071fc3e802b486af45357/seal5-0.2.0-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,166 Found link https://files.pythonhosted.org/packages/ab/cf/629d9838515d4a414fac8d5f43c86c197d6f9e9aa9d3c93da98153aeca27/seal5-0.2.0.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.8), version: 0.2.0 2025-12-13T07:28:13,167 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/64/2b/e3deec1bcfe91ddf65882dd3a10d13e3b0acff1038116dfa08e2f4551080/seal5-0.3.0-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,168 Found link https://files.pythonhosted.org/packages/1c/67/ac7c5a312aae734e9be027768a6a9789cb36aee36e757afd4e599c52bb27/seal5-0.3.0.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.8), version: 0.3.0 2025-12-13T07:28:13,168 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/6b/4f/6e1aad0e6195a1cb2ec9645f32391a9d4186a5b0876b75b1aca45ad243c1/seal5-0.3.1-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,169 Found link https://files.pythonhosted.org/packages/f9/e3/6765c06785c0c68d1f765feaa080c84f9a0bbcb4fa34df08b2dc65249669/seal5-0.3.1.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.8), version: 0.3.1 2025-12-13T07:28:13,170 Skipping link: No binaries permitted for seal5: https://files.pythonhosted.org/packages/7b/6f/05d421bba39e103091b3add52f61e3f293ff3a286d927371edacfef45723/seal5-0.3.2-py3-none-any.whl (from https://pypi.org/simple/seal5/) (requires-python:>=3.10) 2025-12-13T07:28:13,170 Found link https://files.pythonhosted.org/packages/cb/51/0742f8a29f326e1233bf6a637811be514f1d31fba050e29b8a56f283d7c0/seal5-0.3.2.tar.gz (from https://pypi.org/simple/seal5/) (requires-python:>=3.10), version: 0.3.2 2025-12-13T07:28:13,171 Fetching project page and analyzing links: https://www.piwheels.org/simple/seal5/ 2025-12-13T07:28:13,172 Getting page https://www.piwheels.org/simple/seal5/ 2025-12-13T07:28:13,173 Found index url https://www.piwheels.org/simple 2025-12-13T07:28:13,326 Fetched page https://www.piwheels.org/simple/seal5/ as text/html 2025-12-13T07:28:13,330 Skipping link: No binaries permitted for seal5: https://archive1.piwheels.org/simple/seal5/seal5-0.3.1-py3-none-any.whl#sha256=8d1d70b0dd7880884070df245db646345a921681816d4de0facfbef840af9a20 (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,330 Skipping link: No binaries permitted for seal5: https://archive1.piwheels.org/simple/seal5/seal5-0.3.0-py3-none-any.whl#sha256=3ee5e04472ec4b991048da9c54e9ad3b634797fa191d9d4040d99f388e9ea091 (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,331 Skipping link: No binaries permitted for seal5: https://archive1.piwheels.org/simple/seal5/seal5-0.2.0-py3-none-any.whl#sha256=4215666ed62a5b68c7e63923b814182da049bd044230489bf7c7d76fd1f28285 (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,332 Skipping link: No binaries permitted for seal5: https://archive1.piwheels.org/simple/seal5/seal5-0.1.4-py3-none-any.whl#sha256=124235386909d38ba252e9bed0b9837b75d2f5f18d977852be818589651e6e6d (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,332 Skipping link: No binaries permitted for seal5: https://archive1.piwheels.org/simple/seal5/seal5-0.1.3-py3-none-any.whl#sha256=3a961dcced5a05f2b43aa4ffdd0912879a06892966dfb1a999bd556a84686967 (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,333 Skipping link: No binaries permitted for seal5: https://archive1.piwheels.org/simple/seal5/seal5-0.1.2-py3-none-any.whl#sha256=a4b69393213ff899308d4cd82005a43f055a577f95eba42e7cb39636ddc1144a (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,333 Skipping link: No binaries permitted for seal5: https://archive1.piwheels.org/simple/seal5/seal5-0.1.1.dev0-py3-none-any.whl#sha256=9921841f51a0dfe349f86cc3ee44d6a61648a9abfb16053ec71fb468a1475f28 (from https://www.piwheels.org/simple/seal5/) (requires-python:>=3.8) 2025-12-13T07:28:13,334 Skipping link: not a file: https://www.piwheels.org/simple/seal5/ 2025-12-13T07:28:13,335 Skipping link: not a file: https://pypi.org/simple/seal5/ 2025-12-13T07:28:13,355 Given no hashes to check 1 links for project 'seal5': discarding no candidates 2025-12-13T07:28:13,372 Collecting seal5==0.3.2 2025-12-13T07:28:13,375 Created temporary directory: /tmp/pip-unpack-17704at2 2025-12-13T07:28:13,510 Downloading seal5-0.3.2.tar.gz (351 kB) 2025-12-13T07:28:14,630 Added seal5==0.3.2 from https://files.pythonhosted.org/packages/cb/51/0742f8a29f326e1233bf6a637811be514f1d31fba050e29b8a56f283d7c0/seal5-0.3.2.tar.gz to build tracker '/tmp/pip-build-tracker-brohgzpp' 2025-12-13T07:28:14,636 Created temporary directory: /tmp/pip-build-env-kj9wjzmq 2025-12-13T07:28:14,640 Installing build dependencies: started 2025-12-13T07:28:14,642 Running command pip subprocess to install build dependencies 2025-12-13T07:28:15,814 Using pip 23.0.1 from /usr/lib/python3/dist-packages/pip (python 3.11) 2025-12-13T07:28:16,490 DEPRECATION: --no-binary currently disables reading from the cache of locally built wheels. In the future --no-binary will not influence the wheel cache. pip 23.1 will enforce this behaviour change. A possible replacement is to use the --no-cache-dir option. You can use the flag --use-feature=no-binary-enable-wheel-cache to test the upcoming behaviour. Discussion can be found at https://github.com/pypa/pip/issues/11453 2025-12-13T07:28:16,514 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2025-12-13T07:28:18,221 Collecting setuptools>=64 2025-12-13T07:28:18,326 Using cached https://www.piwheels.org/simple/setuptools/setuptools-80.9.0-py3-none-any.whl (1.2 MB) 2025-12-13T07:28:18,697 Collecting setuptools-scm>=8 2025-12-13T07:28:18,715 Using cached https://www.piwheels.org/simple/setuptools-scm/setuptools_scm-9.2.2-py3-none-any.whl (62 kB) 2025-12-13T07:28:18,898 Collecting packaging>=20 2025-12-13T07:28:18,914 Using cached https://www.piwheels.org/simple/packaging/packaging-25.0-py3-none-any.whl (66 kB) 2025-12-13T07:28:21,850 Installing collected packages: setuptools, packaging, setuptools-scm 2025-12-13T07:28:26,305 Creating /tmp/pip-build-env-kj9wjzmq/overlay/local/bin 2025-12-13T07:28:26,307 changing mode of /tmp/pip-build-env-kj9wjzmq/overlay/local/bin/setuptools-scm to 755 2025-12-13T07:28:26,331 Successfully installed packaging-25.0 setuptools-80.9.0 setuptools-scm-9.2.2 2025-12-13T07:28:26,615 Installing build dependencies: finished with status 'done' 2025-12-13T07:28:26,621 Getting requirements to build wheel: started 2025-12-13T07:28:26,623 Running command Getting requirements to build wheel 2025-12-13T07:28:27,298 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated 2025-12-13T07:28:27,298 !! 2025-12-13T07:28:27,300 ******************************************************************************** 2025-12-13T07:28:27,300 Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0). 2025-12-13T07:28:27,301 By 2026-Feb-18, you need to update your project and remove deprecated calls 2025-12-13T07:28:27,302 or your builds will no longer be supported. 2025-12-13T07:28:27,304 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-12-13T07:28:27,304 ******************************************************************************** 2025-12-13T07:28:27,306 !! 2025-12-13T07:28:27,307 corresp(dist, value, root_dir) 2025-12-13T07:28:27,402 running egg_info 2025-12-13T07:28:27,410 writing seal5.egg-info/PKG-INFO 2025-12-13T07:28:27,414 writing dependency_links to seal5.egg-info/dependency_links.txt 2025-12-13T07:28:27,417 writing entry points to seal5.egg-info/entry_points.txt 2025-12-13T07:28:27,419 writing requirements to seal5.egg-info/requires.txt 2025-12-13T07:28:27,420 writing top-level names to seal5.egg-info/top_level.txt 2025-12-13T07:28:27,470 listing git files failed - pretending there aren't any 2025-12-13T07:28:27,476 reading manifest file 'seal5.egg-info/SOURCES.txt' 2025-12-13T07:28:27,570 adding license file 'LICENSE' 2025-12-13T07:28:27,588 writing manifest file 'seal5.egg-info/SOURCES.txt' 2025-12-13T07:28:27,692 Getting requirements to build wheel: finished with status 'done' 2025-12-13T07:28:27,696 Created temporary directory: /tmp/pip-modern-metadata-ejstv3wr 2025-12-13T07:28:27,698 Preparing metadata (pyproject.toml): started 2025-12-13T07:28:27,699 Running command Preparing metadata (pyproject.toml) 2025-12-13T07:28:28,325 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated 2025-12-13T07:28:28,325 !! 2025-12-13T07:28:28,326 ******************************************************************************** 2025-12-13T07:28:28,327 Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0). 2025-12-13T07:28:28,328 By 2026-Feb-18, you need to update your project and remove deprecated calls 2025-12-13T07:28:28,328 or your builds will no longer be supported. 2025-12-13T07:28:28,329 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-12-13T07:28:28,330 ******************************************************************************** 2025-12-13T07:28:28,331 !! 2025-12-13T07:28:28,332 corresp(dist, value, root_dir) 2025-12-13T07:28:28,420 running dist_info 2025-12-13T07:28:28,435 creating /tmp/pip-modern-metadata-ejstv3wr/seal5.egg-info 2025-12-13T07:28:28,436 writing /tmp/pip-modern-metadata-ejstv3wr/seal5.egg-info/PKG-INFO 2025-12-13T07:28:28,441 writing dependency_links to /tmp/pip-modern-metadata-ejstv3wr/seal5.egg-info/dependency_links.txt 2025-12-13T07:28:28,443 writing entry points to /tmp/pip-modern-metadata-ejstv3wr/seal5.egg-info/entry_points.txt 2025-12-13T07:28:28,445 writing requirements to /tmp/pip-modern-metadata-ejstv3wr/seal5.egg-info/requires.txt 2025-12-13T07:28:28,446 writing top-level names to /tmp/pip-modern-metadata-ejstv3wr/seal5.egg-info/top_level.txt 2025-12-13T07:28:28,448 writing manifest file '/tmp/pip-modern-metadata-ejstv3wr/seal5.egg-info/SOURCES.txt' 2025-12-13T07:28:28,496 listing git files failed - pretending there aren't any 2025-12-13T07:28:28,500 reading manifest file '/tmp/pip-modern-metadata-ejstv3wr/seal5.egg-info/SOURCES.txt' 2025-12-13T07:28:28,502 adding license file 'LICENSE' 2025-12-13T07:28:28,506 writing manifest file '/tmp/pip-modern-metadata-ejstv3wr/seal5.egg-info/SOURCES.txt' 2025-12-13T07:28:28,507 creating '/tmp/pip-modern-metadata-ejstv3wr/seal5-0.3.2.dist-info' 2025-12-13T07:28:28,642 Preparing metadata (pyproject.toml): finished with status 'done' 2025-12-13T07:28:28,647 Source in /tmp/pip-wheel-umrl098h/seal5_b7c7211f175c48699193e7ac254ab2a4 has version 0.3.2, which satisfies requirement seal5==0.3.2 from https://files.pythonhosted.org/packages/cb/51/0742f8a29f326e1233bf6a637811be514f1d31fba050e29b8a56f283d7c0/seal5-0.3.2.tar.gz 2025-12-13T07:28:28,648 Removed seal5==0.3.2 from https://files.pythonhosted.org/packages/cb/51/0742f8a29f326e1233bf6a637811be514f1d31fba050e29b8a56f283d7c0/seal5-0.3.2.tar.gz from build tracker '/tmp/pip-build-tracker-brohgzpp' 2025-12-13T07:28:28,654 Created temporary directory: /tmp/pip-unpack-qi_mien6 2025-12-13T07:28:28,655 Building wheels for collected packages: seal5 2025-12-13T07:28:28,660 Created temporary directory: /tmp/pip-wheel-0e6ektnj 2025-12-13T07:28:28,661 Destination directory: /tmp/pip-wheel-0e6ektnj 2025-12-13T07:28:28,663 Building wheel for seal5 (pyproject.toml): started 2025-12-13T07:28:28,664 Running command Building wheel for seal5 (pyproject.toml) 2025-12-13T07:28:29,279 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated 2025-12-13T07:28:29,279 !! 2025-12-13T07:28:29,280 ******************************************************************************** 2025-12-13T07:28:29,281 Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0). 2025-12-13T07:28:29,282 By 2026-Feb-18, you need to update your project and remove deprecated calls 2025-12-13T07:28:29,282 or your builds will no longer be supported. 2025-12-13T07:28:29,283 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-12-13T07:28:29,284 ******************************************************************************** 2025-12-13T07:28:29,285 !! 2025-12-13T07:28:29,285 corresp(dist, value, root_dir) 2025-12-13T07:28:29,362 running bdist_wheel 2025-12-13T07:28:29,388 running build 2025-12-13T07:28:29,389 running build_py 2025-12-13T07:28:29,397 creating build/lib/seal5 2025-12-13T07:28:29,400 copying seal5/utils.py -> build/lib/seal5 2025-12-13T07:28:29,402 copying seal5/model.py -> build/lib/seal5 2025-12-13T07:28:29,405 copying seal5/model_utils.py -> build/lib/seal5 2025-12-13T07:28:29,407 copying seal5/dependencies.py -> build/lib/seal5 2025-12-13T07:28:29,410 copying seal5/flow.py -> build/lib/seal5 2025-12-13T07:28:29,413 copying seal5/logging.py -> build/lib/seal5 2025-12-13T07:28:29,416 copying seal5/testgen_utils.py -> build/lib/seal5 2025-12-13T07:28:29,418 copying seal5/__init__.py -> build/lib/seal5 2025-12-13T07:28:29,420 copying seal5/riscv_utils.py -> build/lib/seal5 2025-12-13T07:28:29,422 copying seal5/settings.py -> build/lib/seal5 2025-12-13T07:28:29,425 copying seal5/pass_list.py -> build/lib/seal5 2025-12-13T07:28:29,430 copying seal5/index.py -> build/lib/seal5 2025-12-13T07:28:29,432 copying seal5/wrapper.py -> build/lib/seal5 2025-12-13T07:28:29,435 copying seal5/types.py -> build/lib/seal5 2025-12-13T07:28:29,437 copying seal5/version.py -> build/lib/seal5 2025-12-13T07:28:29,439 copying seal5/passes.py -> build/lib/seal5 2025-12-13T07:28:29,441 copying seal5/metrics.py -> build/lib/seal5 2025-12-13T07:28:29,443 copying seal5/build_cache.py -> build/lib/seal5 2025-12-13T07:28:29,445 running egg_info 2025-12-13T07:28:29,460 writing seal5.egg-info/PKG-INFO 2025-12-13T07:28:29,464 writing dependency_links to seal5.egg-info/dependency_links.txt 2025-12-13T07:28:29,466 writing entry points to seal5.egg-info/entry_points.txt 2025-12-13T07:28:29,467 writing requirements to seal5.egg-info/requires.txt 2025-12-13T07:28:29,468 writing top-level names to seal5.egg-info/top_level.txt 2025-12-13T07:28:29,502 listing git files failed - pretending there aren't any 2025-12-13T07:28:29,506 reading manifest file 'seal5.egg-info/SOURCES.txt' 2025-12-13T07:28:29,535 adding license file 'LICENSE' 2025-12-13T07:28:29,552 writing manifest file 'seal5.egg-info/SOURCES.txt' 2025-12-13T07:28:29,566 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends' is absent from the `packages` configuration. 2025-12-13T07:28:29,567 !! 2025-12-13T07:28:29,568 ******************************************************************************** 2025-12-13T07:28:29,569 ############################ 2025-12-13T07:28:29,569 # Package would be ignored # 2025-12-13T07:28:29,570 ############################ 2025-12-13T07:28:29,571 Python recognizes 'seal5.backends' as an importable package[^1], 2025-12-13T07:28:29,572 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,573 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,573 package, please make sure that 'seal5.backends' is explicitly added 2025-12-13T07:28:29,574 to the `packages` configuration field. 2025-12-13T07:28:29,574 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,575 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,575 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,576 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,577 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,578 If you don't want 'seal5.backends' to be distributed and are 2025-12-13T07:28:29,579 already explicitly excluding 'seal5.backends' via 2025-12-13T07:28:29,579 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,579 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,580 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,581 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,582 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,583 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,583 even if it does not contain any `.py` files. 2025-12-13T07:28:29,584 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,584 directory, all directories are treated like packages. 2025-12-13T07:28:29,585 ******************************************************************************** 2025-12-13T07:28:29,586 !! 2025-12-13T07:28:29,586 check.warn(importable) 2025-12-13T07:28:29,587 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.coredsl2' is absent from the `packages` configuration. 2025-12-13T07:28:29,588 !! 2025-12-13T07:28:29,589 ******************************************************************************** 2025-12-13T07:28:29,590 ############################ 2025-12-13T07:28:29,590 # Package would be ignored # 2025-12-13T07:28:29,591 ############################ 2025-12-13T07:28:29,591 Python recognizes 'seal5.backends.coredsl2' as an importable package[^1], 2025-12-13T07:28:29,592 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,593 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,593 package, please make sure that 'seal5.backends.coredsl2' is explicitly added 2025-12-13T07:28:29,594 to the `packages` configuration field. 2025-12-13T07:28:29,595 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,595 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,596 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,597 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,598 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,599 If you don't want 'seal5.backends.coredsl2' to be distributed and are 2025-12-13T07:28:29,600 already explicitly excluding 'seal5.backends.coredsl2' via 2025-12-13T07:28:29,600 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,601 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,601 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,602 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,603 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,604 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,604 even if it does not contain any `.py` files. 2025-12-13T07:28:29,605 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,605 directory, all directories are treated like packages. 2025-12-13T07:28:29,606 ******************************************************************************** 2025-12-13T07:28:29,606 !! 2025-12-13T07:28:29,607 check.warn(importable) 2025-12-13T07:28:29,607 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.llvmir' is absent from the `packages` configuration. 2025-12-13T07:28:29,607 !! 2025-12-13T07:28:29,608 ******************************************************************************** 2025-12-13T07:28:29,609 ############################ 2025-12-13T07:28:29,609 # Package would be ignored # 2025-12-13T07:28:29,609 ############################ 2025-12-13T07:28:29,610 Python recognizes 'seal5.backends.llvmir' as an importable package[^1], 2025-12-13T07:28:29,610 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,611 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,612 package, please make sure that 'seal5.backends.llvmir' is explicitly added 2025-12-13T07:28:29,613 to the `packages` configuration field. 2025-12-13T07:28:29,613 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,614 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,614 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,615 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,616 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,617 If you don't want 'seal5.backends.llvmir' to be distributed and are 2025-12-13T07:28:29,618 already explicitly excluding 'seal5.backends.llvmir' via 2025-12-13T07:28:29,618 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,619 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,619 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,620 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,621 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,622 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,623 even if it does not contain any `.py` files. 2025-12-13T07:28:29,623 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,624 directory, all directories are treated like packages. 2025-12-13T07:28:29,624 ******************************************************************************** 2025-12-13T07:28:29,625 !! 2025-12-13T07:28:29,626 check.warn(importable) 2025-12-13T07:28:29,626 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.patterngen' is absent from the `packages` configuration. 2025-12-13T07:28:29,627 !! 2025-12-13T07:28:29,628 ******************************************************************************** 2025-12-13T07:28:29,628 ############################ 2025-12-13T07:28:29,629 # Package would be ignored # 2025-12-13T07:28:29,629 ############################ 2025-12-13T07:28:29,629 Python recognizes 'seal5.backends.patterngen' as an importable package[^1], 2025-12-13T07:28:29,630 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,631 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,631 package, please make sure that 'seal5.backends.patterngen' is explicitly added 2025-12-13T07:28:29,631 to the `packages` configuration field. 2025-12-13T07:28:29,632 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,632 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,633 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,634 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,634 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,635 If you don't want 'seal5.backends.patterngen' to be distributed and are 2025-12-13T07:28:29,636 already explicitly excluding 'seal5.backends.patterngen' via 2025-12-13T07:28:29,636 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,636 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,637 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,638 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,639 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,641 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,641 even if it does not contain any `.py` files. 2025-12-13T07:28:29,642 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,643 directory, all directories are treated like packages. 2025-12-13T07:28:29,643 ******************************************************************************** 2025-12-13T07:28:29,644 !! 2025-12-13T07:28:29,645 check.warn(importable) 2025-12-13T07:28:29,645 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.report' is absent from the `packages` configuration. 2025-12-13T07:28:29,646 !! 2025-12-13T07:28:29,647 ******************************************************************************** 2025-12-13T07:28:29,647 ############################ 2025-12-13T07:28:29,648 # Package would be ignored # 2025-12-13T07:28:29,648 ############################ 2025-12-13T07:28:29,649 Python recognizes 'seal5.backends.report' as an importable package[^1], 2025-12-13T07:28:29,649 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,650 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,651 package, please make sure that 'seal5.backends.report' is explicitly added 2025-12-13T07:28:29,651 to the `packages` configuration field. 2025-12-13T07:28:29,652 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,653 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,653 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,655 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,655 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,656 If you don't want 'seal5.backends.report' to be distributed and are 2025-12-13T07:28:29,656 already explicitly excluding 'seal5.backends.report' via 2025-12-13T07:28:29,657 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,657 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,658 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,658 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,659 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,660 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,660 even if it does not contain any `.py` files. 2025-12-13T07:28:29,661 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,664 directory, all directories are treated like packages. 2025-12-13T07:28:29,665 ******************************************************************************** 2025-12-13T07:28:29,666 !! 2025-12-13T07:28:29,666 check.warn(importable) 2025-12-13T07:28:29,666 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.report.diff' is absent from the `packages` configuration. 2025-12-13T07:28:29,667 !! 2025-12-13T07:28:29,668 ******************************************************************************** 2025-12-13T07:28:29,668 ############################ 2025-12-13T07:28:29,669 # Package would be ignored # 2025-12-13T07:28:29,669 ############################ 2025-12-13T07:28:29,670 Python recognizes 'seal5.backends.report.diff' as an importable package[^1], 2025-12-13T07:28:29,670 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,671 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,672 package, please make sure that 'seal5.backends.report.diff' is explicitly added 2025-12-13T07:28:29,673 to the `packages` configuration field. 2025-12-13T07:28:29,673 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,674 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,675 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,676 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,676 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,677 If you don't want 'seal5.backends.report.diff' to be distributed and are 2025-12-13T07:28:29,678 already explicitly excluding 'seal5.backends.report.diff' via 2025-12-13T07:28:29,678 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,679 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,679 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,680 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,681 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,683 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,684 even if it does not contain any `.py` files. 2025-12-13T07:28:29,684 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,685 directory, all directories are treated like packages. 2025-12-13T07:28:29,685 ******************************************************************************** 2025-12-13T07:28:29,686 !! 2025-12-13T07:28:29,686 check.warn(importable) 2025-12-13T07:28:29,687 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.report.pattern_gen' is absent from the `packages` configuration. 2025-12-13T07:28:29,687 !! 2025-12-13T07:28:29,688 ******************************************************************************** 2025-12-13T07:28:29,688 ############################ 2025-12-13T07:28:29,689 # Package would be ignored # 2025-12-13T07:28:29,689 ############################ 2025-12-13T07:28:29,690 Python recognizes 'seal5.backends.report.pattern_gen' as an importable package[^1], 2025-12-13T07:28:29,690 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,691 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,691 package, please make sure that 'seal5.backends.report.pattern_gen' is explicitly added 2025-12-13T07:28:29,692 to the `packages` configuration field. 2025-12-13T07:28:29,692 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,693 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,693 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,694 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,695 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,696 If you don't want 'seal5.backends.report.pattern_gen' to be distributed and are 2025-12-13T07:28:29,697 already explicitly excluding 'seal5.backends.report.pattern_gen' via 2025-12-13T07:28:29,697 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,698 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,699 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,700 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,701 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,702 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,703 even if it does not contain any `.py` files. 2025-12-13T07:28:29,704 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,704 directory, all directories are treated like packages. 2025-12-13T07:28:29,705 ******************************************************************************** 2025-12-13T07:28:29,705 !! 2025-12-13T07:28:29,706 check.warn(importable) 2025-12-13T07:28:29,706 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.report.properties' is absent from the `packages` configuration. 2025-12-13T07:28:29,707 !! 2025-12-13T07:28:29,708 ******************************************************************************** 2025-12-13T07:28:29,708 ############################ 2025-12-13T07:28:29,709 # Package would be ignored # 2025-12-13T07:28:29,710 ############################ 2025-12-13T07:28:29,710 Python recognizes 'seal5.backends.report.properties' as an importable package[^1], 2025-12-13T07:28:29,711 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,712 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,712 package, please make sure that 'seal5.backends.report.properties' is explicitly added 2025-12-13T07:28:29,713 to the `packages` configuration field. 2025-12-13T07:28:29,714 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,714 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,714 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,715 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,716 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,716 If you don't want 'seal5.backends.report.properties' to be distributed and are 2025-12-13T07:28:29,717 already explicitly excluding 'seal5.backends.report.properties' via 2025-12-13T07:28:29,717 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,717 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,718 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,719 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,719 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,721 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,721 even if it does not contain any `.py` files. 2025-12-13T07:28:29,721 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,722 directory, all directories are treated like packages. 2025-12-13T07:28:29,722 ******************************************************************************** 2025-12-13T07:28:29,724 !! 2025-12-13T07:28:29,724 check.warn(importable) 2025-12-13T07:28:29,725 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.report.status' is absent from the `packages` configuration. 2025-12-13T07:28:29,726 !! 2025-12-13T07:28:29,727 ******************************************************************************** 2025-12-13T07:28:29,727 ############################ 2025-12-13T07:28:29,728 # Package would be ignored # 2025-12-13T07:28:29,728 ############################ 2025-12-13T07:28:29,729 Python recognizes 'seal5.backends.report.status' as an importable package[^1], 2025-12-13T07:28:29,730 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,731 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,731 package, please make sure that 'seal5.backends.report.status' is explicitly added 2025-12-13T07:28:29,732 to the `packages` configuration field. 2025-12-13T07:28:29,733 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,733 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,734 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,734 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,735 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,736 If you don't want 'seal5.backends.report.status' to be distributed and are 2025-12-13T07:28:29,737 already explicitly excluding 'seal5.backends.report.status' via 2025-12-13T07:28:29,738 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,738 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,739 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,740 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,741 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,743 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,743 even if it does not contain any `.py` files. 2025-12-13T07:28:29,743 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,744 directory, all directories are treated like packages. 2025-12-13T07:28:29,744 ******************************************************************************** 2025-12-13T07:28:29,745 !! 2025-12-13T07:28:29,745 check.warn(importable) 2025-12-13T07:28:29,746 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.report.test_results' is absent from the `packages` configuration. 2025-12-13T07:28:29,746 !! 2025-12-13T07:28:29,747 ******************************************************************************** 2025-12-13T07:28:29,747 ############################ 2025-12-13T07:28:29,748 # Package would be ignored # 2025-12-13T07:28:29,748 ############################ 2025-12-13T07:28:29,749 Python recognizes 'seal5.backends.report.test_results' as an importable package[^1], 2025-12-13T07:28:29,749 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,750 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,750 package, please make sure that 'seal5.backends.report.test_results' is explicitly added 2025-12-13T07:28:29,751 to the `packages` configuration field. 2025-12-13T07:28:29,752 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,753 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,753 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,754 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,756 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,757 If you don't want 'seal5.backends.report.test_results' to be distributed and are 2025-12-13T07:28:29,757 already explicitly excluding 'seal5.backends.report.test_results' via 2025-12-13T07:28:29,758 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,759 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,759 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,760 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,761 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,762 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,763 even if it does not contain any `.py` files. 2025-12-13T07:28:29,764 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,764 directory, all directories are treated like packages. 2025-12-13T07:28:29,765 ******************************************************************************** 2025-12-13T07:28:29,766 !! 2025-12-13T07:28:29,766 check.warn(importable) 2025-12-13T07:28:29,767 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.report.times' is absent from the `packages` configuration. 2025-12-13T07:28:29,767 !! 2025-12-13T07:28:29,769 ******************************************************************************** 2025-12-13T07:28:29,769 ############################ 2025-12-13T07:28:29,769 # Package would be ignored # 2025-12-13T07:28:29,770 ############################ 2025-12-13T07:28:29,770 Python recognizes 'seal5.backends.report.times' as an importable package[^1], 2025-12-13T07:28:29,770 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,771 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,772 package, please make sure that 'seal5.backends.report.times' is explicitly added 2025-12-13T07:28:29,772 to the `packages` configuration field. 2025-12-13T07:28:29,773 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,773 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,774 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,774 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,775 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,776 If you don't want 'seal5.backends.report.times' to be distributed and are 2025-12-13T07:28:29,776 already explicitly excluding 'seal5.backends.report.times' via 2025-12-13T07:28:29,777 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,777 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,778 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,779 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,780 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,782 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,782 even if it does not contain any `.py` files. 2025-12-13T07:28:29,783 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,783 directory, all directories are treated like packages. 2025-12-13T07:28:29,784 ******************************************************************************** 2025-12-13T07:28:29,785 !! 2025-12-13T07:28:29,785 check.warn(importable) 2025-12-13T07:28:29,786 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_features' is absent from the `packages` configuration. 2025-12-13T07:28:29,787 !! 2025-12-13T07:28:29,788 ******************************************************************************** 2025-12-13T07:28:29,788 ############################ 2025-12-13T07:28:29,789 # Package would be ignored # 2025-12-13T07:28:29,789 ############################ 2025-12-13T07:28:29,790 Python recognizes 'seal5.backends.riscv_features' as an importable package[^1], 2025-12-13T07:28:29,790 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,791 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,792 package, please make sure that 'seal5.backends.riscv_features' is explicitly added 2025-12-13T07:28:29,792 to the `packages` configuration field. 2025-12-13T07:28:29,793 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,794 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,794 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,795 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,797 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,798 If you don't want 'seal5.backends.riscv_features' to be distributed and are 2025-12-13T07:28:29,798 already explicitly excluding 'seal5.backends.riscv_features' via 2025-12-13T07:28:29,798 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,799 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,799 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,800 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,801 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,802 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,802 even if it does not contain any `.py` files. 2025-12-13T07:28:29,803 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,803 directory, all directories are treated like packages. 2025-12-13T07:28:29,803 ******************************************************************************** 2025-12-13T07:28:29,804 !! 2025-12-13T07:28:29,805 check.warn(importable) 2025-12-13T07:28:29,805 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_features.templates' is absent from the `packages` configuration. 2025-12-13T07:28:29,805 !! 2025-12-13T07:28:29,806 ******************************************************************************** 2025-12-13T07:28:29,807 ############################ 2025-12-13T07:28:29,807 # Package would be ignored # 2025-12-13T07:28:29,807 ############################ 2025-12-13T07:28:29,808 Python recognizes 'seal5.backends.riscv_features.templates' as an importable package[^1], 2025-12-13T07:28:29,809 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,810 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,810 package, please make sure that 'seal5.backends.riscv_features.templates' is explicitly added 2025-12-13T07:28:29,811 to the `packages` configuration field. 2025-12-13T07:28:29,812 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,812 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,813 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,814 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,815 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,816 If you don't want 'seal5.backends.riscv_features.templates' to be distributed and are 2025-12-13T07:28:29,817 already explicitly excluding 'seal5.backends.riscv_features.templates' via 2025-12-13T07:28:29,817 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,818 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,818 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,819 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,821 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,822 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,823 even if it does not contain any `.py` files. 2025-12-13T07:28:29,823 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,824 directory, all directories are treated like packages. 2025-12-13T07:28:29,825 ******************************************************************************** 2025-12-13T07:28:29,826 !! 2025-12-13T07:28:29,826 check.warn(importable) 2025-12-13T07:28:29,826 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_field_types' is absent from the `packages` configuration. 2025-12-13T07:28:29,827 !! 2025-12-13T07:28:29,827 ******************************************************************************** 2025-12-13T07:28:29,828 ############################ 2025-12-13T07:28:29,828 # Package would be ignored # 2025-12-13T07:28:29,828 ############################ 2025-12-13T07:28:29,829 Python recognizes 'seal5.backends.riscv_field_types' as an importable package[^1], 2025-12-13T07:28:29,829 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,830 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,830 package, please make sure that 'seal5.backends.riscv_field_types' is explicitly added 2025-12-13T07:28:29,831 to the `packages` configuration field. 2025-12-13T07:28:29,831 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,832 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,832 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,833 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,834 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,835 If you don't want 'seal5.backends.riscv_field_types' to be distributed and are 2025-12-13T07:28:29,836 already explicitly excluding 'seal5.backends.riscv_field_types' via 2025-12-13T07:28:29,836 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,837 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,838 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,839 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,840 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,841 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,842 even if it does not contain any `.py` files. 2025-12-13T07:28:29,842 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,843 directory, all directories are treated like packages. 2025-12-13T07:28:29,843 ******************************************************************************** 2025-12-13T07:28:29,844 !! 2025-12-13T07:28:29,845 check.warn(importable) 2025-12-13T07:28:29,845 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_gisel_legalizer' is absent from the `packages` configuration. 2025-12-13T07:28:29,846 !! 2025-12-13T07:28:29,847 ******************************************************************************** 2025-12-13T07:28:29,847 ############################ 2025-12-13T07:28:29,848 # Package would be ignored # 2025-12-13T07:28:29,848 ############################ 2025-12-13T07:28:29,849 Python recognizes 'seal5.backends.riscv_gisel_legalizer' as an importable package[^1], 2025-12-13T07:28:29,850 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,851 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,851 package, please make sure that 'seal5.backends.riscv_gisel_legalizer' is explicitly added 2025-12-13T07:28:29,852 to the `packages` configuration field. 2025-12-13T07:28:29,853 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,853 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,853 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,854 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,855 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,855 If you don't want 'seal5.backends.riscv_gisel_legalizer' to be distributed and are 2025-12-13T07:28:29,856 already explicitly excluding 'seal5.backends.riscv_gisel_legalizer' via 2025-12-13T07:28:29,856 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,857 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,857 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,858 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,859 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,860 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,860 even if it does not contain any `.py` files. 2025-12-13T07:28:29,861 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,861 directory, all directories are treated like packages. 2025-12-13T07:28:29,862 ******************************************************************************** 2025-12-13T07:28:29,863 !! 2025-12-13T07:28:29,863 check.warn(importable) 2025-12-13T07:28:29,864 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_instr_info' is absent from the `packages` configuration. 2025-12-13T07:28:29,864 !! 2025-12-13T07:28:29,865 ******************************************************************************** 2025-12-13T07:28:29,866 ############################ 2025-12-13T07:28:29,866 # Package would be ignored # 2025-12-13T07:28:29,867 ############################ 2025-12-13T07:28:29,868 Python recognizes 'seal5.backends.riscv_instr_info' as an importable package[^1], 2025-12-13T07:28:29,868 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,869 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,870 package, please make sure that 'seal5.backends.riscv_instr_info' is explicitly added 2025-12-13T07:28:29,870 to the `packages` configuration field. 2025-12-13T07:28:29,871 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,872 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,872 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,873 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,874 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,875 If you don't want 'seal5.backends.riscv_instr_info' to be distributed and are 2025-12-13T07:28:29,876 already explicitly excluding 'seal5.backends.riscv_instr_info' via 2025-12-13T07:28:29,877 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,877 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,878 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,879 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,880 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,881 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,881 even if it does not contain any `.py` files. 2025-12-13T07:28:29,882 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,882 directory, all directories are treated like packages. 2025-12-13T07:28:29,882 ******************************************************************************** 2025-12-13T07:28:29,883 !! 2025-12-13T07:28:29,883 check.warn(importable) 2025-12-13T07:28:29,884 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_instr_info.templates' is absent from the `packages` configuration. 2025-12-13T07:28:29,884 !! 2025-12-13T07:28:29,885 ******************************************************************************** 2025-12-13T07:28:29,885 ############################ 2025-12-13T07:28:29,886 # Package would be ignored # 2025-12-13T07:28:29,886 ############################ 2025-12-13T07:28:29,887 Python recognizes 'seal5.backends.riscv_instr_info.templates' as an importable package[^1], 2025-12-13T07:28:29,887 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,888 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,888 package, please make sure that 'seal5.backends.riscv_instr_info.templates' is explicitly added 2025-12-13T07:28:29,889 to the `packages` configuration field. 2025-12-13T07:28:29,890 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,891 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,892 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,893 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,894 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,895 If you don't want 'seal5.backends.riscv_instr_info.templates' to be distributed and are 2025-12-13T07:28:29,895 already explicitly excluding 'seal5.backends.riscv_instr_info.templates' via 2025-12-13T07:28:29,896 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,897 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,897 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,898 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,899 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,901 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,901 even if it does not contain any `.py` files. 2025-12-13T07:28:29,902 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,902 directory, all directories are treated like packages. 2025-12-13T07:28:29,903 ******************************************************************************** 2025-12-13T07:28:29,904 !! 2025-12-13T07:28:29,904 check.warn(importable) 2025-12-13T07:28:29,905 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_intrinsics' is absent from the `packages` configuration. 2025-12-13T07:28:29,906 !! 2025-12-13T07:28:29,907 ******************************************************************************** 2025-12-13T07:28:29,907 ############################ 2025-12-13T07:28:29,908 # Package would be ignored # 2025-12-13T07:28:29,908 ############################ 2025-12-13T07:28:29,908 Python recognizes 'seal5.backends.riscv_intrinsics' as an importable package[^1], 2025-12-13T07:28:29,909 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,909 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,910 package, please make sure that 'seal5.backends.riscv_intrinsics' is explicitly added 2025-12-13T07:28:29,910 to the `packages` configuration field. 2025-12-13T07:28:29,911 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,911 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,912 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,912 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,913 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,914 If you don't want 'seal5.backends.riscv_intrinsics' to be distributed and are 2025-12-13T07:28:29,914 already explicitly excluding 'seal5.backends.riscv_intrinsics' via 2025-12-13T07:28:29,915 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,915 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,916 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,917 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,918 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,919 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,920 even if it does not contain any `.py` files. 2025-12-13T07:28:29,920 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,921 directory, all directories are treated like packages. 2025-12-13T07:28:29,922 ******************************************************************************** 2025-12-13T07:28:29,923 !! 2025-12-13T07:28:29,923 check.warn(importable) 2025-12-13T07:28:29,924 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_isa_info' is absent from the `packages` configuration. 2025-12-13T07:28:29,925 !! 2025-12-13T07:28:29,925 ******************************************************************************** 2025-12-13T07:28:29,926 ############################ 2025-12-13T07:28:29,926 # Package would be ignored # 2025-12-13T07:28:29,927 ############################ 2025-12-13T07:28:29,927 Python recognizes 'seal5.backends.riscv_isa_info' as an importable package[^1], 2025-12-13T07:28:29,928 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,929 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,929 package, please make sure that 'seal5.backends.riscv_isa_info' is explicitly added 2025-12-13T07:28:29,930 to the `packages` configuration field. 2025-12-13T07:28:29,931 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,932 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,932 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,934 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,935 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,935 If you don't want 'seal5.backends.riscv_isa_info' to be distributed and are 2025-12-13T07:28:29,936 already explicitly excluding 'seal5.backends.riscv_isa_info' via 2025-12-13T07:28:29,936 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,936 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,937 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,937 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,938 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,939 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,940 even if it does not contain any `.py` files. 2025-12-13T07:28:29,940 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,940 directory, all directories are treated like packages. 2025-12-13T07:28:29,941 ******************************************************************************** 2025-12-13T07:28:29,942 !! 2025-12-13T07:28:29,942 check.warn(importable) 2025-12-13T07:28:29,943 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.riscv_register_info' is absent from the `packages` configuration. 2025-12-13T07:28:29,943 !! 2025-12-13T07:28:29,944 ******************************************************************************** 2025-12-13T07:28:29,944 ############################ 2025-12-13T07:28:29,945 # Package would be ignored # 2025-12-13T07:28:29,945 ############################ 2025-12-13T07:28:29,946 Python recognizes 'seal5.backends.riscv_register_info' as an importable package[^1], 2025-12-13T07:28:29,947 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,948 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,948 package, please make sure that 'seal5.backends.riscv_register_info' is explicitly added 2025-12-13T07:28:29,949 to the `packages` configuration field. 2025-12-13T07:28:29,950 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,951 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,951 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,952 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,953 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,954 If you don't want 'seal5.backends.riscv_register_info' to be distributed and are 2025-12-13T07:28:29,955 already explicitly excluding 'seal5.backends.riscv_register_info' via 2025-12-13T07:28:29,955 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,956 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,956 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,957 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,958 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,960 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,960 even if it does not contain any `.py` files. 2025-12-13T07:28:29,961 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,962 directory, all directories are treated like packages. 2025-12-13T07:28:29,962 ******************************************************************************** 2025-12-13T07:28:29,963 !! 2025-12-13T07:28:29,963 check.warn(importable) 2025-12-13T07:28:29,964 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.viewer_seal5' is absent from the `packages` configuration. 2025-12-13T07:28:29,964 !! 2025-12-13T07:28:29,965 ******************************************************************************** 2025-12-13T07:28:29,965 ############################ 2025-12-13T07:28:29,966 # Package would be ignored # 2025-12-13T07:28:29,966 ############################ 2025-12-13T07:28:29,967 Python recognizes 'seal5.backends.viewer_seal5' as an importable package[^1], 2025-12-13T07:28:29,967 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,968 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,969 package, please make sure that 'seal5.backends.viewer_seal5' is explicitly added 2025-12-13T07:28:29,969 to the `packages` configuration field. 2025-12-13T07:28:29,970 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,970 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,971 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,972 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,973 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,974 If you don't want 'seal5.backends.viewer_seal5' to be distributed and are 2025-12-13T07:28:29,974 already explicitly excluding 'seal5.backends.viewer_seal5' via 2025-12-13T07:28:29,975 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,975 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,976 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,977 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,978 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,980 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,980 even if it does not contain any `.py` files. 2025-12-13T07:28:29,981 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,981 directory, all directories are treated like packages. 2025-12-13T07:28:29,982 ******************************************************************************** 2025-12-13T07:28:29,983 !! 2025-12-13T07:28:29,983 check.warn(importable) 2025-12-13T07:28:29,984 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.backends.yaml' is absent from the `packages` configuration. 2025-12-13T07:28:29,984 !! 2025-12-13T07:28:29,985 ******************************************************************************** 2025-12-13T07:28:29,985 ############################ 2025-12-13T07:28:29,986 # Package would be ignored # 2025-12-13T07:28:29,986 ############################ 2025-12-13T07:28:29,987 Python recognizes 'seal5.backends.yaml' as an importable package[^1], 2025-12-13T07:28:29,988 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:29,989 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:29,989 package, please make sure that 'seal5.backends.yaml' is explicitly added 2025-12-13T07:28:29,990 to the `packages` configuration field. 2025-12-13T07:28:29,990 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:29,991 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:29,991 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:29,992 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:29,993 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:29,993 If you don't want 'seal5.backends.yaml' to be distributed and are 2025-12-13T07:28:29,994 already explicitly excluding 'seal5.backends.yaml' via 2025-12-13T07:28:29,994 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:29,994 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:29,995 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:29,996 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:29,996 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:29,997 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:29,998 even if it does not contain any `.py` files. 2025-12-13T07:28:29,998 On the other hand, currently there is no concept of package data 2025-12-13T07:28:29,999 directory, all directories are treated like packages. 2025-12-13T07:28:29,999 ******************************************************************************** 2025-12-13T07:28:30,000 !! 2025-12-13T07:28:30,001 check.warn(importable) 2025-12-13T07:28:30,002 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.cli' is absent from the `packages` configuration. 2025-12-13T07:28:30,002 !! 2025-12-13T07:28:30,003 ******************************************************************************** 2025-12-13T07:28:30,004 ############################ 2025-12-13T07:28:30,005 # Package would be ignored # 2025-12-13T07:28:30,005 ############################ 2025-12-13T07:28:30,006 Python recognizes 'seal5.cli' as an importable package[^1], 2025-12-13T07:28:30,006 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,007 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,008 package, please make sure that 'seal5.cli' is explicitly added 2025-12-13T07:28:30,008 to the `packages` configuration field. 2025-12-13T07:28:30,009 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,010 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,010 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,011 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,012 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,013 If you don't want 'seal5.cli' to be distributed and are 2025-12-13T07:28:30,014 already explicitly excluding 'seal5.cli' via 2025-12-13T07:28:30,014 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,015 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,015 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,017 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,018 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,019 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,019 even if it does not contain any `.py` files. 2025-12-13T07:28:30,019 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,020 directory, all directories are treated like packages. 2025-12-13T07:28:30,020 ******************************************************************************** 2025-12-13T07:28:30,021 !! 2025-12-13T07:28:30,021 check.warn(importable) 2025-12-13T07:28:30,022 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.frontends.coredsl2_seal5' is absent from the `packages` configuration. 2025-12-13T07:28:30,022 !! 2025-12-13T07:28:30,023 ******************************************************************************** 2025-12-13T07:28:30,023 ############################ 2025-12-13T07:28:30,023 # Package would be ignored # 2025-12-13T07:28:30,024 ############################ 2025-12-13T07:28:30,024 Python recognizes 'seal5.frontends.coredsl2_seal5' as an importable package[^1], 2025-12-13T07:28:30,025 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,025 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,026 package, please make sure that 'seal5.frontends.coredsl2_seal5' is explicitly added 2025-12-13T07:28:30,026 to the `packages` configuration field. 2025-12-13T07:28:30,027 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,028 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,028 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,029 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,031 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,032 If you don't want 'seal5.frontends.coredsl2_seal5' to be distributed and are 2025-12-13T07:28:30,032 already explicitly excluding 'seal5.frontends.coredsl2_seal5' via 2025-12-13T07:28:30,033 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,033 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,034 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,035 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,036 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,037 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,038 even if it does not contain any `.py` files. 2025-12-13T07:28:30,038 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,039 directory, all directories are treated like packages. 2025-12-13T07:28:30,039 ******************************************************************************** 2025-12-13T07:28:30,040 !! 2025-12-13T07:28:30,041 check.warn(importable) 2025-12-13T07:28:30,042 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.frontends.coredsl2_seal5.parser_gen' is absent from the `packages` configuration. 2025-12-13T07:28:30,042 !! 2025-12-13T07:28:30,044 ******************************************************************************** 2025-12-13T07:28:30,044 ############################ 2025-12-13T07:28:30,045 # Package would be ignored # 2025-12-13T07:28:30,045 ############################ 2025-12-13T07:28:30,046 Python recognizes 'seal5.frontends.coredsl2_seal5.parser_gen' as an importable package[^1], 2025-12-13T07:28:30,046 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,047 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,047 package, please make sure that 'seal5.frontends.coredsl2_seal5.parser_gen' is explicitly added 2025-12-13T07:28:30,047 to the `packages` configuration field. 2025-12-13T07:28:30,048 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,048 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,049 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,050 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,050 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,051 If you don't want 'seal5.frontends.coredsl2_seal5.parser_gen' to be distributed and are 2025-12-13T07:28:30,051 already explicitly excluding 'seal5.frontends.coredsl2_seal5.parser_gen' via 2025-12-13T07:28:30,052 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,052 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,052 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,054 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,055 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,056 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,057 even if it does not contain any `.py` files. 2025-12-13T07:28:30,057 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,058 directory, all directories are treated like packages. 2025-12-13T07:28:30,058 ******************************************************************************** 2025-12-13T07:28:30,059 !! 2025-12-13T07:28:30,060 check.warn(importable) 2025-12-13T07:28:30,060 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.resources' is absent from the `packages` configuration. 2025-12-13T07:28:30,061 !! 2025-12-13T07:28:30,062 ******************************************************************************** 2025-12-13T07:28:30,062 ############################ 2025-12-13T07:28:30,063 # Package would be ignored # 2025-12-13T07:28:30,063 ############################ 2025-12-13T07:28:30,064 Python recognizes 'seal5.resources' as an importable package[^1], 2025-12-13T07:28:30,064 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,065 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,066 package, please make sure that 'seal5.resources' is explicitly added 2025-12-13T07:28:30,066 to the `packages` configuration field. 2025-12-13T07:28:30,067 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,068 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,068 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,069 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,070 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,072 If you don't want 'seal5.resources' to be distributed and are 2025-12-13T07:28:30,073 already explicitly excluding 'seal5.resources' via 2025-12-13T07:28:30,073 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,074 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,074 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,075 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,076 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,077 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,078 even if it does not contain any `.py` files. 2025-12-13T07:28:30,078 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,079 directory, all directories are treated like packages. 2025-12-13T07:28:30,079 ******************************************************************************** 2025-12-13T07:28:30,080 !! 2025-12-13T07:28:30,081 check.warn(importable) 2025-12-13T07:28:30,081 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.resources.patches.llvm' is absent from the `packages` configuration. 2025-12-13T07:28:30,082 !! 2025-12-13T07:28:30,083 ******************************************************************************** 2025-12-13T07:28:30,083 ############################ 2025-12-13T07:28:30,084 # Package would be ignored # 2025-12-13T07:28:30,085 ############################ 2025-12-13T07:28:30,085 Python recognizes 'seal5.resources.patches.llvm' as an importable package[^1], 2025-12-13T07:28:30,086 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,087 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,087 package, please make sure that 'seal5.resources.patches.llvm' is explicitly added 2025-12-13T07:28:30,088 to the `packages` configuration field. 2025-12-13T07:28:30,089 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,090 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,091 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,092 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,093 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,095 If you don't want 'seal5.resources.patches.llvm' to be distributed and are 2025-12-13T07:28:30,095 already explicitly excluding 'seal5.resources.patches.llvm' via 2025-12-13T07:28:30,096 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,096 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,097 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,098 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,099 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,101 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,102 even if it does not contain any `.py` files. 2025-12-13T07:28:30,103 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,104 directory, all directories are treated like packages. 2025-12-13T07:28:30,104 ******************************************************************************** 2025-12-13T07:28:30,106 !! 2025-12-13T07:28:30,106 check.warn(importable) 2025-12-13T07:28:30,107 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.tools' is absent from the `packages` configuration. 2025-12-13T07:28:30,107 !! 2025-12-13T07:28:30,108 ******************************************************************************** 2025-12-13T07:28:30,109 ############################ 2025-12-13T07:28:30,109 # Package would be ignored # 2025-12-13T07:28:30,110 ############################ 2025-12-13T07:28:30,110 Python recognizes 'seal5.tools' as an importable package[^1], 2025-12-13T07:28:30,111 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,112 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,112 package, please make sure that 'seal5.tools' is explicitly added 2025-12-13T07:28:30,113 to the `packages` configuration field. 2025-12-13T07:28:30,114 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,114 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,115 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,116 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,117 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,118 If you don't want 'seal5.tools' to be distributed and are 2025-12-13T07:28:30,118 already explicitly excluding 'seal5.tools' via 2025-12-13T07:28:30,119 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,119 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,120 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,121 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,122 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,124 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,125 even if it does not contain any `.py` files. 2025-12-13T07:28:30,126 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,126 directory, all directories are treated like packages. 2025-12-13T07:28:30,127 ******************************************************************************** 2025-12-13T07:28:30,129 !! 2025-12-13T07:28:30,130 check.warn(importable) 2025-12-13T07:28:30,130 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform' is absent from the `packages` configuration. 2025-12-13T07:28:30,131 !! 2025-12-13T07:28:30,132 ******************************************************************************** 2025-12-13T07:28:30,133 ############################ 2025-12-13T07:28:30,133 # Package would be ignored # 2025-12-13T07:28:30,134 ############################ 2025-12-13T07:28:30,135 Python recognizes 'seal5.transform' as an importable package[^1], 2025-12-13T07:28:30,135 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,137 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,137 package, please make sure that 'seal5.transform' is explicitly added 2025-12-13T07:28:30,138 to the `packages` configuration field. 2025-12-13T07:28:30,139 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,140 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,141 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,142 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,143 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,144 If you don't want 'seal5.transform' to be distributed and are 2025-12-13T07:28:30,144 already explicitly excluding 'seal5.transform' via 2025-12-13T07:28:30,145 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,145 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,146 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,147 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,148 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,149 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,150 even if it does not contain any `.py` files. 2025-12-13T07:28:30,150 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,151 directory, all directories are treated like packages. 2025-12-13T07:28:30,151 ******************************************************************************** 2025-12-13T07:28:30,152 !! 2025-12-13T07:28:30,153 check.warn(importable) 2025-12-13T07:28:30,153 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.annotate_opcodes' is absent from the `packages` configuration. 2025-12-13T07:28:30,154 !! 2025-12-13T07:28:30,155 ******************************************************************************** 2025-12-13T07:28:30,156 ############################ 2025-12-13T07:28:30,156 # Package would be ignored # 2025-12-13T07:28:30,157 ############################ 2025-12-13T07:28:30,157 Python recognizes 'seal5.transform.annotate_opcodes' as an importable package[^1], 2025-12-13T07:28:30,158 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,159 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,160 package, please make sure that 'seal5.transform.annotate_opcodes' is explicitly added 2025-12-13T07:28:30,160 to the `packages` configuration field. 2025-12-13T07:28:30,162 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,162 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,163 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,164 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,166 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,167 If you don't want 'seal5.transform.annotate_opcodes' to be distributed and are 2025-12-13T07:28:30,167 already explicitly excluding 'seal5.transform.annotate_opcodes' via 2025-12-13T07:28:30,168 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,169 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,169 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,171 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,172 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,174 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,175 even if it does not contain any `.py` files. 2025-12-13T07:28:30,175 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,176 directory, all directories are treated like packages. 2025-12-13T07:28:30,176 ******************************************************************************** 2025-12-13T07:28:30,177 !! 2025-12-13T07:28:30,177 check.warn(importable) 2025-12-13T07:28:30,178 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.check_pattern_support' is absent from the `packages` configuration. 2025-12-13T07:28:30,178 !! 2025-12-13T07:28:30,179 ******************************************************************************** 2025-12-13T07:28:30,180 ############################ 2025-12-13T07:28:30,180 # Package would be ignored # 2025-12-13T07:28:30,181 ############################ 2025-12-13T07:28:30,181 Python recognizes 'seal5.transform.check_pattern_support' as an importable package[^1], 2025-12-13T07:28:30,182 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,183 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,183 package, please make sure that 'seal5.transform.check_pattern_support' is explicitly added 2025-12-13T07:28:30,184 to the `packages` configuration field. 2025-12-13T07:28:30,185 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,186 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,186 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,187 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,188 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,190 If you don't want 'seal5.transform.check_pattern_support' to be distributed and are 2025-12-13T07:28:30,190 already explicitly excluding 'seal5.transform.check_pattern_support' via 2025-12-13T07:28:30,191 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,191 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,192 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,193 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,194 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,196 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,197 even if it does not contain any `.py` files. 2025-12-13T07:28:30,197 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,198 directory, all directories are treated like packages. 2025-12-13T07:28:30,198 ******************************************************************************** 2025-12-13T07:28:30,200 !! 2025-12-13T07:28:30,200 check.warn(importable) 2025-12-13T07:28:30,201 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.collect_immediate_operands' is absent from the `packages` configuration. 2025-12-13T07:28:30,202 !! 2025-12-13T07:28:30,203 ******************************************************************************** 2025-12-13T07:28:30,204 ############################ 2025-12-13T07:28:30,204 # Package would be ignored # 2025-12-13T07:28:30,205 ############################ 2025-12-13T07:28:30,205 Python recognizes 'seal5.transform.collect_immediate_operands' as an importable package[^1], 2025-12-13T07:28:30,206 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,207 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,208 package, please make sure that 'seal5.transform.collect_immediate_operands' is explicitly added 2025-12-13T07:28:30,208 to the `packages` configuration field. 2025-12-13T07:28:30,209 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,210 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,210 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,211 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,212 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,213 If you don't want 'seal5.transform.collect_immediate_operands' to be distributed and are 2025-12-13T07:28:30,214 already explicitly excluding 'seal5.transform.collect_immediate_operands' via 2025-12-13T07:28:30,215 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,215 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,216 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,217 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,218 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,220 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,221 even if it does not contain any `.py` files. 2025-12-13T07:28:30,222 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,223 directory, all directories are treated like packages. 2025-12-13T07:28:30,223 ******************************************************************************** 2025-12-13T07:28:30,224 !! 2025-12-13T07:28:30,225 check.warn(importable) 2025-12-13T07:28:30,226 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.collect_operand_types' is absent from the `packages` configuration. 2025-12-13T07:28:30,226 !! 2025-12-13T07:28:30,228 ******************************************************************************** 2025-12-13T07:28:30,229 ############################ 2025-12-13T07:28:30,229 # Package would be ignored # 2025-12-13T07:28:30,230 ############################ 2025-12-13T07:28:30,231 Python recognizes 'seal5.transform.collect_operand_types' as an importable package[^1], 2025-12-13T07:28:30,231 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,233 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,233 package, please make sure that 'seal5.transform.collect_operand_types' is explicitly added 2025-12-13T07:28:30,234 to the `packages` configuration field. 2025-12-13T07:28:30,236 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,236 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,237 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,239 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,240 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,242 If you don't want 'seal5.transform.collect_operand_types' to be distributed and are 2025-12-13T07:28:30,243 already explicitly excluding 'seal5.transform.collect_operand_types' via 2025-12-13T07:28:30,243 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,244 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,245 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,246 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,247 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,249 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,249 even if it does not contain any `.py` files. 2025-12-13T07:28:30,250 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,250 directory, all directories are treated like packages. 2025-12-13T07:28:30,251 ******************************************************************************** 2025-12-13T07:28:30,252 !! 2025-12-13T07:28:30,253 check.warn(importable) 2025-12-13T07:28:30,254 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.collect_raises' is absent from the `packages` configuration. 2025-12-13T07:28:30,254 !! 2025-12-13T07:28:30,256 ******************************************************************************** 2025-12-13T07:28:30,256 ############################ 2025-12-13T07:28:30,257 # Package would be ignored # 2025-12-13T07:28:30,258 ############################ 2025-12-13T07:28:30,259 Python recognizes 'seal5.transform.collect_raises' as an importable package[^1], 2025-12-13T07:28:30,259 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,261 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,261 package, please make sure that 'seal5.transform.collect_raises' is explicitly added 2025-12-13T07:28:30,262 to the `packages` configuration field. 2025-12-13T07:28:30,263 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,264 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,264 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,266 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,267 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,268 If you don't want 'seal5.transform.collect_raises' to be distributed and are 2025-12-13T07:28:30,269 already explicitly excluding 'seal5.transform.collect_raises' via 2025-12-13T07:28:30,270 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,270 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,271 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,273 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,274 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,276 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,277 even if it does not contain any `.py` files. 2025-12-13T07:28:30,277 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,278 directory, all directories are treated like packages. 2025-12-13T07:28:30,279 ******************************************************************************** 2025-12-13T07:28:30,281 !! 2025-12-13T07:28:30,281 check.warn(importable) 2025-12-13T07:28:30,282 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.collect_register_operands' is absent from the `packages` configuration. 2025-12-13T07:28:30,282 !! 2025-12-13T07:28:30,284 ******************************************************************************** 2025-12-13T07:28:30,284 ############################ 2025-12-13T07:28:30,285 # Package would be ignored # 2025-12-13T07:28:30,285 ############################ 2025-12-13T07:28:30,286 Python recognizes 'seal5.transform.collect_register_operands' as an importable package[^1], 2025-12-13T07:28:30,286 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,288 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,288 package, please make sure that 'seal5.transform.collect_register_operands' is explicitly added 2025-12-13T07:28:30,289 to the `packages` configuration field. 2025-12-13T07:28:30,290 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,291 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,292 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,293 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,294 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,295 If you don't want 'seal5.transform.collect_register_operands' to be distributed and are 2025-12-13T07:28:30,296 already explicitly excluding 'seal5.transform.collect_register_operands' via 2025-12-13T07:28:30,297 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,297 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,298 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,300 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,301 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,303 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,304 even if it does not contain any `.py` files. 2025-12-13T07:28:30,304 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,305 directory, all directories are treated like packages. 2025-12-13T07:28:30,306 ******************************************************************************** 2025-12-13T07:28:30,307 !! 2025-12-13T07:28:30,308 check.warn(importable) 2025-12-13T07:28:30,309 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.detect_calls' is absent from the `packages` configuration. 2025-12-13T07:28:30,309 !! 2025-12-13T07:28:30,310 ******************************************************************************** 2025-12-13T07:28:30,311 ############################ 2025-12-13T07:28:30,312 # Package would be ignored # 2025-12-13T07:28:30,313 ############################ 2025-12-13T07:28:30,313 Python recognizes 'seal5.transform.detect_calls' as an importable package[^1], 2025-12-13T07:28:30,314 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,315 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,316 package, please make sure that 'seal5.transform.detect_calls' is explicitly added 2025-12-13T07:28:30,317 to the `packages` configuration field. 2025-12-13T07:28:30,319 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,319 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,320 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,321 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,323 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,324 If you don't want 'seal5.transform.detect_calls' to be distributed and are 2025-12-13T07:28:30,325 already explicitly excluding 'seal5.transform.detect_calls' via 2025-12-13T07:28:30,326 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,327 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,327 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,328 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,330 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,333 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,333 even if it does not contain any `.py` files. 2025-12-13T07:28:30,334 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,335 directory, all directories are treated like packages. 2025-12-13T07:28:30,335 ******************************************************************************** 2025-12-13T07:28:30,337 !! 2025-12-13T07:28:30,338 check.warn(importable) 2025-12-13T07:28:30,339 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.detect_imm_leafs' is absent from the `packages` configuration. 2025-12-13T07:28:30,339 !! 2025-12-13T07:28:30,341 ******************************************************************************** 2025-12-13T07:28:30,341 ############################ 2025-12-13T07:28:30,342 # Package would be ignored # 2025-12-13T07:28:30,343 ############################ 2025-12-13T07:28:30,344 Python recognizes 'seal5.transform.detect_imm_leafs' as an importable package[^1], 2025-12-13T07:28:30,344 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,346 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,346 package, please make sure that 'seal5.transform.detect_imm_leafs' is explicitly added 2025-12-13T07:28:30,347 to the `packages` configuration field. 2025-12-13T07:28:30,349 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,349 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,350 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,351 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,353 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,354 If you don't want 'seal5.transform.detect_imm_leafs' to be distributed and are 2025-12-13T07:28:30,355 already explicitly excluding 'seal5.transform.detect_imm_leafs' via 2025-12-13T07:28:30,356 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,356 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,357 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,359 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,360 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,362 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,363 even if it does not contain any `.py` files. 2025-12-13T07:28:30,364 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,364 directory, all directories are treated like packages. 2025-12-13T07:28:30,365 ******************************************************************************** 2025-12-13T07:28:30,367 !! 2025-12-13T07:28:30,367 check.warn(importable) 2025-12-13T07:28:30,368 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.detect_inouts' is absent from the `packages` configuration. 2025-12-13T07:28:30,368 !! 2025-12-13T07:28:30,370 ******************************************************************************** 2025-12-13T07:28:30,371 ############################ 2025-12-13T07:28:30,371 # Package would be ignored # 2025-12-13T07:28:30,372 ############################ 2025-12-13T07:28:30,372 Python recognizes 'seal5.transform.detect_inouts' as an importable package[^1], 2025-12-13T07:28:30,373 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,374 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,375 package, please make sure that 'seal5.transform.detect_inouts' is explicitly added 2025-12-13T07:28:30,375 to the `packages` configuration field. 2025-12-13T07:28:30,376 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,377 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,377 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,379 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,380 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,381 If you don't want 'seal5.transform.detect_inouts' to be distributed and are 2025-12-13T07:28:30,381 already explicitly excluding 'seal5.transform.detect_inouts' via 2025-12-13T07:28:30,382 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,383 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,383 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,384 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,385 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,387 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,388 even if it does not contain any `.py` files. 2025-12-13T07:28:30,388 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,389 directory, all directories are treated like packages. 2025-12-13T07:28:30,389 ******************************************************************************** 2025-12-13T07:28:30,391 !! 2025-12-13T07:28:30,391 check.warn(importable) 2025-12-13T07:28:30,392 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.detect_loops' is absent from the `packages` configuration. 2025-12-13T07:28:30,392 !! 2025-12-13T07:28:30,394 ******************************************************************************** 2025-12-13T07:28:30,394 ############################ 2025-12-13T07:28:30,395 # Package would be ignored # 2025-12-13T07:28:30,395 ############################ 2025-12-13T07:28:30,396 Python recognizes 'seal5.transform.detect_loops' as an importable package[^1], 2025-12-13T07:28:30,396 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,397 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,398 package, please make sure that 'seal5.transform.detect_loops' is explicitly added 2025-12-13T07:28:30,398 to the `packages` configuration field. 2025-12-13T07:28:30,399 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,400 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,400 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,402 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,402 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,404 If you don't want 'seal5.transform.detect_loops' to be distributed and are 2025-12-13T07:28:30,404 already explicitly excluding 'seal5.transform.detect_loops' via 2025-12-13T07:28:30,405 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,405 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,406 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,407 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,408 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,410 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,410 even if it does not contain any `.py` files. 2025-12-13T07:28:30,411 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,411 directory, all directories are treated like packages. 2025-12-13T07:28:30,412 ******************************************************************************** 2025-12-13T07:28:30,413 !! 2025-12-13T07:28:30,413 check.warn(importable) 2025-12-13T07:28:30,414 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.detect_registers' is absent from the `packages` configuration. 2025-12-13T07:28:30,414 !! 2025-12-13T07:28:30,415 ******************************************************************************** 2025-12-13T07:28:30,416 ############################ 2025-12-13T07:28:30,417 # Package would be ignored # 2025-12-13T07:28:30,417 ############################ 2025-12-13T07:28:30,418 Python recognizes 'seal5.transform.detect_registers' as an importable package[^1], 2025-12-13T07:28:30,418 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,419 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,420 package, please make sure that 'seal5.transform.detect_registers' is explicitly added 2025-12-13T07:28:30,420 to the `packages` configuration field. 2025-12-13T07:28:30,421 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,422 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,423 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,424 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,425 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,426 If you don't want 'seal5.transform.detect_registers' to be distributed and are 2025-12-13T07:28:30,426 already explicitly excluding 'seal5.transform.detect_registers' via 2025-12-13T07:28:30,427 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,427 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,428 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,429 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,430 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,431 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,431 even if it does not contain any `.py` files. 2025-12-13T07:28:30,432 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,432 directory, all directories are treated like packages. 2025-12-13T07:28:30,433 ******************************************************************************** 2025-12-13T07:28:30,434 !! 2025-12-13T07:28:30,434 check.warn(importable) 2025-12-13T07:28:30,435 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.detect_side_effects' is absent from the `packages` configuration. 2025-12-13T07:28:30,435 !! 2025-12-13T07:28:30,436 ******************************************************************************** 2025-12-13T07:28:30,437 ############################ 2025-12-13T07:28:30,437 # Package would be ignored # 2025-12-13T07:28:30,438 ############################ 2025-12-13T07:28:30,438 Python recognizes 'seal5.transform.detect_side_effects' as an importable package[^1], 2025-12-13T07:28:30,439 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,440 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,440 package, please make sure that 'seal5.transform.detect_side_effects' is explicitly added 2025-12-13T07:28:30,441 to the `packages` configuration field. 2025-12-13T07:28:30,442 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,443 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,443 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,444 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,445 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,446 If you don't want 'seal5.transform.detect_side_effects' to be distributed and are 2025-12-13T07:28:30,447 already explicitly excluding 'seal5.transform.detect_side_effects' via 2025-12-13T07:28:30,447 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,448 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,448 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,450 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,451 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,452 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,453 even if it does not contain any `.py` files. 2025-12-13T07:28:30,454 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,454 directory, all directories are treated like packages. 2025-12-13T07:28:30,455 ******************************************************************************** 2025-12-13T07:28:30,456 !! 2025-12-13T07:28:30,457 check.warn(importable) 2025-12-13T07:28:30,457 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.drop_unused' is absent from the `packages` configuration. 2025-12-13T07:28:30,457 !! 2025-12-13T07:28:30,458 ******************************************************************************** 2025-12-13T07:28:30,459 ############################ 2025-12-13T07:28:30,459 # Package would be ignored # 2025-12-13T07:28:30,460 ############################ 2025-12-13T07:28:30,460 Python recognizes 'seal5.transform.drop_unused' as an importable package[^1], 2025-12-13T07:28:30,460 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,462 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,462 package, please make sure that 'seal5.transform.drop_unused' is explicitly added 2025-12-13T07:28:30,462 to the `packages` configuration field. 2025-12-13T07:28:30,463 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,464 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,464 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,465 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,466 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,467 If you don't want 'seal5.transform.drop_unused' to be distributed and are 2025-12-13T07:28:30,467 already explicitly excluding 'seal5.transform.drop_unused' via 2025-12-13T07:28:30,468 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,468 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,469 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,470 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,471 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,473 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,473 even if it does not contain any `.py` files. 2025-12-13T07:28:30,474 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,474 directory, all directories are treated like packages. 2025-12-13T07:28:30,475 ******************************************************************************** 2025-12-13T07:28:30,476 !! 2025-12-13T07:28:30,476 check.warn(importable) 2025-12-13T07:28:30,477 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.eliminate_mod_rfs' is absent from the `packages` configuration. 2025-12-13T07:28:30,477 !! 2025-12-13T07:28:30,478 ******************************************************************************** 2025-12-13T07:28:30,479 ############################ 2025-12-13T07:28:30,479 # Package would be ignored # 2025-12-13T07:28:30,480 ############################ 2025-12-13T07:28:30,480 Python recognizes 'seal5.transform.eliminate_mod_rfs' as an importable package[^1], 2025-12-13T07:28:30,481 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,482 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,482 package, please make sure that 'seal5.transform.eliminate_mod_rfs' is explicitly added 2025-12-13T07:28:30,483 to the `packages` configuration field. 2025-12-13T07:28:30,484 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,484 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,485 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,486 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,487 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,488 If you don't want 'seal5.transform.eliminate_mod_rfs' to be distributed and are 2025-12-13T07:28:30,488 already explicitly excluding 'seal5.transform.eliminate_mod_rfs' via 2025-12-13T07:28:30,488 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,489 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,489 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,490 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,491 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,493 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,493 even if it does not contain any `.py` files. 2025-12-13T07:28:30,494 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,494 directory, all directories are treated like packages. 2025-12-13T07:28:30,494 ******************************************************************************** 2025-12-13T07:28:30,495 !! 2025-12-13T07:28:30,496 check.warn(importable) 2025-12-13T07:28:30,496 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.eliminate_rd_cmp_zero' is absent from the `packages` configuration. 2025-12-13T07:28:30,497 !! 2025-12-13T07:28:30,498 ******************************************************************************** 2025-12-13T07:28:30,499 ############################ 2025-12-13T07:28:30,499 # Package would be ignored # 2025-12-13T07:28:30,500 ############################ 2025-12-13T07:28:30,500 Python recognizes 'seal5.transform.eliminate_rd_cmp_zero' as an importable package[^1], 2025-12-13T07:28:30,501 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,502 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,502 package, please make sure that 'seal5.transform.eliminate_rd_cmp_zero' is explicitly added 2025-12-13T07:28:30,503 to the `packages` configuration field. 2025-12-13T07:28:30,504 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,505 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,505 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,506 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,507 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,509 If you don't want 'seal5.transform.eliminate_rd_cmp_zero' to be distributed and are 2025-12-13T07:28:30,509 already explicitly excluding 'seal5.transform.eliminate_rd_cmp_zero' via 2025-12-13T07:28:30,510 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,510 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,511 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,512 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,514 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,517 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,517 even if it does not contain any `.py` files. 2025-12-13T07:28:30,518 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,518 directory, all directories are treated like packages. 2025-12-13T07:28:30,519 ******************************************************************************** 2025-12-13T07:28:30,521 !! 2025-12-13T07:28:30,521 check.warn(importable) 2025-12-13T07:28:30,522 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.explicit_truncations' is absent from the `packages` configuration. 2025-12-13T07:28:30,522 !! 2025-12-13T07:28:30,524 ******************************************************************************** 2025-12-13T07:28:30,525 ############################ 2025-12-13T07:28:30,525 # Package would be ignored # 2025-12-13T07:28:30,527 ############################ 2025-12-13T07:28:30,527 Python recognizes 'seal5.transform.explicit_truncations' as an importable package[^1], 2025-12-13T07:28:30,528 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,530 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,530 package, please make sure that 'seal5.transform.explicit_truncations' is explicitly added 2025-12-13T07:28:30,531 to the `packages` configuration field. 2025-12-13T07:28:30,532 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,534 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,534 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,536 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,537 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,539 If you don't want 'seal5.transform.explicit_truncations' to be distributed and are 2025-12-13T07:28:30,540 already explicitly excluding 'seal5.transform.explicit_truncations' via 2025-12-13T07:28:30,541 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,542 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,542 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,544 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,545 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,546 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,547 even if it does not contain any `.py` files. 2025-12-13T07:28:30,547 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,548 directory, all directories are treated like packages. 2025-12-13T07:28:30,548 ******************************************************************************** 2025-12-13T07:28:30,550 !! 2025-12-13T07:28:30,551 check.warn(importable) 2025-12-13T07:28:30,551 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.filter_model' is absent from the `packages` configuration. 2025-12-13T07:28:30,552 !! 2025-12-13T07:28:30,553 ******************************************************************************** 2025-12-13T07:28:30,554 ############################ 2025-12-13T07:28:30,554 # Package would be ignored # 2025-12-13T07:28:30,555 ############################ 2025-12-13T07:28:30,556 Python recognizes 'seal5.transform.filter_model' as an importable package[^1], 2025-12-13T07:28:30,556 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,557 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,557 package, please make sure that 'seal5.transform.filter_model' is explicitly added 2025-12-13T07:28:30,558 to the `packages` configuration field. 2025-12-13T07:28:30,559 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,559 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,560 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,561 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,562 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,563 If you don't want 'seal5.transform.filter_model' to be distributed and are 2025-12-13T07:28:30,564 already explicitly excluding 'seal5.transform.filter_model' via 2025-12-13T07:28:30,564 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,565 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,565 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,566 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,567 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,569 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,569 even if it does not contain any `.py` files. 2025-12-13T07:28:30,570 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,571 directory, all directories are treated like packages. 2025-12-13T07:28:30,572 ******************************************************************************** 2025-12-13T07:28:30,575 !! 2025-12-13T07:28:30,576 check.warn(importable) 2025-12-13T07:28:30,576 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.infer_types' is absent from the `packages` configuration. 2025-12-13T07:28:30,577 !! 2025-12-13T07:28:30,578 ******************************************************************************** 2025-12-13T07:28:30,579 ############################ 2025-12-13T07:28:30,579 # Package would be ignored # 2025-12-13T07:28:30,580 ############################ 2025-12-13T07:28:30,580 Python recognizes 'seal5.transform.infer_types' as an importable package[^1], 2025-12-13T07:28:30,581 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,582 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,582 package, please make sure that 'seal5.transform.infer_types' is explicitly added 2025-12-13T07:28:30,583 to the `packages` configuration field. 2025-12-13T07:28:30,584 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,584 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,585 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,586 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,587 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,588 If you don't want 'seal5.transform.infer_types' to be distributed and are 2025-12-13T07:28:30,589 already explicitly excluding 'seal5.transform.infer_types' via 2025-12-13T07:28:30,590 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,590 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,590 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,591 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,592 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,593 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,594 even if it does not contain any `.py` files. 2025-12-13T07:28:30,594 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,595 directory, all directories are treated like packages. 2025-12-13T07:28:30,595 ******************************************************************************** 2025-12-13T07:28:30,596 !! 2025-12-13T07:28:30,596 check.warn(importable) 2025-12-13T07:28:30,597 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.inline_functions' is absent from the `packages` configuration. 2025-12-13T07:28:30,597 !! 2025-12-13T07:28:30,598 ******************************************************************************** 2025-12-13T07:28:30,599 ############################ 2025-12-13T07:28:30,599 # Package would be ignored # 2025-12-13T07:28:30,600 ############################ 2025-12-13T07:28:30,600 Python recognizes 'seal5.transform.inline_functions' as an importable package[^1], 2025-12-13T07:28:30,601 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,602 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,602 package, please make sure that 'seal5.transform.inline_functions' is explicitly added 2025-12-13T07:28:30,603 to the `packages` configuration field. 2025-12-13T07:28:30,604 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,604 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,605 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,606 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,607 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,608 If you don't want 'seal5.transform.inline_functions' to be distributed and are 2025-12-13T07:28:30,609 already explicitly excluding 'seal5.transform.inline_functions' via 2025-12-13T07:28:30,609 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,610 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,610 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,611 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,613 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,614 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,615 even if it does not contain any `.py` files. 2025-12-13T07:28:30,616 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,616 directory, all directories are treated like packages. 2025-12-13T07:28:30,617 ******************************************************************************** 2025-12-13T07:28:30,618 !! 2025-12-13T07:28:30,618 check.warn(importable) 2025-12-13T07:28:30,619 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.optimize_instructions' is absent from the `packages` configuration. 2025-12-13T07:28:30,619 !! 2025-12-13T07:28:30,620 ******************************************************************************** 2025-12-13T07:28:30,620 ############################ 2025-12-13T07:28:30,621 # Package would be ignored # 2025-12-13T07:28:30,621 ############################ 2025-12-13T07:28:30,622 Python recognizes 'seal5.transform.optimize_instructions' as an importable package[^1], 2025-12-13T07:28:30,622 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,623 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,624 package, please make sure that 'seal5.transform.optimize_instructions' is explicitly added 2025-12-13T07:28:30,624 to the `packages` configuration field. 2025-12-13T07:28:30,625 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,626 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,626 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,627 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,628 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,629 If you don't want 'seal5.transform.optimize_instructions' to be distributed and are 2025-12-13T07:28:30,630 already explicitly excluding 'seal5.transform.optimize_instructions' via 2025-12-13T07:28:30,630 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,631 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,631 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,632 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,633 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,635 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,635 even if it does not contain any `.py` files. 2025-12-13T07:28:30,636 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,637 directory, all directories are treated like packages. 2025-12-13T07:28:30,637 ******************************************************************************** 2025-12-13T07:28:30,638 !! 2025-12-13T07:28:30,639 check.warn(importable) 2025-12-13T07:28:30,639 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.process_settings' is absent from the `packages` configuration. 2025-12-13T07:28:30,640 !! 2025-12-13T07:28:30,641 ******************************************************************************** 2025-12-13T07:28:30,642 ############################ 2025-12-13T07:28:30,642 # Package would be ignored # 2025-12-13T07:28:30,643 ############################ 2025-12-13T07:28:30,644 Python recognizes 'seal5.transform.process_settings' as an importable package[^1], 2025-12-13T07:28:30,644 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,645 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,646 package, please make sure that 'seal5.transform.process_settings' is explicitly added 2025-12-13T07:28:30,646 to the `packages` configuration field. 2025-12-13T07:28:30,647 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,648 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,648 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,649 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,650 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,651 If you don't want 'seal5.transform.process_settings' to be distributed and are 2025-12-13T07:28:30,651 already explicitly excluding 'seal5.transform.process_settings' via 2025-12-13T07:28:30,652 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,652 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,653 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,654 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,655 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,656 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,656 even if it does not contain any `.py` files. 2025-12-13T07:28:30,657 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,657 directory, all directories are treated like packages. 2025-12-13T07:28:30,658 ******************************************************************************** 2025-12-13T07:28:30,659 !! 2025-12-13T07:28:30,659 check.warn(importable) 2025-12-13T07:28:30,660 /tmp/pip-build-env-kj9wjzmq/overlay/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'seal5.transform.simplify_trivial_slices' is absent from the `packages` configuration. 2025-12-13T07:28:30,660 !! 2025-12-13T07:28:30,661 ******************************************************************************** 2025-12-13T07:28:30,662 ############################ 2025-12-13T07:28:30,662 # Package would be ignored # 2025-12-13T07:28:30,663 ############################ 2025-12-13T07:28:30,663 Python recognizes 'seal5.transform.simplify_trivial_slices' as an importable package[^1], 2025-12-13T07:28:30,664 but it is absent from setuptools' `packages` configuration. 2025-12-13T07:28:30,665 This leads to an ambiguous overall configuration. If you want to distribute this 2025-12-13T07:28:30,666 package, please make sure that 'seal5.transform.simplify_trivial_slices' is explicitly added 2025-12-13T07:28:30,666 to the `packages` configuration field. 2025-12-13T07:28:30,667 Alternatively, you can also rely on setuptools' discovery methods 2025-12-13T07:28:30,668 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-12-13T07:28:30,668 instead of `find_packages(...)`/`find:`). 2025-12-13T07:28:30,669 You can read more about "package discovery" on setuptools documentation page: 2025-12-13T07:28:30,670 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-12-13T07:28:30,672 If you don't want 'seal5.transform.simplify_trivial_slices' to be distributed and are 2025-12-13T07:28:30,672 already explicitly excluding 'seal5.transform.simplify_trivial_slices' via 2025-12-13T07:28:30,673 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-12-13T07:28:30,673 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-12-13T07:28:30,674 combination with a more fine grained `package-data` configuration. 2025-12-13T07:28:30,675 You can read more about "package data files" on setuptools documentation page: 2025-12-13T07:28:30,676 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-12-13T07:28:30,678 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-12-13T07:28:30,678 even if it does not contain any `.py` files. 2025-12-13T07:28:30,678 On the other hand, currently there is no concept of package data 2025-12-13T07:28:30,679 directory, all directories are treated like packages. 2025-12-13T07:28:30,679 ******************************************************************************** 2025-12-13T07:28:30,680 !! 2025-12-13T07:28:30,681 check.warn(importable) 2025-12-13T07:28:30,681 creating build/lib/seal5/backends 2025-12-13T07:28:30,682 copying seal5/backends/__init__.py -> build/lib/seal5/backends 2025-12-13T07:28:30,682 creating build/lib/seal5/backends/coredsl2 2025-12-13T07:28:30,683 copying seal5/backends/coredsl2/__init__.py -> build/lib/seal5/backends/coredsl2 2025-12-13T07:28:30,683 copying seal5/backends/coredsl2/visitor.py -> build/lib/seal5/backends/coredsl2 2025-12-13T07:28:30,683 copying seal5/backends/coredsl2/writer.py -> build/lib/seal5/backends/coredsl2 2025-12-13T07:28:30,684 creating build/lib/seal5/backends/llvmir 2025-12-13T07:28:30,684 copying seal5/backends/llvmir/__init__.py -> build/lib/seal5/backends/llvmir 2025-12-13T07:28:30,685 copying seal5/backends/llvmir/writer.py -> build/lib/seal5/backends/llvmir 2025-12-13T07:28:30,685 creating build/lib/seal5/backends/patterngen 2025-12-13T07:28:30,686 copying seal5/backends/patterngen/__init__.py -> build/lib/seal5/backends/patterngen 2025-12-13T07:28:30,686 copying seal5/backends/patterngen/writer.py -> build/lib/seal5/backends/patterngen 2025-12-13T07:28:30,687 creating build/lib/seal5/backends/report 2025-12-13T07:28:30,687 copying seal5/backends/report/__init__.py -> build/lib/seal5/backends/report 2025-12-13T07:28:30,688 creating build/lib/seal5/backends/report/diff 2025-12-13T07:28:30,688 copying seal5/backends/report/diff/__init__.py -> build/lib/seal5/backends/report/diff 2025-12-13T07:28:30,689 copying seal5/backends/report/diff/writer.py -> build/lib/seal5/backends/report/diff 2025-12-13T07:28:30,689 creating build/lib/seal5/backends/report/pattern_gen 2025-12-13T07:28:30,690 copying seal5/backends/report/pattern_gen/__init__.py -> build/lib/seal5/backends/report/pattern_gen 2025-12-13T07:28:30,691 copying seal5/backends/report/pattern_gen/writer.py -> build/lib/seal5/backends/report/pattern_gen 2025-12-13T07:28:30,691 creating build/lib/seal5/backends/report/properties 2025-12-13T07:28:30,692 copying seal5/backends/report/properties/__init__.py -> build/lib/seal5/backends/report/properties 2025-12-13T07:28:30,693 copying seal5/backends/report/properties/writer.py -> build/lib/seal5/backends/report/properties 2025-12-13T07:28:30,693 creating build/lib/seal5/backends/report/status 2025-12-13T07:28:30,694 copying seal5/backends/report/status/__init__.py -> build/lib/seal5/backends/report/status 2025-12-13T07:28:30,694 copying seal5/backends/report/status/writer.py -> build/lib/seal5/backends/report/status 2025-12-13T07:28:30,695 creating build/lib/seal5/backends/report/test_results 2025-12-13T07:28:30,696 copying seal5/backends/report/test_results/__init__.py -> build/lib/seal5/backends/report/test_results 2025-12-13T07:28:30,697 copying seal5/backends/report/test_results/writer.py -> build/lib/seal5/backends/report/test_results 2025-12-13T07:28:30,697 creating build/lib/seal5/backends/report/times 2025-12-13T07:28:30,698 copying seal5/backends/report/times/__init__.py -> build/lib/seal5/backends/report/times 2025-12-13T07:28:30,699 copying seal5/backends/report/times/writer.py -> build/lib/seal5/backends/report/times 2025-12-13T07:28:30,700 creating build/lib/seal5/backends/riscv_features 2025-12-13T07:28:30,701 copying seal5/backends/riscv_features/__init__.py -> build/lib/seal5/backends/riscv_features 2025-12-13T07:28:30,702 copying seal5/backends/riscv_features/writer.py -> build/lib/seal5/backends/riscv_features 2025-12-13T07:28:30,702 creating build/lib/seal5/backends/riscv_features/templates 2025-12-13T07:28:30,703 copying seal5/backends/riscv_features/templates/__init__.py -> build/lib/seal5/backends/riscv_features/templates 2025-12-13T07:28:30,704 copying seal5/backends/riscv_features/templates/riscv_features.mako -> build/lib/seal5/backends/riscv_features/templates 2025-12-13T07:28:30,704 copying seal5/backends/riscv_features/templates/riscv_features_experimental_new.mako -> build/lib/seal5/backends/riscv_features/templates 2025-12-13T07:28:30,705 copying seal5/backends/riscv_features/templates/riscv_features_experimental_new_slim.mako -> build/lib/seal5/backends/riscv_features/templates 2025-12-13T07:28:30,705 copying seal5/backends/riscv_features/templates/riscv_features_new.mako -> build/lib/seal5/backends/riscv_features/templates 2025-12-13T07:28:30,706 copying seal5/backends/riscv_features/templates/riscv_features_new_slim.mako -> build/lib/seal5/backends/riscv_features/templates 2025-12-13T07:28:30,706 copying seal5/backends/riscv_features/templates/test_riscv_attributes.mako -> build/lib/seal5/backends/riscv_features/templates 2025-12-13T07:28:30,707 creating build/lib/seal5/backends/riscv_field_types 2025-12-13T07:28:30,707 copying seal5/backends/riscv_field_types/__init__.py -> build/lib/seal5/backends/riscv_field_types 2025-12-13T07:28:30,708 copying seal5/backends/riscv_field_types/writer.py -> build/lib/seal5/backends/riscv_field_types 2025-12-13T07:28:30,709 creating build/lib/seal5/backends/riscv_gisel_legalizer 2025-12-13T07:28:30,709 copying seal5/backends/riscv_gisel_legalizer/__init__.py -> build/lib/seal5/backends/riscv_gisel_legalizer 2025-12-13T07:28:30,710 copying seal5/backends/riscv_gisel_legalizer/writer.py -> build/lib/seal5/backends/riscv_gisel_legalizer 2025-12-13T07:28:30,710 creating build/lib/seal5/backends/riscv_instr_info 2025-12-13T07:28:30,711 copying seal5/backends/riscv_instr_info/__init__.py -> build/lib/seal5/backends/riscv_instr_info 2025-12-13T07:28:30,712 copying seal5/backends/riscv_instr_info/writer.py -> build/lib/seal5/backends/riscv_instr_info 2025-12-13T07:28:30,712 creating build/lib/seal5/backends/riscv_instr_info/templates 2025-12-13T07:28:30,713 copying seal5/backends/riscv_instr_info/templates/__init__.py -> build/lib/seal5/backends/riscv_instr_info/templates 2025-12-13T07:28:30,713 copying seal5/backends/riscv_instr_info/templates/instr_tablegen.mako -> build/lib/seal5/backends/riscv_instr_info/templates 2025-12-13T07:28:30,714 creating build/lib/seal5/backends/riscv_intrinsics 2025-12-13T07:28:30,715 copying seal5/backends/riscv_intrinsics/__init__.py -> build/lib/seal5/backends/riscv_intrinsics 2025-12-13T07:28:30,715 copying seal5/backends/riscv_intrinsics/writer.py -> build/lib/seal5/backends/riscv_intrinsics 2025-12-13T07:28:30,716 creating build/lib/seal5/backends/riscv_isa_info 2025-12-13T07:28:30,717 copying seal5/backends/riscv_isa_info/__init__.py -> build/lib/seal5/backends/riscv_isa_info 2025-12-13T07:28:30,717 copying seal5/backends/riscv_isa_info/writer.py -> build/lib/seal5/backends/riscv_isa_info 2025-12-13T07:28:30,718 creating build/lib/seal5/backends/riscv_register_info 2025-12-13T07:28:30,718 copying seal5/backends/riscv_register_info/__init__.py -> build/lib/seal5/backends/riscv_register_info 2025-12-13T07:28:30,719 copying seal5/backends/riscv_register_info/writer.py -> build/lib/seal5/backends/riscv_register_info 2025-12-13T07:28:30,719 creating build/lib/seal5/backends/viewer_seal5 2025-12-13T07:28:30,720 copying seal5/backends/viewer_seal5/__init__.py -> build/lib/seal5/backends/viewer_seal5 2025-12-13T07:28:30,721 copying seal5/backends/viewer_seal5/treegen.py -> build/lib/seal5/backends/viewer_seal5 2025-12-13T07:28:30,722 copying seal5/backends/viewer_seal5/utils.py -> build/lib/seal5/backends/viewer_seal5 2025-12-13T07:28:30,722 copying seal5/backends/viewer_seal5/viewer.py -> build/lib/seal5/backends/viewer_seal5 2025-12-13T07:28:30,724 creating build/lib/seal5/backends/yaml 2025-12-13T07:28:30,725 copying seal5/backends/yaml/__init__.py -> build/lib/seal5/backends/yaml 2025-12-13T07:28:30,725 copying seal5/backends/yaml/writer.py -> build/lib/seal5/backends/yaml 2025-12-13T07:28:30,727 creating build/lib/seal5/cli 2025-12-13T07:28:30,727 copying seal5/cli/__init__.py -> build/lib/seal5/cli 2025-12-13T07:28:30,728 copying seal5/cli/build.py -> build/lib/seal5/cli 2025-12-13T07:28:30,728 copying seal5/cli/clean.py -> build/lib/seal5/cli 2025-12-13T07:28:30,729 copying seal5/cli/common.py -> build/lib/seal5/cli 2025-12-13T07:28:30,729 copying seal5/cli/deploy.py -> build/lib/seal5/cli 2025-12-13T07:28:30,730 copying seal5/cli/export.py -> build/lib/seal5/cli 2025-12-13T07:28:30,731 copying seal5/cli/generate.py -> build/lib/seal5/cli 2025-12-13T07:28:30,732 copying seal5/cli/init.py -> build/lib/seal5/cli 2025-12-13T07:28:30,732 copying seal5/cli/install.py -> build/lib/seal5/cli 2025-12-13T07:28:30,733 copying seal5/cli/load.py -> build/lib/seal5/cli 2025-12-13T07:28:30,733 copying seal5/cli/main.py -> build/lib/seal5/cli 2025-12-13T07:28:30,734 copying seal5/cli/patch.py -> build/lib/seal5/cli 2025-12-13T07:28:30,734 copying seal5/cli/reset.py -> build/lib/seal5/cli 2025-12-13T07:28:30,735 copying seal5/cli/setup.py -> build/lib/seal5/cli 2025-12-13T07:28:30,735 copying seal5/cli/test.py -> build/lib/seal5/cli 2025-12-13T07:28:30,736 copying seal5/cli/transform.py -> build/lib/seal5/cli 2025-12-13T07:28:30,736 copying seal5/cli/wrapper.py -> build/lib/seal5/cli 2025-12-13T07:28:30,737 creating build/lib/seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,737 copying seal5/frontends/coredsl2_seal5/.gitignore -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,738 copying seal5/frontends/coredsl2_seal5/CoreDSL2.g4 -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,738 copying seal5/frontends/coredsl2_seal5/README.md -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,739 copying seal5/frontends/coredsl2_seal5/__init__.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,740 copying seal5/frontends/coredsl2_seal5/antlr.sh -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,740 copying seal5/frontends/coredsl2_seal5/architecture_model_builder.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,741 copying seal5/frontends/coredsl2_seal5/behavior_model_builder.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,742 copying seal5/frontends/coredsl2_seal5/expr_interpreter.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,742 copying seal5/frontends/coredsl2_seal5/importer.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,743 copying seal5/frontends/coredsl2_seal5/load_order.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,745 copying seal5/frontends/coredsl2_seal5/parser.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,746 copying seal5/frontends/coredsl2_seal5/utils.py -> build/lib/seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,746 creating build/lib/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-13T07:28:30,747 copying seal5/frontends/coredsl2_seal5/parser_gen/.gitignore -> build/lib/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-13T07:28:30,747 copying seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Lexer.py -> build/lib/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-13T07:28:30,748 copying seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Listener.py -> build/lib/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-13T07:28:30,749 copying seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Parser.py -> build/lib/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-13T07:28:30,750 copying seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Visitor.py -> build/lib/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-13T07:28:30,751 copying seal5/frontends/coredsl2_seal5/parser_gen/__init__.py -> build/lib/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-13T07:28:30,751 creating build/lib/seal5/resources 2025-12-13T07:28:30,752 copying seal5/resources/__init__.py -> build/lib/seal5/resources 2025-12-13T07:28:30,753 copying seal5/resources/lit.cfg.py -> build/lib/seal5/resources 2025-12-13T07:28:30,753 copying seal5/resources/resources.py -> build/lib/seal5/resources 2025-12-13T07:28:30,754 creating build/lib/seal5/resources/patches/llvm 2025-12-13T07:28:30,754 copying seal5/resources/patches/llvm/github_ci.patch -> build/lib/seal5/resources/patches/llvm 2025-12-13T07:28:30,754 copying seal5/resources/patches/llvm/gitignore.patch -> build/lib/seal5/resources/patches/llvm 2025-12-13T07:28:30,755 copying seal5/resources/patches/llvm/gitlab_ci.patch -> build/lib/seal5/resources/patches/llvm 2025-12-13T07:28:30,755 copying seal5/resources/patches/llvm/insert_markers_llvm17.patch -> build/lib/seal5/resources/patches/llvm 2025-12-13T07:28:30,756 copying seal5/resources/patches/llvm/insert_markers_llvm18.patch -> build/lib/seal5/resources/patches/llvm 2025-12-13T07:28:30,756 copying seal5/resources/patches/llvm/insert_markers_llvm19.patch -> build/lib/seal5/resources/patches/llvm 2025-12-13T07:28:30,757 copying seal5/resources/patches/llvm/insert_markers_llvm20.patch -> build/lib/seal5/resources/patches/llvm 2025-12-13T07:28:30,757 copying seal5/resources/patches/llvm/legalizer_fix_1.patch -> build/lib/seal5/resources/patches/llvm 2025-12-13T07:28:30,758 copying seal5/resources/patches/llvm/legalizer_fix_2.patch -> build/lib/seal5/resources/patches/llvm 2025-12-13T07:28:30,758 copying seal5/resources/patches/llvm/legalizer_split.patch -> build/lib/seal5/resources/patches/llvm 2025-12-13T07:28:30,759 copying seal5/resources/patches/llvm/regclass_gpr32v.patch -> build/lib/seal5/resources/patches/llvm 2025-12-13T07:28:30,759 copying seal5/resources/patches/llvm/simd_gpr32v.patch -> build/lib/seal5/resources/patches/llvm 2025-12-13T07:28:30,760 creating build/lib/seal5/tools 2025-12-13T07:28:30,761 copying seal5/tools/__init__.py -> build/lib/seal5/tools 2025-12-13T07:28:30,762 copying seal5/tools/cdsl2llvm.py -> build/lib/seal5/tools 2025-12-13T07:28:30,762 copying seal5/tools/cmake.py -> build/lib/seal5/tools 2025-12-13T07:28:30,763 copying seal5/tools/git.py -> build/lib/seal5/tools 2025-12-13T07:28:30,764 copying seal5/tools/inject_patches.py -> build/lib/seal5/tools 2025-12-13T07:28:30,765 copying seal5/tools/llvm.py -> build/lib/seal5/tools 2025-12-13T07:28:30,766 copying seal5/tools/m2isar.py -> build/lib/seal5/tools 2025-12-13T07:28:30,766 creating build/lib/seal5/transform 2025-12-13T07:28:30,767 copying seal5/transform/__init__.py -> build/lib/seal5/transform 2025-12-13T07:28:30,768 copying seal5/transform/converter.py -> build/lib/seal5/transform 2025-12-13T07:28:30,768 creating build/lib/seal5/transform/annotate_opcodes 2025-12-13T07:28:30,769 copying seal5/transform/annotate_opcodes/__init__.py -> build/lib/seal5/transform/annotate_opcodes 2025-12-13T07:28:30,769 copying seal5/transform/annotate_opcodes/annotate.py -> build/lib/seal5/transform/annotate_opcodes 2025-12-13T07:28:30,770 creating build/lib/seal5/transform/check_pattern_support 2025-12-13T07:28:30,771 copying seal5/transform/check_pattern_support/__init__.py -> build/lib/seal5/transform/check_pattern_support 2025-12-13T07:28:30,771 copying seal5/transform/check_pattern_support/check.py -> build/lib/seal5/transform/check_pattern_support 2025-12-13T07:28:30,772 creating build/lib/seal5/transform/collect_immediate_operands 2025-12-13T07:28:30,773 copying seal5/transform/collect_immediate_operands/__init__.py -> build/lib/seal5/transform/collect_immediate_operands 2025-12-13T07:28:30,773 copying seal5/transform/collect_immediate_operands/collect.py -> build/lib/seal5/transform/collect_immediate_operands 2025-12-13T07:28:30,774 copying seal5/transform/collect_immediate_operands/visitor.py -> build/lib/seal5/transform/collect_immediate_operands 2025-12-13T07:28:30,774 creating build/lib/seal5/transform/collect_operand_types 2025-12-13T07:28:30,776 copying seal5/transform/collect_operand_types/__init__.py -> build/lib/seal5/transform/collect_operand_types 2025-12-13T07:28:30,776 copying seal5/transform/collect_operand_types/collect.py -> build/lib/seal5/transform/collect_operand_types 2025-12-13T07:28:30,777 copying seal5/transform/collect_operand_types/visitor.py -> build/lib/seal5/transform/collect_operand_types 2025-12-13T07:28:30,777 creating build/lib/seal5/transform/collect_raises 2025-12-13T07:28:30,778 copying seal5/transform/collect_raises/__init__.py -> build/lib/seal5/transform/collect_raises 2025-12-13T07:28:30,778 copying seal5/transform/collect_raises/collect.py -> build/lib/seal5/transform/collect_raises 2025-12-13T07:28:30,779 copying seal5/transform/collect_raises/visitor.py -> build/lib/seal5/transform/collect_raises 2025-12-13T07:28:30,780 creating build/lib/seal5/transform/collect_register_operands 2025-12-13T07:28:30,781 copying seal5/transform/collect_register_operands/__init__.py -> build/lib/seal5/transform/collect_register_operands 2025-12-13T07:28:30,782 copying seal5/transform/collect_register_operands/collect.py -> build/lib/seal5/transform/collect_register_operands 2025-12-13T07:28:30,783 copying seal5/transform/collect_register_operands/visitor.py -> build/lib/seal5/transform/collect_register_operands 2025-12-13T07:28:30,783 creating build/lib/seal5/transform/detect_calls 2025-12-13T07:28:30,784 copying seal5/transform/detect_calls/__init__.py -> build/lib/seal5/transform/detect_calls 2025-12-13T07:28:30,785 copying seal5/transform/detect_calls/collect.py -> build/lib/seal5/transform/detect_calls 2025-12-13T07:28:30,786 copying seal5/transform/detect_calls/visitor.py -> build/lib/seal5/transform/detect_calls 2025-12-13T07:28:30,786 creating build/lib/seal5/transform/detect_imm_leafs 2025-12-13T07:28:30,787 copying seal5/transform/detect_imm_leafs/__init__.py -> build/lib/seal5/transform/detect_imm_leafs 2025-12-13T07:28:30,787 copying seal5/transform/detect_imm_leafs/collect.py -> build/lib/seal5/transform/detect_imm_leafs 2025-12-13T07:28:30,788 copying seal5/transform/detect_imm_leafs/visitor.py -> build/lib/seal5/transform/detect_imm_leafs 2025-12-13T07:28:30,789 creating build/lib/seal5/transform/detect_inouts 2025-12-13T07:28:30,790 copying seal5/transform/detect_inouts/__init__.py -> build/lib/seal5/transform/detect_inouts 2025-12-13T07:28:30,790 copying seal5/transform/detect_inouts/collect.py -> build/lib/seal5/transform/detect_inouts 2025-12-13T07:28:30,791 copying seal5/transform/detect_inouts/utils.py -> build/lib/seal5/transform/detect_inouts 2025-12-13T07:28:30,791 copying seal5/transform/detect_inouts/visitor.py -> build/lib/seal5/transform/detect_inouts 2025-12-13T07:28:30,792 creating build/lib/seal5/transform/detect_loops 2025-12-13T07:28:30,793 copying seal5/transform/detect_loops/__init__.py -> build/lib/seal5/transform/detect_loops 2025-12-13T07:28:30,794 copying seal5/transform/detect_loops/collect.py -> build/lib/seal5/transform/detect_loops 2025-12-13T07:28:30,794 copying seal5/transform/detect_loops/visitor.py -> build/lib/seal5/transform/detect_loops 2025-12-13T07:28:30,795 creating build/lib/seal5/transform/detect_registers 2025-12-13T07:28:30,795 copying seal5/transform/detect_registers/__init__.py -> build/lib/seal5/transform/detect_registers 2025-12-13T07:28:30,796 copying seal5/transform/detect_registers/detect.py -> build/lib/seal5/transform/detect_registers 2025-12-13T07:28:30,797 creating build/lib/seal5/transform/detect_side_effects 2025-12-13T07:28:30,798 copying seal5/transform/detect_side_effects/__init__.py -> build/lib/seal5/transform/detect_side_effects 2025-12-13T07:28:30,798 copying seal5/transform/detect_side_effects/collect.py -> build/lib/seal5/transform/detect_side_effects 2025-12-13T07:28:30,799 copying seal5/transform/detect_side_effects/visitor.py -> build/lib/seal5/transform/detect_side_effects 2025-12-13T07:28:30,800 creating build/lib/seal5/transform/drop_unused 2025-12-13T07:28:30,801 copying seal5/transform/drop_unused/__init__.py -> build/lib/seal5/transform/drop_unused 2025-12-13T07:28:30,802 copying seal5/transform/drop_unused/optimizer.py -> build/lib/seal5/transform/drop_unused 2025-12-13T07:28:30,802 copying seal5/transform/drop_unused/track_uses.py -> build/lib/seal5/transform/drop_unused 2025-12-13T07:28:30,803 creating build/lib/seal5/transform/eliminate_mod_rfs 2025-12-13T07:28:30,804 copying seal5/transform/eliminate_mod_rfs/__init__.py -> build/lib/seal5/transform/eliminate_mod_rfs 2025-12-13T07:28:30,804 copying seal5/transform/eliminate_mod_rfs/transform.py -> build/lib/seal5/transform/eliminate_mod_rfs 2025-12-13T07:28:30,805 copying seal5/transform/eliminate_mod_rfs/visitor.py -> build/lib/seal5/transform/eliminate_mod_rfs 2025-12-13T07:28:30,805 creating build/lib/seal5/transform/eliminate_rd_cmp_zero 2025-12-13T07:28:30,806 copying seal5/transform/eliminate_rd_cmp_zero/__init__.py -> build/lib/seal5/transform/eliminate_rd_cmp_zero 2025-12-13T07:28:30,807 copying seal5/transform/eliminate_rd_cmp_zero/transform.py -> build/lib/seal5/transform/eliminate_rd_cmp_zero 2025-12-13T07:28:30,807 copying seal5/transform/eliminate_rd_cmp_zero/visitor.py -> build/lib/seal5/transform/eliminate_rd_cmp_zero 2025-12-13T07:28:30,808 creating build/lib/seal5/transform/explicit_truncations 2025-12-13T07:28:30,809 copying seal5/transform/explicit_truncations/__init__.py -> build/lib/seal5/transform/explicit_truncations 2025-12-13T07:28:30,811 copying seal5/transform/explicit_truncations/transform.py -> build/lib/seal5/transform/explicit_truncations 2025-12-13T07:28:30,814 copying seal5/transform/explicit_truncations/visitor.py -> build/lib/seal5/transform/explicit_truncations 2025-12-13T07:28:30,817 creating build/lib/seal5/transform/filter_model 2025-12-13T07:28:30,818 copying seal5/transform/filter_model/__init__.py -> build/lib/seal5/transform/filter_model 2025-12-13T07:28:30,820 copying seal5/transform/filter_model/filter.py -> build/lib/seal5/transform/filter_model 2025-12-13T07:28:30,823 creating build/lib/seal5/transform/infer_types 2025-12-13T07:28:30,825 copying seal5/transform/infer_types/__init__.py -> build/lib/seal5/transform/infer_types 2025-12-13T07:28:30,828 copying seal5/transform/infer_types/transform.py -> build/lib/seal5/transform/infer_types 2025-12-13T07:28:30,830 copying seal5/transform/infer_types/visitor.py -> build/lib/seal5/transform/infer_types 2025-12-13T07:28:30,833 creating build/lib/seal5/transform/inline_functions 2025-12-13T07:28:30,835 copying seal5/transform/inline_functions/__init__.py -> build/lib/seal5/transform/inline_functions 2025-12-13T07:28:30,837 copying seal5/transform/inline_functions/optimizer.py -> build/lib/seal5/transform/inline_functions 2025-12-13T07:28:30,840 copying seal5/transform/inline_functions/visitor.py -> build/lib/seal5/transform/inline_functions 2025-12-13T07:28:30,843 creating build/lib/seal5/transform/optimize_instructions 2025-12-13T07:28:30,844 copying seal5/transform/optimize_instructions/__init__.py -> build/lib/seal5/transform/optimize_instructions 2025-12-13T07:28:30,847 copying seal5/transform/optimize_instructions/optimizer.py -> build/lib/seal5/transform/optimize_instructions 2025-12-13T07:28:30,849 creating build/lib/seal5/transform/process_settings 2025-12-13T07:28:30,851 copying seal5/transform/process_settings/__init__.py -> build/lib/seal5/transform/process_settings 2025-12-13T07:28:30,853 copying seal5/transform/process_settings/transform.py -> build/lib/seal5/transform/process_settings 2025-12-13T07:28:30,856 creating build/lib/seal5/transform/simplify_trivial_slices 2025-12-13T07:28:30,857 copying seal5/transform/simplify_trivial_slices/__init__.py -> build/lib/seal5/transform/simplify_trivial_slices 2025-12-13T07:28:30,860 copying seal5/transform/simplify_trivial_slices/transform.py -> build/lib/seal5/transform/simplify_trivial_slices 2025-12-13T07:28:30,863 copying seal5/transform/simplify_trivial_slices/visitor.py -> build/lib/seal5/transform/simplify_trivial_slices 2025-12-13T07:28:30,880 installing to build/bdist.linux-armv7l/wheel 2025-12-13T07:28:30,881 running install 2025-12-13T07:28:30,905 running install_lib 2025-12-13T07:28:30,913 creating build/bdist.linux-armv7l/wheel 2025-12-13T07:28:30,915 creating build/bdist.linux-armv7l/wheel/seal5 2025-12-13T07:28:30,917 copying build/lib/seal5/utils.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:30,921 creating build/bdist.linux-armv7l/wheel/seal5/frontends 2025-12-13T07:28:30,923 creating build/bdist.linux-armv7l/wheel/seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,924 copying build/lib/seal5/frontends/coredsl2_seal5/utils.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,927 copying build/lib/seal5/frontends/coredsl2_seal5/importer.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,930 copying build/lib/seal5/frontends/coredsl2_seal5/CoreDSL2.g4 -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,932 copying build/lib/seal5/frontends/coredsl2_seal5/antlr.sh -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,934 copying build/lib/seal5/frontends/coredsl2_seal5/.gitignore -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,937 copying build/lib/seal5/frontends/coredsl2_seal5/parser.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,939 copying build/lib/seal5/frontends/coredsl2_seal5/architecture_model_builder.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,942 copying build/lib/seal5/frontends/coredsl2_seal5/load_order.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,944 copying build/lib/seal5/frontends/coredsl2_seal5/README.md -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,947 copying build/lib/seal5/frontends/coredsl2_seal5/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,949 copying build/lib/seal5/frontends/coredsl2_seal5/behavior_model_builder.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,952 copying build/lib/seal5/frontends/coredsl2_seal5/expr_interpreter.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5 2025-12-13T07:28:30,955 creating build/bdist.linux-armv7l/wheel/seal5/frontends/coredsl2_seal5/parser_gen 2025-12-13T07:28:30,956 copying build/lib/seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Parser.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5/parser_gen 2025-12-13T07:28:30,964 copying build/lib/seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Listener.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5/parser_gen 2025-12-13T07:28:30,967 copying build/lib/seal5/frontends/coredsl2_seal5/parser_gen/.gitignore -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5/parser_gen 2025-12-13T07:28:30,969 copying build/lib/seal5/frontends/coredsl2_seal5/parser_gen/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5/parser_gen 2025-12-13T07:28:30,971 copying build/lib/seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5/parser_gen 2025-12-13T07:28:30,974 copying build/lib/seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Lexer.py -> build/bdist.linux-armv7l/wheel/./seal5/frontends/coredsl2_seal5/parser_gen 2025-12-13T07:28:30,978 creating build/bdist.linux-armv7l/wheel/seal5/cli 2025-12-13T07:28:30,979 copying build/lib/seal5/cli/install.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:30,981 copying build/lib/seal5/cli/setup.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:30,983 copying build/lib/seal5/cli/patch.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:30,985 copying build/lib/seal5/cli/init.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:30,987 copying build/lib/seal5/cli/deploy.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:30,988 copying build/lib/seal5/cli/common.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:30,990 copying build/lib/seal5/cli/export.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:30,992 copying build/lib/seal5/cli/generate.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:30,994 copying build/lib/seal5/cli/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:30,996 copying build/lib/seal5/cli/test.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:30,998 copying build/lib/seal5/cli/load.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:31,000 copying build/lib/seal5/cli/wrapper.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:31,002 copying build/lib/seal5/cli/transform.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:31,004 copying build/lib/seal5/cli/main.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:31,006 copying build/lib/seal5/cli/reset.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:31,007 copying build/lib/seal5/cli/clean.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:31,009 copying build/lib/seal5/cli/build.py -> build/bdist.linux-armv7l/wheel/./seal5/cli 2025-12-13T07:28:31,011 copying build/lib/seal5/model.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,014 copying build/lib/seal5/model_utils.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,016 copying build/lib/seal5/dependencies.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,019 creating build/bdist.linux-armv7l/wheel/seal5/backends 2025-12-13T07:28:31,021 creating build/bdist.linux-armv7l/wheel/seal5/backends/report 2025-12-13T07:28:31,022 creating build/bdist.linux-armv7l/wheel/seal5/backends/report/properties 2025-12-13T07:28:31,024 copying build/lib/seal5/backends/report/properties/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/properties 2025-12-13T07:28:31,026 copying build/lib/seal5/backends/report/properties/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/properties 2025-12-13T07:28:31,029 creating build/bdist.linux-armv7l/wheel/seal5/backends/report/times 2025-12-13T07:28:31,029 copying build/lib/seal5/backends/report/times/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/times 2025-12-13T07:28:31,032 copying build/lib/seal5/backends/report/times/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/times 2025-12-13T07:28:31,035 creating build/bdist.linux-armv7l/wheel/seal5/backends/report/diff 2025-12-13T07:28:31,036 copying build/lib/seal5/backends/report/diff/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/diff 2025-12-13T07:28:31,038 copying build/lib/seal5/backends/report/diff/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/diff 2025-12-13T07:28:31,040 copying build/lib/seal5/backends/report/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report 2025-12-13T07:28:31,042 creating build/bdist.linux-armv7l/wheel/seal5/backends/report/pattern_gen 2025-12-13T07:28:31,043 copying build/lib/seal5/backends/report/pattern_gen/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/pattern_gen 2025-12-13T07:28:31,046 copying build/lib/seal5/backends/report/pattern_gen/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/pattern_gen 2025-12-13T07:28:31,048 creating build/bdist.linux-armv7l/wheel/seal5/backends/report/test_results 2025-12-13T07:28:31,049 copying build/lib/seal5/backends/report/test_results/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/test_results 2025-12-13T07:28:31,052 copying build/lib/seal5/backends/report/test_results/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/test_results 2025-12-13T07:28:31,055 creating build/bdist.linux-armv7l/wheel/seal5/backends/report/status 2025-12-13T07:28:31,056 copying build/lib/seal5/backends/report/status/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/status 2025-12-13T07:28:31,058 copying build/lib/seal5/backends/report/status/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/report/status 2025-12-13T07:28:31,061 creating build/bdist.linux-armv7l/wheel/seal5/backends/coredsl2 2025-12-13T07:28:31,062 copying build/lib/seal5/backends/coredsl2/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/coredsl2 2025-12-13T07:28:31,064 copying build/lib/seal5/backends/coredsl2/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/coredsl2 2025-12-13T07:28:31,067 copying build/lib/seal5/backends/coredsl2/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/coredsl2 2025-12-13T07:28:31,070 creating build/bdist.linux-armv7l/wheel/seal5/backends/viewer_seal5 2025-12-13T07:28:31,071 copying build/lib/seal5/backends/viewer_seal5/utils.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/viewer_seal5 2025-12-13T07:28:31,073 copying build/lib/seal5/backends/viewer_seal5/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/viewer_seal5 2025-12-13T07:28:31,075 copying build/lib/seal5/backends/viewer_seal5/viewer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/viewer_seal5 2025-12-13T07:28:31,078 copying build/lib/seal5/backends/viewer_seal5/treegen.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/viewer_seal5 2025-12-13T07:28:31,081 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_register_info 2025-12-13T07:28:31,082 copying build/lib/seal5/backends/riscv_register_info/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_register_info 2025-12-13T07:28:31,085 copying build/lib/seal5/backends/riscv_register_info/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_register_info 2025-12-13T07:28:31,088 creating build/bdist.linux-armv7l/wheel/seal5/backends/llvmir 2025-12-13T07:28:31,089 copying build/lib/seal5/backends/llvmir/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/llvmir 2025-12-13T07:28:31,092 copying build/lib/seal5/backends/llvmir/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/llvmir 2025-12-13T07:28:31,095 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_isa_info 2025-12-13T07:28:31,096 copying build/lib/seal5/backends/riscv_isa_info/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_isa_info 2025-12-13T07:28:31,099 copying build/lib/seal5/backends/riscv_isa_info/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_isa_info 2025-12-13T07:28:31,102 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_features 2025-12-13T07:28:31,104 copying build/lib/seal5/backends/riscv_features/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features 2025-12-13T07:28:31,107 copying build/lib/seal5/backends/riscv_features/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features 2025-12-13T07:28:31,110 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_features/templates 2025-12-13T07:28:31,111 copying build/lib/seal5/backends/riscv_features/templates/riscv_features_experimental_new.mako -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features/templates 2025-12-13T07:28:31,114 copying build/lib/seal5/backends/riscv_features/templates/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features/templates 2025-12-13T07:28:31,116 copying build/lib/seal5/backends/riscv_features/templates/riscv_features_new.mako -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features/templates 2025-12-13T07:28:31,119 copying build/lib/seal5/backends/riscv_features/templates/riscv_features.mako -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features/templates 2025-12-13T07:28:31,121 copying build/lib/seal5/backends/riscv_features/templates/test_riscv_attributes.mako -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features/templates 2025-12-13T07:28:31,124 copying build/lib/seal5/backends/riscv_features/templates/riscv_features_experimental_new_slim.mako -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features/templates 2025-12-13T07:28:31,126 copying build/lib/seal5/backends/riscv_features/templates/riscv_features_new_slim.mako -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_features/templates 2025-12-13T07:28:31,128 copying build/lib/seal5/backends/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends 2025-12-13T07:28:31,131 creating build/bdist.linux-armv7l/wheel/seal5/backends/yaml 2025-12-13T07:28:31,132 copying build/lib/seal5/backends/yaml/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/yaml 2025-12-13T07:28:31,135 copying build/lib/seal5/backends/yaml/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/yaml 2025-12-13T07:28:31,138 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_intrinsics 2025-12-13T07:28:31,139 copying build/lib/seal5/backends/riscv_intrinsics/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_intrinsics 2025-12-13T07:28:31,142 copying build/lib/seal5/backends/riscv_intrinsics/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_intrinsics 2025-12-13T07:28:31,145 creating build/bdist.linux-armv7l/wheel/seal5/backends/patterngen 2025-12-13T07:28:31,146 copying build/lib/seal5/backends/patterngen/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/patterngen 2025-12-13T07:28:31,149 copying build/lib/seal5/backends/patterngen/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/patterngen 2025-12-13T07:28:31,152 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_field_types 2025-12-13T07:28:31,154 copying build/lib/seal5/backends/riscv_field_types/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_field_types 2025-12-13T07:28:31,156 copying build/lib/seal5/backends/riscv_field_types/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_field_types 2025-12-13T07:28:31,160 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_gisel_legalizer 2025-12-13T07:28:31,161 copying build/lib/seal5/backends/riscv_gisel_legalizer/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_gisel_legalizer 2025-12-13T07:28:31,164 copying build/lib/seal5/backends/riscv_gisel_legalizer/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_gisel_legalizer 2025-12-13T07:28:31,167 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_instr_info 2025-12-13T07:28:31,168 copying build/lib/seal5/backends/riscv_instr_info/writer.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_instr_info 2025-12-13T07:28:31,171 copying build/lib/seal5/backends/riscv_instr_info/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_instr_info 2025-12-13T07:28:31,174 creating build/bdist.linux-armv7l/wheel/seal5/backends/riscv_instr_info/templates 2025-12-13T07:28:31,176 copying build/lib/seal5/backends/riscv_instr_info/templates/instr_tablegen.mako -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_instr_info/templates 2025-12-13T07:28:31,178 copying build/lib/seal5/backends/riscv_instr_info/templates/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/backends/riscv_instr_info/templates 2025-12-13T07:28:31,180 copying build/lib/seal5/flow.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,183 copying build/lib/seal5/logging.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,185 copying build/lib/seal5/testgen_utils.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,187 copying build/lib/seal5/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,189 copying build/lib/seal5/riscv_utils.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,192 copying build/lib/seal5/settings.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,194 copying build/lib/seal5/pass_list.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,198 copying build/lib/seal5/index.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,200 copying build/lib/seal5/wrapper.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,202 copying build/lib/seal5/types.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,205 creating build/bdist.linux-armv7l/wheel/seal5/transform 2025-12-13T07:28:31,207 creating build/bdist.linux-armv7l/wheel/seal5/transform/infer_types 2025-12-13T07:28:31,208 copying build/lib/seal5/transform/infer_types/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/infer_types 2025-12-13T07:28:31,210 copying build/lib/seal5/transform/infer_types/transform.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/infer_types 2025-12-13T07:28:31,212 copying build/lib/seal5/transform/infer_types/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/infer_types 2025-12-13T07:28:31,215 creating build/bdist.linux-armv7l/wheel/seal5/transform/filter_model 2025-12-13T07:28:31,216 copying build/lib/seal5/transform/filter_model/filter.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/filter_model 2025-12-13T07:28:31,218 copying build/lib/seal5/transform/filter_model/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/filter_model 2025-12-13T07:28:31,221 creating build/bdist.linux-armv7l/wheel/seal5/transform/collect_operand_types 2025-12-13T07:28:31,222 copying build/lib/seal5/transform/collect_operand_types/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_operand_types 2025-12-13T07:28:31,224 copying build/lib/seal5/transform/collect_operand_types/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_operand_types 2025-12-13T07:28:31,226 copying build/lib/seal5/transform/collect_operand_types/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_operand_types 2025-12-13T07:28:31,229 creating build/bdist.linux-armv7l/wheel/seal5/transform/check_pattern_support 2025-12-13T07:28:31,230 copying build/lib/seal5/transform/check_pattern_support/check.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/check_pattern_support 2025-12-13T07:28:31,232 copying build/lib/seal5/transform/check_pattern_support/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/check_pattern_support 2025-12-13T07:28:31,235 creating build/bdist.linux-armv7l/wheel/seal5/transform/collect_register_operands 2025-12-13T07:28:31,236 copying build/lib/seal5/transform/collect_register_operands/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_register_operands 2025-12-13T07:28:31,238 copying build/lib/seal5/transform/collect_register_operands/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_register_operands 2025-12-13T07:28:31,240 copying build/lib/seal5/transform/collect_register_operands/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_register_operands 2025-12-13T07:28:31,243 creating build/bdist.linux-armv7l/wheel/seal5/transform/eliminate_rd_cmp_zero 2025-12-13T07:28:31,244 copying build/lib/seal5/transform/eliminate_rd_cmp_zero/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/eliminate_rd_cmp_zero 2025-12-13T07:28:31,246 copying build/lib/seal5/transform/eliminate_rd_cmp_zero/transform.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/eliminate_rd_cmp_zero 2025-12-13T07:28:31,248 copying build/lib/seal5/transform/eliminate_rd_cmp_zero/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/eliminate_rd_cmp_zero 2025-12-13T07:28:31,250 creating build/bdist.linux-armv7l/wheel/seal5/transform/simplify_trivial_slices 2025-12-13T07:28:31,252 copying build/lib/seal5/transform/simplify_trivial_slices/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/simplify_trivial_slices 2025-12-13T07:28:31,254 copying build/lib/seal5/transform/simplify_trivial_slices/transform.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/simplify_trivial_slices 2025-12-13T07:28:31,256 copying build/lib/seal5/transform/simplify_trivial_slices/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/simplify_trivial_slices 2025-12-13T07:28:31,258 creating build/bdist.linux-armv7l/wheel/seal5/transform/inline_functions 2025-12-13T07:28:31,260 copying build/lib/seal5/transform/inline_functions/optimizer.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/inline_functions 2025-12-13T07:28:31,262 copying build/lib/seal5/transform/inline_functions/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/inline_functions 2025-12-13T07:28:31,263 copying build/lib/seal5/transform/inline_functions/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/inline_functions 2025-12-13T07:28:31,266 creating build/bdist.linux-armv7l/wheel/seal5/transform/detect_registers 2025-12-13T07:28:31,267 copying build/lib/seal5/transform/detect_registers/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_registers 2025-12-13T07:28:31,269 copying build/lib/seal5/transform/detect_registers/detect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_registers 2025-12-13T07:28:31,272 creating build/bdist.linux-armv7l/wheel/seal5/transform/detect_inouts 2025-12-13T07:28:31,273 copying build/lib/seal5/transform/detect_inouts/utils.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_inouts 2025-12-13T07:28:31,275 copying build/lib/seal5/transform/detect_inouts/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_inouts 2025-12-13T07:28:31,277 copying build/lib/seal5/transform/detect_inouts/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_inouts 2025-12-13T07:28:31,279 copying build/lib/seal5/transform/detect_inouts/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_inouts 2025-12-13T07:28:31,282 creating build/bdist.linux-armv7l/wheel/seal5/transform/drop_unused 2025-12-13T07:28:31,283 copying build/lib/seal5/transform/drop_unused/optimizer.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/drop_unused 2025-12-13T07:28:31,285 copying build/lib/seal5/transform/drop_unused/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/drop_unused 2025-12-13T07:28:31,287 copying build/lib/seal5/transform/drop_unused/track_uses.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/drop_unused 2025-12-13T07:28:31,289 copying build/lib/seal5/transform/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform 2025-12-13T07:28:31,291 creating build/bdist.linux-armv7l/wheel/seal5/transform/eliminate_mod_rfs 2025-12-13T07:28:31,293 copying build/lib/seal5/transform/eliminate_mod_rfs/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/eliminate_mod_rfs 2025-12-13T07:28:31,295 copying build/lib/seal5/transform/eliminate_mod_rfs/transform.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/eliminate_mod_rfs 2025-12-13T07:28:31,297 copying build/lib/seal5/transform/eliminate_mod_rfs/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/eliminate_mod_rfs 2025-12-13T07:28:31,299 creating build/bdist.linux-armv7l/wheel/seal5/transform/detect_imm_leafs 2025-12-13T07:28:31,300 copying build/lib/seal5/transform/detect_imm_leafs/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_imm_leafs 2025-12-13T07:28:31,302 copying build/lib/seal5/transform/detect_imm_leafs/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_imm_leafs 2025-12-13T07:28:31,304 copying build/lib/seal5/transform/detect_imm_leafs/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_imm_leafs 2025-12-13T07:28:31,307 creating build/bdist.linux-armv7l/wheel/seal5/transform/detect_side_effects 2025-12-13T07:28:31,308 copying build/lib/seal5/transform/detect_side_effects/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_side_effects 2025-12-13T07:28:31,311 copying build/lib/seal5/transform/detect_side_effects/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_side_effects 2025-12-13T07:28:31,313 copying build/lib/seal5/transform/detect_side_effects/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_side_effects 2025-12-13T07:28:31,316 creating build/bdist.linux-armv7l/wheel/seal5/transform/collect_immediate_operands 2025-12-13T07:28:31,317 copying build/lib/seal5/transform/collect_immediate_operands/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_immediate_operands 2025-12-13T07:28:31,319 copying build/lib/seal5/transform/collect_immediate_operands/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_immediate_operands 2025-12-13T07:28:31,320 copying build/lib/seal5/transform/collect_immediate_operands/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_immediate_operands 2025-12-13T07:28:31,323 creating build/bdist.linux-armv7l/wheel/seal5/transform/detect_calls 2025-12-13T07:28:31,324 copying build/lib/seal5/transform/detect_calls/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_calls 2025-12-13T07:28:31,326 copying build/lib/seal5/transform/detect_calls/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_calls 2025-12-13T07:28:31,328 copying build/lib/seal5/transform/detect_calls/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_calls 2025-12-13T07:28:31,331 creating build/bdist.linux-armv7l/wheel/seal5/transform/detect_loops 2025-12-13T07:28:31,332 copying build/lib/seal5/transform/detect_loops/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_loops 2025-12-13T07:28:31,334 copying build/lib/seal5/transform/detect_loops/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_loops 2025-12-13T07:28:31,336 copying build/lib/seal5/transform/detect_loops/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/detect_loops 2025-12-13T07:28:31,338 creating build/bdist.linux-armv7l/wheel/seal5/transform/optimize_instructions 2025-12-13T07:28:31,339 copying build/lib/seal5/transform/optimize_instructions/optimizer.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/optimize_instructions 2025-12-13T07:28:31,342 copying build/lib/seal5/transform/optimize_instructions/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/optimize_instructions 2025-12-13T07:28:31,344 creating build/bdist.linux-armv7l/wheel/seal5/transform/collect_raises 2025-12-13T07:28:31,345 copying build/lib/seal5/transform/collect_raises/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_raises 2025-12-13T07:28:31,347 copying build/lib/seal5/transform/collect_raises/collect.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_raises 2025-12-13T07:28:31,349 copying build/lib/seal5/transform/collect_raises/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/collect_raises 2025-12-13T07:28:31,352 creating build/bdist.linux-armv7l/wheel/seal5/transform/process_settings 2025-12-13T07:28:31,353 copying build/lib/seal5/transform/process_settings/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/process_settings 2025-12-13T07:28:31,355 copying build/lib/seal5/transform/process_settings/transform.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/process_settings 2025-12-13T07:28:31,358 creating build/bdist.linux-armv7l/wheel/seal5/transform/explicit_truncations 2025-12-13T07:28:31,359 copying build/lib/seal5/transform/explicit_truncations/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/explicit_truncations 2025-12-13T07:28:31,361 copying build/lib/seal5/transform/explicit_truncations/transform.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/explicit_truncations 2025-12-13T07:28:31,363 copying build/lib/seal5/transform/explicit_truncations/visitor.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/explicit_truncations 2025-12-13T07:28:31,365 copying build/lib/seal5/transform/converter.py -> build/bdist.linux-armv7l/wheel/./seal5/transform 2025-12-13T07:28:31,368 creating build/bdist.linux-armv7l/wheel/seal5/transform/annotate_opcodes 2025-12-13T07:28:31,369 copying build/lib/seal5/transform/annotate_opcodes/annotate.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/annotate_opcodes 2025-12-13T07:28:31,371 copying build/lib/seal5/transform/annotate_opcodes/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/transform/annotate_opcodes 2025-12-13T07:28:31,373 copying build/lib/seal5/version.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,375 creating build/bdist.linux-armv7l/wheel/seal5/resources 2025-12-13T07:28:31,376 copying build/lib/seal5/resources/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/resources 2025-12-13T07:28:31,378 copying build/lib/seal5/resources/resources.py -> build/bdist.linux-armv7l/wheel/./seal5/resources 2025-12-13T07:28:31,381 creating build/bdist.linux-armv7l/wheel/seal5/resources/patches 2025-12-13T07:28:31,382 creating build/bdist.linux-armv7l/wheel/seal5/resources/patches/llvm 2025-12-13T07:28:31,383 copying build/lib/seal5/resources/patches/llvm/legalizer_fix_1.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-13T07:28:31,385 copying build/lib/seal5/resources/patches/llvm/insert_markers_llvm18.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-13T07:28:31,388 copying build/lib/seal5/resources/patches/llvm/github_ci.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-13T07:28:31,389 copying build/lib/seal5/resources/patches/llvm/simd_gpr32v.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-13T07:28:31,391 copying build/lib/seal5/resources/patches/llvm/insert_markers_llvm19.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-13T07:28:31,394 copying build/lib/seal5/resources/patches/llvm/legalizer_fix_2.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-13T07:28:31,396 copying build/lib/seal5/resources/patches/llvm/regclass_gpr32v.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-13T07:28:31,398 copying build/lib/seal5/resources/patches/llvm/insert_markers_llvm17.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-13T07:28:31,400 copying build/lib/seal5/resources/patches/llvm/gitignore.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-13T07:28:31,402 copying build/lib/seal5/resources/patches/llvm/legalizer_split.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-13T07:28:31,404 copying build/lib/seal5/resources/patches/llvm/gitlab_ci.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-13T07:28:31,406 copying build/lib/seal5/resources/patches/llvm/insert_markers_llvm20.patch -> build/bdist.linux-armv7l/wheel/./seal5/resources/patches/llvm 2025-12-13T07:28:31,408 copying build/lib/seal5/resources/lit.cfg.py -> build/bdist.linux-armv7l/wheel/./seal5/resources 2025-12-13T07:28:31,410 copying build/lib/seal5/passes.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,412 copying build/lib/seal5/metrics.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,415 creating build/bdist.linux-armv7l/wheel/seal5/tools 2025-12-13T07:28:31,416 copying build/lib/seal5/tools/llvm.py -> build/bdist.linux-armv7l/wheel/./seal5/tools 2025-12-13T07:28:31,418 copying build/lib/seal5/tools/git.py -> build/bdist.linux-armv7l/wheel/./seal5/tools 2025-12-13T07:28:31,420 copying build/lib/seal5/tools/cdsl2llvm.py -> build/bdist.linux-armv7l/wheel/./seal5/tools 2025-12-13T07:28:31,423 copying build/lib/seal5/tools/__init__.py -> build/bdist.linux-armv7l/wheel/./seal5/tools 2025-12-13T07:28:31,425 copying build/lib/seal5/tools/cmake.py -> build/bdist.linux-armv7l/wheel/./seal5/tools 2025-12-13T07:28:31,427 copying build/lib/seal5/tools/inject_patches.py -> build/bdist.linux-armv7l/wheel/./seal5/tools 2025-12-13T07:28:31,429 copying build/lib/seal5/tools/m2isar.py -> build/bdist.linux-armv7l/wheel/./seal5/tools 2025-12-13T07:28:31,431 copying build/lib/seal5/build_cache.py -> build/bdist.linux-armv7l/wheel/./seal5 2025-12-13T07:28:31,433 running install_egg_info 2025-12-13T07:28:31,440 Copying seal5.egg-info to build/bdist.linux-armv7l/wheel/./seal5-0.3.2-py3.11.egg-info 2025-12-13T07:28:31,453 running install_scripts 2025-12-13T07:28:31,467 creating build/bdist.linux-armv7l/wheel/seal5-0.3.2.dist-info/WHEEL 2025-12-13T07:28:31,470 creating '/tmp/pip-wheel-0e6ektnj/.tmp-t79g6gcr/seal5-0.3.2-py3-none-any.whl' and adding 'build/bdist.linux-armv7l/wheel' to it 2025-12-13T07:28:31,473 adding 'seal5/__init__.py' 2025-12-13T07:28:31,475 adding 'seal5/build_cache.py' 2025-12-13T07:28:31,476 adding 'seal5/dependencies.py' 2025-12-13T07:28:31,482 adding 'seal5/flow.py' 2025-12-13T07:28:31,484 adding 'seal5/index.py' 2025-12-13T07:28:31,486 adding 'seal5/logging.py' 2025-12-13T07:28:31,487 adding 'seal5/metrics.py' 2025-12-13T07:28:31,490 adding 'seal5/model.py' 2025-12-13T07:28:31,492 adding 'seal5/model_utils.py' 2025-12-13T07:28:31,497 adding 'seal5/pass_list.py' 2025-12-13T07:28:31,499 adding 'seal5/passes.py' 2025-12-13T07:28:31,501 adding 'seal5/riscv_utils.py' 2025-12-13T07:28:31,504 adding 'seal5/settings.py' 2025-12-13T07:28:31,505 adding 'seal5/testgen_utils.py' 2025-12-13T07:28:31,506 adding 'seal5/types.py' 2025-12-13T07:28:31,508 adding 'seal5/utils.py' 2025-12-13T07:28:31,509 adding 'seal5/version.py' 2025-12-13T07:28:31,511 adding 'seal5/wrapper.py' 2025-12-13T07:28:31,513 adding 'seal5/backends/__init__.py' 2025-12-13T07:28:31,515 adding 'seal5/backends/coredsl2/__init__.py' 2025-12-13T07:28:31,517 adding 'seal5/backends/coredsl2/visitor.py' 2025-12-13T07:28:31,519 adding 'seal5/backends/coredsl2/writer.py' 2025-12-13T07:28:31,521 adding 'seal5/backends/llvmir/__init__.py' 2025-12-13T07:28:31,522 adding 'seal5/backends/llvmir/writer.py' 2025-12-13T07:28:31,524 adding 'seal5/backends/patterngen/__init__.py' 2025-12-13T07:28:31,526 adding 'seal5/backends/patterngen/writer.py' 2025-12-13T07:28:31,528 adding 'seal5/backends/report/__init__.py' 2025-12-13T07:28:31,530 adding 'seal5/backends/report/diff/__init__.py' 2025-12-13T07:28:31,532 adding 'seal5/backends/report/diff/writer.py' 2025-12-13T07:28:31,534 adding 'seal5/backends/report/pattern_gen/__init__.py' 2025-12-13T07:28:31,535 adding 'seal5/backends/report/pattern_gen/writer.py' 2025-12-13T07:28:31,537 adding 'seal5/backends/report/properties/__init__.py' 2025-12-13T07:28:31,539 adding 'seal5/backends/report/properties/writer.py' 2025-12-13T07:28:31,540 adding 'seal5/backends/report/status/__init__.py' 2025-12-13T07:28:31,542 adding 'seal5/backends/report/status/writer.py' 2025-12-13T07:28:31,544 adding 'seal5/backends/report/test_results/__init__.py' 2025-12-13T07:28:31,546 adding 'seal5/backends/report/test_results/writer.py' 2025-12-13T07:28:31,548 adding 'seal5/backends/report/times/__init__.py' 2025-12-13T07:28:31,550 adding 'seal5/backends/report/times/writer.py' 2025-12-13T07:28:31,552 adding 'seal5/backends/riscv_features/__init__.py' 2025-12-13T07:28:31,554 adding 'seal5/backends/riscv_features/writer.py' 2025-12-13T07:28:31,556 adding 'seal5/backends/riscv_features/templates/__init__.py' 2025-12-13T07:28:31,557 adding 'seal5/backends/riscv_features/templates/riscv_features.mako' 2025-12-13T07:28:31,558 adding 'seal5/backends/riscv_features/templates/riscv_features_experimental_new.mako' 2025-12-13T07:28:31,559 adding 'seal5/backends/riscv_features/templates/riscv_features_experimental_new_slim.mako' 2025-12-13T07:28:31,560 adding 'seal5/backends/riscv_features/templates/riscv_features_new.mako' 2025-12-13T07:28:31,562 adding 'seal5/backends/riscv_features/templates/riscv_features_new_slim.mako' 2025-12-13T07:28:31,563 adding 'seal5/backends/riscv_features/templates/test_riscv_attributes.mako' 2025-12-13T07:28:31,565 adding 'seal5/backends/riscv_field_types/__init__.py' 2025-12-13T07:28:31,567 adding 'seal5/backends/riscv_field_types/writer.py' 2025-12-13T07:28:31,568 adding 'seal5/backends/riscv_gisel_legalizer/__init__.py' 2025-12-13T07:28:31,570 adding 'seal5/backends/riscv_gisel_legalizer/writer.py' 2025-12-13T07:28:31,572 adding 'seal5/backends/riscv_instr_info/__init__.py' 2025-12-13T07:28:31,574 adding 'seal5/backends/riscv_instr_info/writer.py' 2025-12-13T07:28:31,576 adding 'seal5/backends/riscv_instr_info/templates/__init__.py' 2025-12-13T07:28:31,577 adding 'seal5/backends/riscv_instr_info/templates/instr_tablegen.mako' 2025-12-13T07:28:31,579 adding 'seal5/backends/riscv_intrinsics/__init__.py' 2025-12-13T07:28:31,581 adding 'seal5/backends/riscv_intrinsics/writer.py' 2025-12-13T07:28:31,583 adding 'seal5/backends/riscv_isa_info/__init__.py' 2025-12-13T07:28:31,584 adding 'seal5/backends/riscv_isa_info/writer.py' 2025-12-13T07:28:31,586 adding 'seal5/backends/riscv_register_info/__init__.py' 2025-12-13T07:28:31,587 adding 'seal5/backends/riscv_register_info/writer.py' 2025-12-13T07:28:31,589 adding 'seal5/backends/viewer_seal5/__init__.py' 2025-12-13T07:28:31,590 adding 'seal5/backends/viewer_seal5/treegen.py' 2025-12-13T07:28:31,592 adding 'seal5/backends/viewer_seal5/utils.py' 2025-12-13T07:28:31,594 adding 'seal5/backends/viewer_seal5/viewer.py' 2025-12-13T07:28:31,596 adding 'seal5/backends/yaml/__init__.py' 2025-12-13T07:28:31,597 adding 'seal5/backends/yaml/writer.py' 2025-12-13T07:28:31,599 adding 'seal5/cli/__init__.py' 2025-12-13T07:28:31,600 adding 'seal5/cli/build.py' 2025-12-13T07:28:31,602 adding 'seal5/cli/clean.py' 2025-12-13T07:28:31,603 adding 'seal5/cli/common.py' 2025-12-13T07:28:31,604 adding 'seal5/cli/deploy.py' 2025-12-13T07:28:31,606 adding 'seal5/cli/export.py' 2025-12-13T07:28:31,607 adding 'seal5/cli/generate.py' 2025-12-13T07:28:31,608 adding 'seal5/cli/init.py' 2025-12-13T07:28:31,610 adding 'seal5/cli/install.py' 2025-12-13T07:28:31,611 adding 'seal5/cli/load.py' 2025-12-13T07:28:31,612 adding 'seal5/cli/main.py' 2025-12-13T07:28:31,614 adding 'seal5/cli/patch.py' 2025-12-13T07:28:31,615 adding 'seal5/cli/reset.py' 2025-12-13T07:28:31,616 adding 'seal5/cli/setup.py' 2025-12-13T07:28:31,618 adding 'seal5/cli/test.py' 2025-12-13T07:28:31,619 adding 'seal5/cli/transform.py' 2025-12-13T07:28:31,620 adding 'seal5/cli/wrapper.py' 2025-12-13T07:28:31,622 adding 'seal5/frontends/coredsl2_seal5/.gitignore' 2025-12-13T07:28:31,624 adding 'seal5/frontends/coredsl2_seal5/CoreDSL2.g4' 2025-12-13T07:28:31,626 adding 'seal5/frontends/coredsl2_seal5/README.md' 2025-12-13T07:28:31,627 adding 'seal5/frontends/coredsl2_seal5/__init__.py' 2025-12-13T07:28:31,628 adding 'seal5/frontends/coredsl2_seal5/antlr.sh' 2025-12-13T07:28:31,631 adding 'seal5/frontends/coredsl2_seal5/architecture_model_builder.py' 2025-12-13T07:28:31,633 adding 'seal5/frontends/coredsl2_seal5/behavior_model_builder.py' 2025-12-13T07:28:31,635 adding 'seal5/frontends/coredsl2_seal5/expr_interpreter.py' 2025-12-13T07:28:31,636 adding 'seal5/frontends/coredsl2_seal5/importer.py' 2025-12-13T07:28:31,637 adding 'seal5/frontends/coredsl2_seal5/load_order.py' 2025-12-13T07:28:31,639 adding 'seal5/frontends/coredsl2_seal5/parser.py' 2025-12-13T07:28:31,641 adding 'seal5/frontends/coredsl2_seal5/utils.py' 2025-12-13T07:28:31,642 adding 'seal5/frontends/coredsl2_seal5/parser_gen/.gitignore' 2025-12-13T07:28:31,647 adding 'seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Lexer.py' 2025-12-13T07:28:31,650 adding 'seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Listener.py' 2025-12-13T07:28:31,666 adding 'seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Parser.py' 2025-12-13T07:28:31,669 adding 'seal5/frontends/coredsl2_seal5/parser_gen/CoreDSL2Visitor.py' 2025-12-13T07:28:31,671 adding 'seal5/frontends/coredsl2_seal5/parser_gen/__init__.py' 2025-12-13T07:28:31,673 adding 'seal5/resources/__init__.py' 2025-12-13T07:28:31,674 adding 'seal5/resources/lit.cfg.py' 2025-12-13T07:28:31,675 adding 'seal5/resources/resources.py' 2025-12-13T07:28:31,678 adding 'seal5/resources/patches/llvm/github_ci.patch' 2025-12-13T07:28:31,679 adding 'seal5/resources/patches/llvm/gitignore.patch' 2025-12-13T07:28:31,680 adding 'seal5/resources/patches/llvm/gitlab_ci.patch' 2025-12-13T07:28:31,682 adding 'seal5/resources/patches/llvm/insert_markers_llvm17.patch' 2025-12-13T07:28:31,684 adding 'seal5/resources/patches/llvm/insert_markers_llvm18.patch' 2025-12-13T07:28:31,685 adding 'seal5/resources/patches/llvm/insert_markers_llvm19.patch' 2025-12-13T07:28:31,687 adding 'seal5/resources/patches/llvm/insert_markers_llvm20.patch' 2025-12-13T07:28:31,688 adding 'seal5/resources/patches/llvm/legalizer_fix_1.patch' 2025-12-13T07:28:31,689 adding 'seal5/resources/patches/llvm/legalizer_fix_2.patch' 2025-12-13T07:28:31,691 adding 'seal5/resources/patches/llvm/legalizer_split.patch' 2025-12-13T07:28:31,692 adding 'seal5/resources/patches/llvm/regclass_gpr32v.patch' 2025-12-13T07:28:31,694 adding 'seal5/resources/patches/llvm/simd_gpr32v.patch' 2025-12-13T07:28:31,696 adding 'seal5/tools/__init__.py' 2025-12-13T07:28:31,697 adding 'seal5/tools/cdsl2llvm.py' 2025-12-13T07:28:31,699 adding 'seal5/tools/cmake.py' 2025-12-13T07:28:31,700 adding 'seal5/tools/git.py' 2025-12-13T07:28:31,702 adding 'seal5/tools/inject_patches.py' 2025-12-13T07:28:31,704 adding 'seal5/tools/llvm.py' 2025-12-13T07:28:31,705 adding 'seal5/tools/m2isar.py' 2025-12-13T07:28:31,707 adding 'seal5/transform/__init__.py' 2025-12-13T07:28:31,708 adding 'seal5/transform/converter.py' 2025-12-13T07:28:31,710 adding 'seal5/transform/annotate_opcodes/__init__.py' 2025-12-13T07:28:31,712 adding 'seal5/transform/annotate_opcodes/annotate.py' 2025-12-13T07:28:31,714 adding 'seal5/transform/check_pattern_support/__init__.py' 2025-12-13T07:28:31,715 adding 'seal5/transform/check_pattern_support/check.py' 2025-12-13T07:28:31,717 adding 'seal5/transform/collect_immediate_operands/__init__.py' 2025-12-13T07:28:31,718 adding 'seal5/transform/collect_immediate_operands/collect.py' 2025-12-13T07:28:31,720 adding 'seal5/transform/collect_immediate_operands/visitor.py' 2025-12-13T07:28:31,722 adding 'seal5/transform/collect_operand_types/__init__.py' 2025-12-13T07:28:31,723 adding 'seal5/transform/collect_operand_types/collect.py' 2025-12-13T07:28:31,725 adding 'seal5/transform/collect_operand_types/visitor.py' 2025-12-13T07:28:31,727 adding 'seal5/transform/collect_raises/__init__.py' 2025-12-13T07:28:31,728 adding 'seal5/transform/collect_raises/collect.py' 2025-12-13T07:28:31,730 adding 'seal5/transform/collect_raises/visitor.py' 2025-12-13T07:28:31,732 adding 'seal5/transform/collect_register_operands/__init__.py' 2025-12-13T07:28:31,733 adding 'seal5/transform/collect_register_operands/collect.py' 2025-12-13T07:28:31,735 adding 'seal5/transform/collect_register_operands/visitor.py' 2025-12-13T07:28:31,736 adding 'seal5/transform/detect_calls/__init__.py' 2025-12-13T07:28:31,738 adding 'seal5/transform/detect_calls/collect.py' 2025-12-13T07:28:31,739 adding 'seal5/transform/detect_calls/visitor.py' 2025-12-13T07:28:31,741 adding 'seal5/transform/detect_imm_leafs/__init__.py' 2025-12-13T07:28:31,743 adding 'seal5/transform/detect_imm_leafs/collect.py' 2025-12-13T07:28:31,744 adding 'seal5/transform/detect_imm_leafs/visitor.py' 2025-12-13T07:28:31,746 adding 'seal5/transform/detect_inouts/__init__.py' 2025-12-13T07:28:31,748 adding 'seal5/transform/detect_inouts/collect.py' 2025-12-13T07:28:31,749 adding 'seal5/transform/detect_inouts/utils.py' 2025-12-13T07:28:31,750 adding 'seal5/transform/detect_inouts/visitor.py' 2025-12-13T07:28:31,752 adding 'seal5/transform/detect_loops/__init__.py' 2025-12-13T07:28:31,754 adding 'seal5/transform/detect_loops/collect.py' 2025-12-13T07:28:31,755 adding 'seal5/transform/detect_loops/visitor.py' 2025-12-13T07:28:31,757 adding 'seal5/transform/detect_registers/__init__.py' 2025-12-13T07:28:31,759 adding 'seal5/transform/detect_registers/detect.py' 2025-12-13T07:28:31,760 adding 'seal5/transform/detect_side_effects/__init__.py' 2025-12-13T07:28:31,762 adding 'seal5/transform/detect_side_effects/collect.py' 2025-12-13T07:28:31,763 adding 'seal5/transform/detect_side_effects/visitor.py' 2025-12-13T07:28:31,765 adding 'seal5/transform/drop_unused/__init__.py' 2025-12-13T07:28:31,766 adding 'seal5/transform/drop_unused/optimizer.py' 2025-12-13T07:28:31,767 adding 'seal5/transform/drop_unused/track_uses.py' 2025-12-13T07:28:31,769 adding 'seal5/transform/eliminate_mod_rfs/__init__.py' 2025-12-13T07:28:31,770 adding 'seal5/transform/eliminate_mod_rfs/transform.py' 2025-12-13T07:28:31,772 adding 'seal5/transform/eliminate_mod_rfs/visitor.py' 2025-12-13T07:28:31,773 adding 'seal5/transform/eliminate_rd_cmp_zero/__init__.py' 2025-12-13T07:28:31,775 adding 'seal5/transform/eliminate_rd_cmp_zero/transform.py' 2025-12-13T07:28:31,776 adding 'seal5/transform/eliminate_rd_cmp_zero/visitor.py' 2025-12-13T07:28:31,778 adding 'seal5/transform/explicit_truncations/__init__.py' 2025-12-13T07:28:31,779 adding 'seal5/transform/explicit_truncations/transform.py' 2025-12-13T07:28:31,781 adding 'seal5/transform/explicit_truncations/visitor.py' 2025-12-13T07:28:31,783 adding 'seal5/transform/filter_model/__init__.py' 2025-12-13T07:28:31,784 adding 'seal5/transform/filter_model/filter.py' 2025-12-13T07:28:31,786 adding 'seal5/transform/infer_types/__init__.py' 2025-12-13T07:28:31,787 adding 'seal5/transform/infer_types/transform.py' 2025-12-13T07:28:31,789 adding 'seal5/transform/infer_types/visitor.py' 2025-12-13T07:28:31,791 adding 'seal5/transform/inline_functions/__init__.py' 2025-12-13T07:28:31,792 adding 'seal5/transform/inline_functions/optimizer.py' 2025-12-13T07:28:31,794 adding 'seal5/transform/inline_functions/visitor.py' 2025-12-13T07:28:31,796 adding 'seal5/transform/optimize_instructions/__init__.py' 2025-12-13T07:28:31,797 adding 'seal5/transform/optimize_instructions/optimizer.py' 2025-12-13T07:28:31,799 adding 'seal5/transform/process_settings/__init__.py' 2025-12-13T07:28:31,801 adding 'seal5/transform/process_settings/transform.py' 2025-12-13T07:28:31,802 adding 'seal5/transform/simplify_trivial_slices/__init__.py' 2025-12-13T07:28:31,804 adding 'seal5/transform/simplify_trivial_slices/transform.py' 2025-12-13T07:28:31,805 adding 'seal5/transform/simplify_trivial_slices/visitor.py' 2025-12-13T07:28:31,809 adding 'seal5-0.3.2.dist-info/licenses/LICENSE' 2025-12-13T07:28:31,811 adding 'seal5-0.3.2.dist-info/METADATA' 2025-12-13T07:28:31,812 adding 'seal5-0.3.2.dist-info/WHEEL' 2025-12-13T07:28:31,813 adding 'seal5-0.3.2.dist-info/entry_points.txt' 2025-12-13T07:28:31,814 adding 'seal5-0.3.2.dist-info/top_level.txt' 2025-12-13T07:28:31,817 adding 'seal5-0.3.2.dist-info/RECORD' 2025-12-13T07:28:31,823 removing build/bdist.linux-armv7l/wheel 2025-12-13T07:28:31,993 Building wheel for seal5 (pyproject.toml): finished with status 'done' 2025-12-13T07:28:32,006 Created wheel for seal5: filename=seal5-0.3.2-py3-none-any.whl size=318261 sha256=ce5406f34e574e238611e81da6d677cc556cda15e189810126da3ad7f2c08821 2025-12-13T07:28:32,007 Stored in directory: /tmp/pip-ephem-wheel-cache-nq9mic0t/wheels/1d/27/16/38bc31a373a110049455f5e56a57b0266786d92a585b4ec3fb 2025-12-13T07:28:32,025 Successfully built seal5 2025-12-13T07:28:32,037 Removed build tracker: '/tmp/pip-build-tracker-brohgzpp'