+ case "${usergroup_phase}" in
+ local run_cmd
+ run_cmd=run_su
+ shift
+ run_su /opt/local/bin/bmake all BATCH=1 DEPENDS_TARGET=/nonexistent PYTHON_VERSION_REQD=311 WRKLOG=/tmp/bulklog/py311-pint-0.20.1nb1/work.log
+ su pbulk -c '"$@"' make /opt/local/bin/bmake all BATCH=1 DEPENDS_TARGET=/nonexistent PYTHON_VERSION_REQD=311 WRKLOG=/tmp/bulklog/py311-pint-0.20.1nb1/work.log
=> Bootstrap dependency digest>=20211023: found digest-20220214
===> Building for py311-pint-0.20.1nb1
(cd /home/pbulk/build/wip/py-pint/work/Pint-0.20.1/ && /usr/bin/env USETOOLS=no PTHREAD_CFLAGS=\ -pthread\  PTHREAD_LDFLAGS=\ -pthread PTHREAD_LIBS=-lpthread\ -lrt PTHREADBASE=/usr DL_CFLAGS= DL_LDFLAGS= DL_LIBS= PYTHON=/opt/local/bin/python3.11 CC=gcc CFLAGS=-pipe\ -O2\ -msave-args\ -fno-aggressive-loop-optimizations\ -I/usr/include\ -I/opt/local/include/python3.11\ -I/opt/local/include CPPFLAGS=-I/usr/include\ -I/opt/local/include/python3.11\ -I/opt/local/include CXX=g++ CXXFLAGS=-pipe\ -O2\ -msave-args\ -fno-aggressive-loop-optimizations\ -I/usr/include\ -I/opt/local/include/python3.11\ -I/opt/local/include COMPILER_RPATH_FLAG=-Wl,-R F77=f77 FC=f77 FFLAGS=-O LANG=C LC_ALL=C LC_COLLATE=C LC_CTYPE=C LC_MESSAGES=C LC_MONETARY=C LC_NUMERIC=C LC_TIME=C LDFLAGS=-L/usr/lib/amd64\ -Wl,-R/usr/lib/amd64\ -Wl,-R/opt/local/lib\ -lintl\ -liconv\ -L/opt/local/lib LINKER_RPATH_FLAG=-R PATH=/home/pbulk/build/wip/py-pint/work/.cwrapper/bin:/home/pbulk/build/wip/py-pint/work/.buildlink/bin:/home/pbulk/build/wip/py-pint/work/.tools/bin:/opt/local/bin:/sbin:/usr/sbin:/usr/bin:/opt/tools/bin:/opt/local/bin:/opt/local/bin PREFIX=/opt/local MAKELEVEL=0 CONFIG_SITE= PKG_SYSCONFDIR=/opt/local/etc CPP=cpp CXXCPP=cpp HOME=/home/pbulk/build/wip/py-pint/work/.home CWRAPPERS_CONFIG_DIR=/home/pbulk/build/wip/py-pint/work/.cwrapper/config CPP=cpp LOCALBASE=/opt/local X11BASE=/opt/local PKGMANDIR=man PKGINFODIR=info PKGGNUDIR= MAKECONF=/dev/null OBJECT_FMT=ELF USETOOLS=no BSD_INSTALL_PROGRAM=/opt/local/bin/bsdinstall\ -c\ \ -o\ pbulk\ -g\ pbulk\ -m\ 755 BSD_INSTALL_SCRIPT=/opt/local/bin/bsdinstall\ -c\ -o\ pbulk\ -g\ pbulk\ -m\ 755 BSD_INSTALL_LIB=/opt/local/bin/bsdinstall\ -c\ -o\ pbulk\ -g\ pbulk\ -m\ 755 BSD_INSTALL_DATA=/opt/local/bin/bsdinstall\ -c\ -o\ pbulk\ -g\ pbulk\ -m\ 644 BSD_INSTALL_MAN=/opt/local/bin/bsdinstall\ -c\ -o\ pbulk\ -g\ pbulk\ -m\ 644 BSD_INSTALL=/opt/local/bin/bsdinstall BSD_INSTALL_PROGRAM_DIR=/opt/local/bin/bsdinstall\ -d\ -o\ pbulk\ -g\ pbulk\ -m\ 755 BSD_INSTALL_SCRIPT_DIR=/opt/local/bin/bsdinstall\ -d\ -o\ pbulk\ -g\ pbulk\ -m\ 755 BSD_INSTALL_LIB_DIR=/opt/local/bin/bsdinstall\ -d\ -o\ pbulk\ -g\ pbulk\ -m\ 755 BSD_INSTALL_DATA_DIR=/opt/local/bin/bsdinstall\ -d\ -o\ pbulk\ -g\ pbulk\ -m\ 755 BSD_INSTALL_MAN_DIR=/opt/local/bin/bsdinstall\ -d\ -o\ pbulk\ -g\ pbulk\ -m\ 755 BSD_INSTALL_GAME=/opt/local/bin/bsdinstall\ -c\ \ -o\ pbulk\ -g\ pbulk\ -m\ 2555 BSD_INSTALL_GAME_DATA=/opt/local/bin/bsdinstall\ -c\ -o\ pbulk\ -g\ pbulk\ -m\ 664 BSD_INSTALL_GAME_DIR=/opt/local/bin/bsdinstall\ -d\ -o\ pbulk\ -g\ pbulk\ -m\ 775 INSTALL_INFO= MAKEINFO=/home/pbulk/build/wip/py-pint/work/.tools/bin/makeinfo FLEX= BISON= ITSTOOL=/home/pbulk/build/wip/py-pint/work/.tools/bin/itstool GDBUS_CODEGEN=/home/pbulk/build/wip/py-pint/work/.tools/bin/gdbus-codegen PKG_CONFIG=/home/pbulk/build/wip/py-pint/work/.tools/bin/pkg-config PKG_CONFIG_LIBDIR=/home/pbulk/build/wip/py-pint/work/.buildlink/lib/amd64/pkgconfig:/home/pbulk/build/wip/py-pint/work/.buildlink/lib/pkgconfig:/home/pbulk/build/wip/py-pint/work/.buildlink/share/pkgconfig PKG_CONFIG_LOG=/home/pbulk/build/wip/py-pint/work/.pkg-config.log PKG_CONFIG_PATH= CWRAPPERS_CONFIG_DIR=/home/pbulk/build/wip/py-pint/work/.cwrapper/config  /opt/local/bin/python3.11 setup.py  build   -j1)
/opt/local/lib/python3.11/site-packages/setuptools/__init__.py:80: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!

        ********************************************************************************
        Requirements should be satisfied by a PEP 517 installer.
        If you are using pip, you can try `pip install --use-pep517`.
        ********************************************************************************

!!
  dist.fetch_build_eggs(dist.setup_requires)
WARNING: The wheel package is not available.
running build
running build_py
creating build
creating build/lib
creating build/lib/pint
copying pint/__init__.py -> build/lib/pint
copying pint/_typing.py -> build/lib/pint
copying pint/babel_names.py -> build/lib/pint
copying pint/compat.py -> build/lib/pint
copying pint/context.py -> build/lib/pint
copying pint/converters.py -> build/lib/pint
copying pint/definitions.py -> build/lib/pint
copying pint/errors.py -> build/lib/pint
copying pint/formatting.py -> build/lib/pint
copying pint/matplotlib.py -> build/lib/pint
copying pint/pint_eval.py -> build/lib/pint
copying pint/registry.py -> build/lib/pint
copying pint/registry_helpers.py -> build/lib/pint
copying pint/testing.py -> build/lib/pint
copying pint/util.py -> build/lib/pint
running egg_info
writing Pint.egg-info/PKG-INFO
writing dependency_links to Pint.egg-info/dependency_links.txt
writing requirements to Pint.egg-info/requires.txt
writing top-level names to Pint.egg-info/top_level.txt
reading manifest file 'Pint.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'BADGES.rst'
warning: no files found matching 'version.txt'
warning: no files found matching '*' under directory 'bench'
no previously-included directories found matching 'docs/_build'
no previously-included directories found matching 'docs/_themes/.git'
warning: no previously-included files found matching '.editorconfig'
warning: no previously-included files found matching 'bors.toml'
warning: no previously-included files found matching 'pull_request_template.md'
warning: no previously-included files found matching 'requirements_docs.txt'
warning: no previously-included files found matching 'version.py'
warning: no previously-included files matching '*.pyc' found anywhere in distribution
warning: no previously-included files matching '*~' found anywhere in distribution
warning: no previously-included files matching '.DS_Store' found anywhere in distribution
warning: no previously-included files matching '*__pycache__*' found anywhere in distribution
warning: no previously-included files matching '*.pyo' found anywhere in distribution
warning: no previously-included files matching '.travis-exclude.yml' found anywhere in distribution
adding license file 'LICENSE'
adding license file 'AUTHORS'
writing manifest file 'Pint.egg-info/SOURCES.txt'
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint._vendor' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint._vendor' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint._vendor' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint._vendor' to be distributed and are
        already explicitly excluding 'pint._vendor' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint.delegates' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint.delegates' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint.delegates' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint.delegates' to be distributed and are
        already explicitly excluding 'pint.delegates' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint.delegates.txt_defparser' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint.delegates.txt_defparser' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint.delegates.txt_defparser' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint.delegates.txt_defparser' to be distributed and are
        already explicitly excluding 'pint.delegates.txt_defparser' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint.facets' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint.facets' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint.facets' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint.facets' to be distributed and are
        already explicitly excluding 'pint.facets' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint.facets.context' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint.facets.context' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint.facets.context' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint.facets.context' to be distributed and are
        already explicitly excluding 'pint.facets.context' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint.facets.dask' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint.facets.dask' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint.facets.dask' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint.facets.dask' to be distributed and are
        already explicitly excluding 'pint.facets.dask' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint.facets.formatting' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint.facets.formatting' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint.facets.formatting' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint.facets.formatting' to be distributed and are
        already explicitly excluding 'pint.facets.formatting' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint.facets.group' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint.facets.group' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint.facets.group' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint.facets.group' to be distributed and are
        already explicitly excluding 'pint.facets.group' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint.facets.measurement' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint.facets.measurement' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint.facets.measurement' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint.facets.measurement' to be distributed and are
        already explicitly excluding 'pint.facets.measurement' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint.facets.nonmultiplicative' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint.facets.nonmultiplicative' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint.facets.nonmultiplicative' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint.facets.nonmultiplicative' to be distributed and are
        already explicitly excluding 'pint.facets.nonmultiplicative' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint.facets.numpy' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint.facets.numpy' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint.facets.numpy' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint.facets.numpy' to be distributed and are
        already explicitly excluding 'pint.facets.numpy' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint.facets.plain' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint.facets.plain' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint.facets.plain' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint.facets.plain' to be distributed and are
        already explicitly excluding 'pint.facets.plain' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint.facets.system' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint.facets.system' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint.facets.system' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint.facets.system' to be distributed and are
        already explicitly excluding 'pint.facets.system' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint.testsuite' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint.testsuite' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint.testsuite' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint.testsuite' to be distributed and are
        already explicitly excluding 'pint.testsuite' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'pint.testsuite.baseline' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'pint.testsuite.baseline' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'pint.testsuite.baseline' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'pint.testsuite.baseline' to be distributed and are
        already explicitly excluding 'pint.testsuite.baseline' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
copying pint/constants_en.txt -> build/lib/pint
copying pint/default_en.txt -> build/lib/pint
copying pint/pint-convert -> build/lib/pint
copying pint/py.typed -> build/lib/pint
copying pint/xtranslated.txt -> build/lib/pint
creating build/lib/pint/_vendor
copying pint/_vendor/__init__.py -> build/lib/pint/_vendor
copying pint/_vendor/appdirs.py -> build/lib/pint/_vendor
copying pint/_vendor/flexcache.py -> build/lib/pint/_vendor
copying pint/_vendor/flexparser.py -> build/lib/pint/_vendor
creating build/lib/pint/delegates
copying pint/delegates/__init__.py -> build/lib/pint/delegates
copying pint/delegates/base_defparser.py -> build/lib/pint/delegates
creating build/lib/pint/delegates/txt_defparser
copying pint/delegates/txt_defparser/__init__.py -> build/lib/pint/delegates/txt_defparser
copying pint/delegates/txt_defparser/block.py -> build/lib/pint/delegates/txt_defparser
copying pint/delegates/txt_defparser/common.py -> build/lib/pint/delegates/txt_defparser
copying pint/delegates/txt_defparser/context.py -> build/lib/pint/delegates/txt_defparser
copying pint/delegates/txt_defparser/defaults.py -> build/lib/pint/delegates/txt_defparser
copying pint/delegates/txt_defparser/defparser.py -> build/lib/pint/delegates/txt_defparser
copying pint/delegates/txt_defparser/group.py -> build/lib/pint/delegates/txt_defparser
copying pint/delegates/txt_defparser/plain.py -> build/lib/pint/delegates/txt_defparser
copying pint/delegates/txt_defparser/system.py -> build/lib/pint/delegates/txt_defparser
creating build/lib/pint/facets
copying pint/facets/__init__.py -> build/lib/pint/facets
creating build/lib/pint/facets/context
copying pint/facets/context/__init__.py -> build/lib/pint/facets/context
copying pint/facets/context/definitions.py -> build/lib/pint/facets/context
copying pint/facets/context/objects.py -> build/lib/pint/facets/context
copying pint/facets/context/registry.py -> build/lib/pint/facets/context
creating build/lib/pint/facets/dask
copying pint/facets/dask/__init__.py -> build/lib/pint/facets/dask
creating build/lib/pint/facets/formatting
copying pint/facets/formatting/__init__.py -> build/lib/pint/facets/formatting
copying pint/facets/formatting/objects.py -> build/lib/pint/facets/formatting
copying pint/facets/formatting/registry.py -> build/lib/pint/facets/formatting
creating build/lib/pint/facets/group
copying pint/facets/group/__init__.py -> build/lib/pint/facets/group
copying pint/facets/group/definitions.py -> build/lib/pint/facets/group
copying pint/facets/group/objects.py -> build/lib/pint/facets/group
copying pint/facets/group/registry.py -> build/lib/pint/facets/group
creating build/lib/pint/facets/measurement
copying pint/facets/measurement/__init__.py -> build/lib/pint/facets/measurement
copying pint/facets/measurement/objects.py -> build/lib/pint/facets/measurement
copying pint/facets/measurement/registry.py -> build/lib/pint/facets/measurement
creating build/lib/pint/facets/nonmultiplicative
copying pint/facets/nonmultiplicative/__init__.py -> build/lib/pint/facets/nonmultiplicative
copying pint/facets/nonmultiplicative/definitions.py -> build/lib/pint/facets/nonmultiplicative
copying pint/facets/nonmultiplicative/objects.py -> build/lib/pint/facets/nonmultiplicative
copying pint/facets/nonmultiplicative/registry.py -> build/lib/pint/facets/nonmultiplicative
creating build/lib/pint/facets/numpy
copying pint/facets/numpy/__init__.py -> build/lib/pint/facets/numpy
copying pint/facets/numpy/numpy_func.py -> build/lib/pint/facets/numpy
copying pint/facets/numpy/quantity.py -> build/lib/pint/facets/numpy
copying pint/facets/numpy/registry.py -> build/lib/pint/facets/numpy
copying pint/facets/numpy/unit.py -> build/lib/pint/facets/numpy
creating build/lib/pint/facets/plain
copying pint/facets/plain/__init__.py -> build/lib/pint/facets/plain
copying pint/facets/plain/definitions.py -> build/lib/pint/facets/plain
copying pint/facets/plain/objects.py -> build/lib/pint/facets/plain
copying pint/facets/plain/quantity.py -> build/lib/pint/facets/plain
copying pint/facets/plain/registry.py -> build/lib/pint/facets/plain
copying pint/facets/plain/unit.py -> build/lib/pint/facets/plain
creating build/lib/pint/facets/system
copying pint/facets/system/__init__.py -> build/lib/pint/facets/system
copying pint/facets/system/definitions.py -> build/lib/pint/facets/system
copying pint/facets/system/objects.py -> build/lib/pint/facets/system
copying pint/facets/system/registry.py -> build/lib/pint/facets/system
creating build/lib/pint/testsuite
copying pint/testsuite/__init__.py -> build/lib/pint/testsuite
copying pint/testsuite/conftest.py -> build/lib/pint/testsuite
copying pint/testsuite/helpers.py -> build/lib/pint/testsuite
copying pint/testsuite/test_application_registry.py -> build/lib/pint/testsuite
copying pint/testsuite/test_babel.py -> build/lib/pint/testsuite
copying pint/testsuite/test_compat.py -> build/lib/pint/testsuite
copying pint/testsuite/test_compat_downcast.py -> build/lib/pint/testsuite
copying pint/testsuite/test_compat_upcast.py -> build/lib/pint/testsuite
copying pint/testsuite/test_contexts.py -> build/lib/pint/testsuite
copying pint/testsuite/test_converters.py -> build/lib/pint/testsuite
copying pint/testsuite/test_dask.py -> build/lib/pint/testsuite
copying pint/testsuite/test_definitions.py -> build/lib/pint/testsuite
copying pint/testsuite/test_diskcache.py -> build/lib/pint/testsuite
copying pint/testsuite/test_errors.py -> build/lib/pint/testsuite
copying pint/testsuite/test_formatter.py -> build/lib/pint/testsuite
copying pint/testsuite/test_formatting.py -> build/lib/pint/testsuite
copying pint/testsuite/test_infer_base_unit.py -> build/lib/pint/testsuite
copying pint/testsuite/test_issues.py -> build/lib/pint/testsuite
copying pint/testsuite/test_log_units.py -> build/lib/pint/testsuite
copying pint/testsuite/test_matplotlib.py -> build/lib/pint/testsuite
copying pint/testsuite/test_measurement.py -> build/lib/pint/testsuite
copying pint/testsuite/test_non_int.py -> build/lib/pint/testsuite
copying pint/testsuite/test_numpy.py -> build/lib/pint/testsuite
copying pint/testsuite/test_numpy_func.py -> build/lib/pint/testsuite
copying pint/testsuite/test_pint_eval.py -> build/lib/pint/testsuite
copying pint/testsuite/test_pitheorem.py -> build/lib/pint/testsuite
copying pint/testsuite/test_quantity.py -> build/lib/pint/testsuite
copying pint/testsuite/test_systems.py -> build/lib/pint/testsuite
copying pint/testsuite/test_testing.py -> build/lib/pint/testsuite
copying pint/testsuite/test_umath.py -> build/lib/pint/testsuite
copying pint/testsuite/test_unit.py -> build/lib/pint/testsuite
copying pint/testsuite/test_util.py -> build/lib/pint/testsuite
creating build/lib/pint/testsuite/baseline
copying pint/testsuite/baseline/test_basic_plot.png -> build/lib/pint/testsuite/baseline
copying pint/testsuite/baseline/test_plot_with_set_units.png -> build/lib/pint/testsuite/baseline
running build_scripts
creating build/scripts-3.11
copying and adjusting pint/pint-convert -> build/scripts-3.11
changing mode of build/scripts-3.11/pint-convert from 644 to 755