Created attachment 916792 [details] ebuild log file app-office/libreoffice-24.2.7.2 Searched but did not see this issue come up so would like to file a bug report. Sorry if this is a duplicate and thank you for looking at it. Beginning at like 878 in the attached build.log file. mkdir -p /var/tmp/portage/app-office/libreoffice-24.2.7.2/work/libreoffice-24.2.7.2/workdir/ExternalProject/ touch /var/tmp/portage/app-office/libreoffice-24.2.7.2/work/libreoffice-24.2.7.2/workdir/Executable/gcc-wrapper.run touch: cannot touch '/var/tmp/portage/app-office/libreoffice-24.2.7.2/work/libreoffice-24.2.7.2/workdir/Executable/gcc-wrapper.run': No such file or directory Compiling on a Raspberry Pi 5 (8GB model) (arm64), attaching build.log file. Swap file is enabled with 8GB so memory should not be an issue. Compiling using external USB3 hard disk mounted as the root filesystem. Started with a fresh stage3 tarball (below) and now emerging the system. stage3-arm64-openrc-splitusr-20250112T234833Z.tar.xz LibreOffice is one of 874 packages pulled in for emerge. Have not attempted to compile again as current system emerge is still running and expect it to take another day or so to complete. emerge failed, I believe this is the cause below but the system is currently busy so not able to test a fix/patch at the moment. When the system becomes available I will attempt the emerge again and follow up on this report. Kernel version information: Kernel version (Rasbperry Pi default with btrfs changed from module to compile into the kernel for rootfs mount at boot). Linux version 6.6.70-v8-16k+ (root@raspberrypi) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #2 SMP PREEMPT Mon Jan 13 22:09:04 JST 2025 Versions of toolchain used: GNU ld (Gentoo 2.43 p3) 2.43.1 gcc (Gentoo 14.2.1_p20241221 p7) 14.2.1 20241221 Using a local mirror synced on 2025-01-15. Can not seem to attach two files so make.conf settings are below: /etc/portage/make.conf # These settings were set by the catalyst build script that automatically # built this stage. # Please consult /usr/share/portage/config/make.conf.example for a more # detailed example. COMMON_FLAGS="-O2 -pipe" CFLAGS="${COMMON_FLAGS}" CXXFLAGS="${COMMON_FLAGS}" FCFLAGS="${COMMON_FLAGS}" FFLAGS="${COMMON_FLAGS}" # WARNING: Changing your CHOST is not something that should be done lightly. # Please consult https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable before changing. CHOST="aarch64-unknown-linux-gnu" # NOTE: This stage was built with the bindist USE flag enabled # This sets the language of build output to English. # Please keep this setting intact when reporting bugs. LC_MESSAGES=C.utf8 # global USE flag overrides USE="" # some scripts looks for PORTDIR in make.conf explicitly PORTDIR=/var/db/repos/gentoo # override default build parallelism by changing the following # two lines, and modifying the values as required # Pi3 users (or Pi4 users with a 1GiB variant) should be # less aggressive here MAKEOPTS="-j5 -l4" EMERGE_DEFAULT_OPTS="--jobs=5 --load-average=4" # caution! many parallel threads and / or emerge jobs may cause your # RPi3/4 to run out of memory during large builds, or genup runs # to get the old (<portage-2.3.77) autoumask behaviour back, # uncomment the following line #EMERGE_DEFAULT_OPTS="${EMERGE_DEFAULT_OPTS} --autounmask" # per https://wiki.gentoo.org/wiki/Raspberry_Pi_VC4 VIDEO_CARDS="fbdev vc4 v3d" INPUT_DEVICES="evdev synaptics" # uncomment to build binary packages as a byproduct of each emerge # (these are useful backups) in /usr/portage/packages FEATURES="${FEATURES} buildpkg" # uncomment to disribute emerges, where possible, using distcc # (NB: distcc-pump mode is now effectively deprecated) #FEATURES="${FEATURES} distcc" # uncomment to use binary packages from PORTAGE_BINHOST, where available, # (and build normally, where not) FEATURES="${FEATURES} getbinpkg" PORTAGE_BINHOST="http://192.168.3.14/gentoo/pi64pie_20250115" GENTOO_MIRRORS="http://192.168.3.14/gentoo/gentoo_20250115/" PKGDIR=/var/cache/binpkgs DISTDIR=/var/cache/distfiles #additional options for binary package building BINPKG_FORMAT="gpkg" BINPKG_GPG_SIGNING_GPG_HOME="/root/.gnupg" BINPKG_GPG_SIGNING_KEY=***removed*** #FEATURES="${FEATURES} gpg-keepalive" PYTHON_TARGETS="python3_11 python3_12 python3_13"
Created attachment 916793 [details] emerge info Adding output of emerge --info
Created attachment 916794 [details] make.conf Adding /etc/portage/make.conf
Might be a missing Makefile dep.
Created attachment 916924 [details] build order Build order where the ebuild failed. This was a fresh emerge starting from the stage3 tarball (stage3-arm64-openrc-splitusr-20250112T234833Z.tar.xz). Perhaps a required dependency was not built before this ebuild was allowed to run. It would be nice to know what was missing if that was the case.
(In reply to Allan from comment #4) I'm saying missing *Makefile* dependency, i.e. some internal dependency within the Makefiles of the project, rather than a missing package.
Follow up on this bug. After the other packages finished LibreOffice was the only package that failed to emerge. Ran the emerge again, this time LibreOffice emerged successfully. There were no other emerges running in parallel. This does not resolve the bug, but I think since it also happened to someone else in https://bugs.gentoo.org/show_bug.cgi?id=937944 that there is still an issue that can show under certain circumstances. It feels like a race condition that when the system is under load the directory /var/tmp/portage/app-office/libreoffice-24.2.7.2/work/libreoffice-24.2.7.2/workdir/Executable was not created in time and needed for another part of the build. As such, I will leave this thread open for more testing.
