On April 8, 2019 1:14:38 PM UTC, Peter Humphrey <pe...@prh.myzen.co.uk> wrote: >Hello list, > >Is anyone else having trouble emerging systemd-boot-241? This machine >has a >small rescue system as an alternative boot, and I get a mysterious >error when >I emerge the package. The end of the log shows this: > >[248/248] x86_64-pc-linux-gnu-gcc -o bootctl 'bootctl@exe/ >src_boot_bootctl.c.o' -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro >-Wl,- >z,now -Wl,--gc-sections -O2 -march=haswell -pipe -Wl,-O1 >-Wl,--as-needed - >Wl,--start-group src/shared/libsystemd-shared-241.a src/libsystemd/ >libsystemd_static.a src/basic/libbasic.a /usr/lib64/libblkid.so -lrt >/usr/ >lib64/libcap.so /usr/lib64/libmount.so -lrt -lm -Wl,--end-group >-pthread '- >Wl,-rpath,$ORIGIN/src/shared:$ORIGIN/src/libsystemd:$ORIGIN/src/basic' >-Wl,- >rpath-link,/var/tmp/portage/sys-boot/systemd-boot-241/work/systemd-boot-241- >build/src/shared:/var/tmp/portage/sys-boot/systemd-boot-241/work/systemd- >boot-241-build/src/libsystemd:/var/tmp/portage/sys-boot/systemd-boot-241/work/ >systemd-boot-241-build/src/basic >stat: No such file or directory > * ERROR: sys-boot/systemd-boot-241::gentoo failed (compile phase): > * (no error message) > >But it compiles just fine on the main system. > >Perhaps something is missing from the rescue system and hasn't been >caught by >the ebuild, but I can't think of what. If 'stat' had said what file or >directory wasn't present, I'd be able to dig a bit deeper to find the >problem. > >I see the same behaviour on another machine. Both are 64-bit, but only >this >one is ~amd64; the other one has a KEYWORD to enable systemd-boot.
Have you tried compiling with "MAKEOPTS="-j 1"? (Eg, no parallel build? -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
