==> Synchronizing chroot copy [/home/leming/armv7/root] -> [leming]...done
==> Making package: python-llfuse 1.5.0-3 (Tue Dec 24 02:04:51 2024)
==> Retrieving sources...
-> Found llfuse-1.5.0.tar.gz
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha256sums...
llfuse-1.5.0.tar.gz ... Passed
==> Making package: python-llfuse 1.5.0-3 (Tue Dec 24 02:05:14 2024)
==> Checking runtime dependencies...
==> Installing missing dependencies...
[?25lresolving dependencies...
looking for conflicting packages...
Packages (2) fuse-common-3.16.2-1 fuse2-2.9.9-5
Total Download Size: 0.10 MiB
Total Installed Size: 0.37 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
fuse2-2.9.9-5-armv7h downloading...
fuse-common-3.16.2-1-armv7h downloading...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing fuse-common...
installing fuse2...
:: Running post-transaction hooks...
(1/2) Reloading device manager configuration...
Skipped: Device manager is not running.
(2/2) Arming ConditionNeedsUpdate...
[?25h==> Checking buildtime dependencies...
==> Installing missing dependencies...
[?25lresolving dependencies...
looking for conflicting packages...
Packages (11) python-autocommand-2.2.2-7 python-jaraco.collections-5.0.1-2
python-jaraco.context-5.3.0-3 python-jaraco.functools-4.1.0-1
python-jaraco.text-4.0.0-2 python-more-itertools-10.5.0-1
python-packaging-24.2-3 python-platformdirs-4.3.6-2
python-wheel-0.45.0-3 cython-3.0.11-2
python-setuptools-1:75.2.0-4
Total Installed Size: 28.06 MiB
:: Proceed with installation? [Y/n]
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing python-more-itertools...
installing python-jaraco.functools...
installing python-jaraco.context...
installing python-autocommand...
installing python-jaraco.text...
Optional dependencies for python-jaraco.text
python-inflect: for show-newlines script
installing python-jaraco.collections...
installing python-packaging...
installing python-platformdirs...
installing python-wheel...
Optional dependencies for python-wheel
python-keyring: for wheel.signatures
python-xdg: for wheel.signatures
python-setuptools: for legacy bdist_wheel subcommand [pending]
installing python-setuptools...
installing cython...
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
[?25h==> Retrieving sources...
-> Found llfuse-1.5.0.tar.gz
==> WARNING: Skipping all source file integrity checks.
==> Extracting sources...
-> Extracting llfuse-1.5.0.tar.gz with bsdtar
==> Starting prepare()...
==> Starting build()...
/usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'tests_require'
warnings.warn(msg)
running build_cython
Using Cython version 3.0.11.
Compiling /build/python-llfuse/src/llfuse-1.5.0/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.
/usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'tests_require'
warnings.warn(msg)
running build_ext
building 'llfuse' extension
creating build/temp.linux-armv7l-cpython-313/src
gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -march=armv7-a -mfloat-abi=hard -mfpu=neon -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -march=armv7-a -mfloat-abi=hard -mfpu=neon -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -march=armv7-a -mfloat-abi=hard -mfpu=neon -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -march=armv7-a -mfloat-abi=hard -mfpu=neon -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fPIC -I/usr/include/python3.13 -c src/llfuse.c -o build/temp.linux-armv7l-cpython-313/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.0\" -Wno-unused-function -Wno-implicit-fallthrough -Wno-unused-parameter
In file included from /usr/include/python3.13/internal/pycore_code.h:12,
from /usr/include/python3.13/internal/pycore_frame.h:13,
from src/llfuse.c:63169:
/usr/include/python3.13/internal/pycore_backoff.h: In function 'make_backoff_counter':
/usr/include/python3.13/internal/pycore_backoff.h:60:20: warning: conversion from 'uint16_t' {aka 'short unsigned int'} to 'short unsigned int:12' may change value [-Wconversion]
/usr/include/python3.13/internal/pycore_backoff.h:61:22: warning: conversion from 'uint16_t' {aka 'short unsigned int'} to 'unsigned char:4' may change value [-Wconversion]
/usr/include/python3.13/internal/pycore_backoff.h: In function 'restart_backoff_counter':
/usr/include/python3.13/internal/pycore_backoff.h:78:66: warning: conversion from 'int' to 'uint16_t' {aka 'short unsigned int'} may change value [-Wconversion]
gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -march=armv7-a -mfloat-abi=hard -mfpu=neon -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -march=armv7-a -mfloat-abi=hard -mfpu=neon -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -march=armv7-a -mfloat-abi=hard -mfpu=neon -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -march=armv7-a -mfloat-abi=hard -mfpu=neon -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fPIC -I/usr/include/python3.13 -c src/lock.c -o build/temp.linux-armv7l-cpython-313/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.0\" -Wno-unused-function -Wno-implicit-fallthrough -Wno-unused-parameter
creating build/lib.linux-armv7l-cpython-313
gcc -shared -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -march=armv7-a -mfloat-abi=hard -mfpu=neon -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection build/temp.linux-armv7l-cpython-313/src/llfuse.o build/temp.linux-armv7l-cpython-313/src/lock.o -L/usr/lib -o build/lib.linux-armv7l-cpython-313/llfuse.cpython-313-arm-linux-gnueabihf.so -lfuse -pthread -lpthread -lrt
copying build/lib.linux-armv7l-cpython-313/llfuse.cpython-313-arm-linux-gnueabihf.so -> src
==> Entering fakeroot environment...
==> Starting package()...
/usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'tests_require'
warnings.warn(msg)
running install
/usr/lib/python3.13/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 build
running build_ext
running install_lib
creating /build/python-llfuse/pkg/python-llfuse/usr/lib/python3.13/site-packages
copying build/lib.linux-armv7l-cpython-313/llfuse.cpython-313-arm-linux-gnueabihf.so -> /build/python-llfuse/pkg/python-llfuse/usr/lib/python3.13/site-packages
writing byte-compilation script '/tmp/tmps4i957cg.py'
/usr/bin/python /tmp/tmps4i957cg.py
removing /tmp/tmps4i957cg.py
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 /build/python-llfuse/pkg/python-llfuse/usr/lib/python3.13/site-packages/llfuse-1.5.0-py3.13.egg-info
running install_scripts
==> Tidying install...
-> Removing empty directories...
-> Removing libtool files...
-> Purging unwanted files...
-> Removing static library files...
-> Stripping unneeded symbols from binaries and libraries...
-> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "python-llfuse"...
-> Generating .PKGINFO file...
-> Generating .BUILDINFO file...
-> Generating .MTREE file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: python-llfuse 1.5.0-3 (Tue Dec 24 02:06:02 2024)
==> Cleaning up...