>>> py3-llfuse: Building community/py3-llfuse 1.5.1-r0 (using abuild 3.14.1-r3) started Thu, 28 Nov 2024 16:34:37 +0000
>>> py3-llfuse: Validating /home/buildozer/aports/community/py3-llfuse/APKBUILD...
>>> py3-llfuse: Analyzing dependencies...
>>> py3-llfuse: Installing for build: build-base python3 cython python3-dev py3-setuptools fuse-dev
(1/25) Installing libbz2 (1.0.8-r6)
(2/25) Installing libffi (3.4.6-r0)
(3/25) Installing gdbm (1.24-r0)
(4/25) Installing xz-libs (5.6.3-r0)
(5/25) Installing mpdecimal (4.0.0-r0)
(6/25) Installing libpanelw (6.5_p20241006-r3)
(7/25) Installing sqlite-libs (3.47.1-r0)
(8/25) Installing python3 (3.12.7-r1)
(9/25) Installing python3-pycache-pyc0 (3.12.7-r1)
(10/25) Installing pyc (3.12.7-r1)
(11/25) Installing python3-pyc (3.12.7-r1)
(12/25) Installing cython (3.0.10-r0)
(13/25) Installing cython-pyc (3.0.10-r0)
(14/25) Installing python3-dev (3.12.7-r1)
(15/25) Installing py3-parsing (3.1.4-r0)
(16/25) Installing py3-parsing-pyc (3.1.4-r0)
(17/25) Installing py3-packaging (24.2-r0)
(18/25) Installing py3-packaging-pyc (24.2-r0)
(19/25) Installing py3-setuptools (70.3.0-r0)
(20/25) Installing py3-setuptools-pyc (70.3.0-r0)
(21/25) Installing fuse-common (3.16.2-r1)
(22/25) Installing fuse (2.9.9-r6)
(23/25) Installing fuse-dev (2.9.9-r6)
(24/25) Installing .makedepends-py3-llfuse (20241128.163439)
(25/25) Installing fuse-openrc (3.16.2-r1)
Executing busybox-1.37.0-r8.trigger
OK: 572 MiB in 128 packages
>>> py3-llfuse: Cleaning up srcdir
>>> py3-llfuse: Cleaning up pkgdir
>>> py3-llfuse: Cleaning up tmpdir
>>> py3-llfuse: Fetching https://distfiles.alpinelinux.org/distfiles/edge/llfuse-1.5.1.tar.gz
>>> py3-llfuse: Fetching https://distfiles.alpinelinux.org/distfiles/edge/llfuse-1.5.1.tar.gz
>>> py3-llfuse: Checking sha512sums...
llfuse-1.5.1.tar.gz: OK
>>> py3-llfuse: Unpacking /var/cache/distfiles/edge/llfuse-1.5.1.tar.gz...
running build_cython
Compiling /home/buildozer/aports/community/py3-llfuse/src/llfuse-1.5.1/src/llfuse.pyx
performance hint: src/handlers.pxi:13:5: Exception check on 'fuse_init' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_init' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_init' to allow an error code to be returned.
performance hint: src/handlers.pxi:20:5: Exception check on 'fuse_destroy' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_destroy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_destroy' to allow an error code to be returned.
performance hint: src/handlers.pxi:31:5: Exception check on 'fuse_lookup' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_lookup' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_lookup' to allow an error code to be returned.
performance hint: src/handlers.pxi:51:5: Exception check on 'fuse_forget' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_forget' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_forget' to allow an error code to be returned.
performance hint: src/handlers.pxi:61:5: Exception check on 'fuse_forget_multi' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_forget_multi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_forget_multi' to allow an error code to be returned.
performance hint: src/handlers.pxi:73:5: Exception check on 'fuse_getattr' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_getattr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_getattr' to allow an error code to be returned.
performance hint: src/handlers.pxi:92:5: Exception check on 'fuse_setattr' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_setattr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_setattr' to allow an error code to be returned.
performance hint: src/handlers.pxi:148:5: Exception check on 'fuse_readlink' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_readlink' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_readlink' to allow an error code to be returned.
performance hint: src/handlers.pxi:165:5: Exception check on 'fuse_mknod' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_mknod' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_mknod' to allow an error code to be returned.
performance hint: src/handlers.pxi:184:5: Exception check on 'fuse_mkdir' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_mkdir' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_mkdir' to allow an error code to be returned.
performance hint: src/handlers.pxi:206:5: Exception check on 'fuse_unlink' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_unlink' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_unlink' to allow an error code to be returned.
performance hint: src/handlers.pxi:222:5: Exception check on 'fuse_rmdir' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_rmdir' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_rmdir' to allow an error code to be returned.
performance hint: src/handlers.pxi:238:5: Exception check on 'fuse_symlink' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_symlink' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_symlink' to allow an error code to be returned.
performance hint: src/handlers.pxi:257:5: Exception check on 'fuse_rename' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_rename' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_rename' to allow an error code to be returned.
performance hint: src/handlers.pxi:275:5: Exception check on 'fuse_link' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_link' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_link' to allow an error code to be returned.
performance hint: src/handlers.pxi:295:5: Exception check on 'fuse_open' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_open' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_open' to allow an error code to be returned.
performance hint: src/handlers.pxi:316:5: Exception check on 'fuse_read' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_read' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_read' to allow an error code to be returned.
performance hint: src/handlers.pxi:337:5: Exception check on 'fuse_write' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_write' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_write' to allow an error code to be returned.
performance hint: src/handlers.pxi:362:5: Exception check on 'fuse_write_buf' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_write_buf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_write_buf' to allow an error code to be returned.
performance hint: src/handlers.pxi:385:5: Exception check on 'fuse_flush' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_flush' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_flush' to allow an error code to be returned.
performance hint: src/handlers.pxi:400:5: Exception check on 'fuse_release' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_release' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_release' to allow an error code to be returned.
performance hint: src/handlers.pxi:415:5: Exception check on 'fuse_fsync' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_fsync' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_fsync' to allow an error code to be returned.
performance hint: src/handlers.pxi:431:5: Exception check on 'fuse_opendir' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_opendir' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_opendir' to allow an error code to be returned.
performance hint: src/handlers.pxi:448:5: Exception check on 'fuse_readdir' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_readdir' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_readdir' to allow an error code to be returned.
performance hint: src/handlers.pxi:482:5: Exception check on 'fuse_releasedir' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_releasedir' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_releasedir' to allow an error code to be returned.
performance hint: src/handlers.pxi:498:5: Exception check on 'fuse_fsyncdir' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_fsyncdir' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_fsyncdir' to allow an error code to be returned.
performance hint: src/handlers.pxi:515:5: Exception check on 'fuse_statfs' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_statfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_statfs' to allow an error code to be returned.
performance hint: src/handlers.pxi:533:5: Exception check on 'fuse_setxattr_darwin' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_setxattr_darwin' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_setxattr_darwin' to allow an error code to be returned.
performance hint: src/handlers.pxi:553:5: Exception check on 'fuse_setxattr' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_setxattr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_setxattr' to allow an error code to be returned.
performance hint: src/handlers.pxi:601:5: Exception check on 'fuse_getxattr_darwin' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_getxattr_darwin' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_getxattr_darwin' to allow an error code to be returned.
performance hint: src/handlers.pxi:613:5: Exception check on 'fuse_getxattr' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_getxattr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_getxattr' to allow an error code to be returned.
performance hint: src/handlers.pxi:641:5: Exception check on 'fuse_listxattr' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_listxattr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_listxattr' to allow an error code to be returned.
performance hint: src/handlers.pxi:671:5: Exception check on 'fuse_removexattr' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_removexattr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_removexattr' to allow an error code to be returned.
performance hint: src/handlers.pxi:687:5: Exception check on 'fuse_access' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_access' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_access' to allow an error code to be returned.
performance hint: src/handlers.pxi:707:5: Exception check on 'fuse_create' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'fuse_create' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'fuse_create' to allow an error code to be returned.
Using Cython version 3.0.10.
running build
running build_ext
building 'llfuse' extension
creating build
creating build/temp.linux-aarch64-cpython-312
creating build/temp.linux-aarch64-cpython-312/src
gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -Os -fstack-clash-protection -Wformat -Werror=format-security -fPIC -I/usr/include/python3.12 -c src/llfuse.c -o build/temp.linux-aarch64-cpython-312/src/llfuse.o -I/usr/include/fuse -D_FILE_OFFSET_BITS=64 -DFUSE_USE_VERSION=29 -Wall -Wextra -Wconversion -Wsign-compare -DLLFUSE_VERSION=\"1.5.1\" -Wno-unused-function -Wno-implicit-fallthrough -Wno-unused-parameter
gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -Os -fstack-clash-protection -Wformat -Werror=format-security -fPIC -I/usr/include/python3.12 -c src/lock.c -o build/temp.linux-aarch64-cpython-312/src/lock.o -I/usr/include/fuse -D_FILE_OFFSET_BITS=64 -DFUSE_USE_VERSION=29 -Wall -Wextra -Wconversion -Wsign-compare -DLLFUSE_VERSION=\"1.5.1\" -Wno-unused-function -Wno-implicit-fallthrough -Wno-unused-parameter
creating build/lib.linux-aarch64-cpython-312
gcc -shared -Wl,--as-needed,-O1,--sort-common -Wl,-z,pack-relative-relocs -Os -fstack-clash-protection -Wformat -Werror=format-security build/temp.linux-aarch64-cpython-312/src/llfuse.o build/temp.linux-aarch64-cpython-312/src/lock.o -L/usr/lib -o build/lib.linux-aarch64-cpython-312/llfuse.cpython-312-aarch64-linux-musl.so -lfuse -pthread -lpthread -lrt
>>> py3-llfuse: Entering fakeroot...
running install
/usr/lib/python3.12/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!

        ********************************************************************************
        Please avoid running ``setup.py`` directly.
        Instead, use pypa/build, pypa/installer or other
        standards-based tools.

        See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
        ********************************************************************************

!!
  self.initialize_options()
running install_lib
creating /home/buildozer/aports/community/py3-llfuse/pkg
creating /home/buildozer/aports/community/py3-llfuse/pkg/py3-llfuse
creating /home/buildozer/aports/community/py3-llfuse/pkg/py3-llfuse/usr
creating /home/buildozer/aports/community/py3-llfuse/pkg/py3-llfuse/usr/lib
creating /home/buildozer/aports/community/py3-llfuse/pkg/py3-llfuse/usr/lib/python3.12
creating /home/buildozer/aports/community/py3-llfuse/pkg/py3-llfuse/usr/lib/python3.12/site-packages
copying build/lib.linux-aarch64-cpython-312/llfuse.cpython-312-aarch64-linux-musl.so -> /home/buildozer/aports/community/py3-llfuse/pkg/py3-llfuse/usr/lib/python3.12/site-packages
running install_egg_info
running egg_info
writing src/llfuse.egg-info/PKG-INFO
writing dependency_links to src/llfuse.egg-info/dependency_links.txt
writing top-level names to src/llfuse.egg-info/top_level.txt
reading manifest file 'src/llfuse.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 'src/llfuse.egg-info/SOURCES.txt'
Copying src/llfuse.egg-info to /home/buildozer/aports/community/py3-llfuse/pkg/py3-llfuse/usr/lib/python3.12/site-packages/llfuse-1.5.1-py3.12.egg-info
running install_scripts
>>> py3-llfuse*: Running postcheck for py3-llfuse
>>> py3-llfuse*: Preparing package py3-llfuse...
>>> py3-llfuse*: Stripping binaries
>>> py3-llfuse*: Scanning shared objects
>>> py3-llfuse*: Tracing dependencies...
	python3
	python3~3.12
	so:libc.musl-aarch64.so.1
	so:libfuse.so.2
>>> py3-llfuse*: Package size: 402.3 KB
>>> py3-llfuse*: Compressing data...
>>> py3-llfuse*: Create checksum...
>>> py3-llfuse*: Create py3-llfuse-1.5.1-r0.apk
>>> py3-llfuse: Build complete at Thu, 28 Nov 2024 16:35:11 +0000 elapsed time 0h 0m 34s
>>> py3-llfuse: Cleaning up srcdir
>>> py3-llfuse: Cleaning up pkgdir
>>> py3-llfuse: Uninstalling dependencies...
(1/25) Purging .makedepends-py3-llfuse (20241128.163439)
(2/25) Purging cython-pyc (3.0.10-r0)
(3/25) Purging cython (3.0.10-r0)
(4/25) Purging python3-dev (3.12.7-r1)
(5/25) Purging py3-setuptools-pyc (70.3.0-r0)
(6/25) Purging py3-setuptools (70.3.0-r0)
(7/25) Purging py3-packaging-pyc (24.2-r0)
(8/25) Purging py3-packaging (24.2-r0)
(9/25) Purging py3-parsing-pyc (3.1.4-r0)
(10/25) Purging py3-parsing (3.1.4-r0)
(11/25) Purging python3-pyc (3.12.7-r1)
(12/25) Purging python3-pycache-pyc0 (3.12.7-r1)
(13/25) Purging pyc (3.12.7-r1)
(14/25) Purging python3 (3.12.7-r1)
(15/25) Purging fuse-dev (2.9.9-r6)
(16/25) Purging fuse (2.9.9-r6)
(17/25) Purging fuse-openrc (3.16.2-r1)
(18/25) Purging fuse-common (3.16.2-r1)
(19/25) Purging gdbm (1.24-r0)
(20/25) Purging libbz2 (1.0.8-r6)
(21/25) Purging libffi (3.4.6-r0)
(22/25) Purging libpanelw (6.5_p20241006-r3)
(23/25) Purging mpdecimal (4.0.0-r0)
(24/25) Purging sqlite-libs (3.47.1-r0)
(25/25) Purging xz-libs (5.6.3-r0)
Executing busybox-1.37.0-r8.trigger
OK: 397 MiB in 103 packages
>>> py3-llfuse: Updating the community/aarch64 repository index...
>>> py3-llfuse: Signing the index...