Created attachment 880966 [details] emerge --info "emerge apsw" hangs shortly after starting [ebuild N ] dev-python/apsw-3.44.2.0::gentoo USE="-debug -doc" PYTHON_TARGETS="python3_11 -python3_10 (-python3_12)" 0 KiB Total: 1 package (1 new), Size of downloads: 0 KiB >>> Verifying ebuild manifests >>> Emerging (1 of 1) dev-python/apsw-3.44.2.0::gentoo * apsw-3.44.2.0.gh.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking apsw-3.44.2.0.gh.tar.gz to /var/tmp/portage/dev-python/apsw-3.44.2.0/work >>> Source unpacked in /var/tmp/portage/dev-python/apsw-3.44.2.0/work >>> Preparing source in /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0 ... * Build system packages: * dev-python/gpep517 : 15 * dev-python/installer : 0.7.0 * dev-python/cython : 3.0.6 * dev-python/setuptools : 69.0.2-r1 * dev-python/setuptools-rust : 1.6.0 * dev-python/setuptools-scm : 8.0.4 * dev-python/wheel : 0.42.0 >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0 ... * python3_11: running distutils-r1_run_phase distutils-r1_python_compile * Building the wheel for apsw-3.44.2.0 via setuptools.build_meta python3.11 -m gpep517 build-wheel --prefix=/usr --backend setuptools.build_meta --output-fd 3 --wheel-dir /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0-python3_11/wheel 2023-12-29 16:21:54,304 gpep517 INFO Building wheel via backend setuptools.build_meta 2023-12-29 16:21:54,525 root INFO running bdist_wheel 2023-12-29 16:21:54,581 root INFO running build 2023-12-29 16:21:54,581 root INFO running build_py 2023-12-29 16:21:54,599 root INFO creating /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0-python3_11/build 2023-12-29 16:21:54,599 root INFO creating /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0-python3_11/build/lib.linux-x86_64-cpython-311 2023-12-29 16:21:54,600 root INFO creating /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0-python3_11/build/lib.linux-x86_64-cpython-311/apsw 2023-12-29 16:21:54,600 root INFO copying apsw/__main__.py -> /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0-python3_11/build/lib.linux-x86_64-cpython-311/apsw 2023-12-29 16:21:54,601 root INFO copying apsw/bestpractice.py -> /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0-python3_11/build/lib.linux-x86_64-cpython-311/apsw 2023-12-29 16:21:54,601 root INFO copying apsw/ext.py -> /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0-python3_11/build/lib.linux-x86_64-cpython-311/apsw 2023-12-29 16:21:54,602 root INFO copying apsw/speedtest.py -> /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0-python3_11/build/lib.linux-x86_64-cpython-311/apsw 2023-12-29 16:21:54,602 root INFO copying apsw/tests.py -> /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0-python3_11/build/lib.linux-x86_64-cpython-311/apsw 2023-12-29 16:21:54,604 root INFO copying apsw/trace.py -> /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0-python3_11/build/lib.linux-x86_64-cpython-311/apsw 2023-12-29 16:21:54,604 root INFO copying apsw/shell.py -> /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0-python3_11/build/lib.linux-x86_64-cpython-311/apsw 2023-12-29 16:21:54,606 root INFO copying apsw/__init__.pyi -> /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0-python3_11/build/lib.linux-x86_64-cpython-311/apsw 2023-12-29 16:21:54,607 root INFO copying apsw/py.typed -> /var/tmp/portage/dev-python/apsw-3.44.2.0/work/apsw-3.44.2.0-python3_11/build/lib.linux-x86_64-cpython-311/apsw 2023-12-29 16:21:54,608 root WARNING warning: build_py: byte-compiling is disabled, skipping. 2023-12-29 16:21:54,608 root INFO running build_ext * * * This is where it stops doing anything.
Could you attach the output of `ps -f --forest -g portage` when emerge hangs as an attachment please?
Created attachment 880968 [details] result of `ps -f --forest -g portage` Here is the result of `ps -f --forest -g portage` (I also add it as an attachment) portage 4853 4850 0 19:02 pts/2 00:00:00 [dev-python/apsw-3.44.2.0] sandbox /usr/lib/portage/python3.11/ebuild.sh compile portage 4854 4853 0 19:02 pts/2 00:00:00 \_ bash /usr/lib/portage/python3.11/ebuild.sh compile portage 4870 4854 0 19:02 pts/2 00:00:00 \_ bash /usr/lib/portage/python3.11/ebuild.sh compile portage 4884 4870 0 19:02 pts/2 00:00:00 \_ tee -a /var/tmp/portage/dev-python/apsw-3.44.2.0/temp/build-python3_11.log portage 4963 4870 0 19:02 pts/2 00:00:00 \_ bash /usr/lib/portage/python3.11/ebuild.sh compile portage 4964 4963 0 19:02 pts/2 00:00:00 \_ python3.11 -m gpep517 build-wheel --prefix=/usr --backend setuptools.build_meta --output-fd 3 --w portage 4965 4964 0 19:02 pts/2 00:00:00 \_ python3.11 -m gpep517 build-wheel --prefix=/usr --backend setuptools.build_meta --output-fd 3 portage 4966 4965 0 19:02 pts/2 00:00:00 \_ /sbin/ldconfig -p
We should stop it running ldconfig at all if we can.
The real question is what's running ldconfig. From a quick grep, the only `ldconfig -p` invocation in my installed packages is inside Nuitka, and I honestly doubt it's being used there. Could you grep your /usr/lib/python3.11/site-packages?
The only file which matches ldconfig is /usr/lib/python3.11/site-packages/portage/util/env_update.py which belongs to sys-apps/portage-3.0.59
justI hoped it might just resolve itself after an upgrade, but no such luck. I have just upgraded everything, and emerge apsw hangs at the same place as before
Also, I tried the newer version (unstable) dev-python/apsw-3.45.2.0 it hangs at the same place, no difference
Could you try something like: grep -rsin "ldconfig -p" /usr/?
grep -rsin "ldconfig -p" /usr/ I am not sure it's correct, at least this command does not do anything
Created attachment 890972 [details] result of grep -rsin "ldconfig -p" /usr/ Sorry! It worked after all! I am adding the result as an attachment.
I am sorry for this confusion. Please ignore the previous attachment, it is an output of a different command. The output of grep -rsin "ldconfig -p" /usr/ is just two lines /usr/src/linux-4.19.72-gentoo/scripts/ver_linux:47: while ("ldconfig -p 2>/dev/null" | getline > 0) { /usr/src/linux-4.12.12-gentoo/scripts/ver_linux:46: while ("ldconfig -p 2>/dev/null" | getline > 0) {
