On Thu, 7 Oct 2021, Greg A. Woods wrote:
It's almost as if the call to rename() in 'mv' succeeds, but returns an
ENOENT error sometimes!!!
Or, there's a race to completion happening. Is libstdc++-v3 being built
twice?
BTW, there's a rule in /usr/src/external/gpl3/gcc/lib/libstdc++-v3/Makefi
Updating src tree:
P src/distrib/sets/lists/tests/mi
P src/lib/libc/arch/aarch64/gen/_setjmp.S
P src/lib/libc/arch/aarch64/gen/setjmp.S
P src/sys/arch/arm/arm/cpufunc_asm_armv5.S
P src/sys/arch/arm/arm/cpufunc_asm_armv5_ec.S
P src/sys/arch/riscv/riscv/pmap_machdep.c
P src/sys/arch/riscv/riscv/ris
At Thu, 07 Oct 2021 10:25:31 -0700, "Greg A. Woods" wrote:
Subject: very strange build failure in
external/gpl3/gcc/lib/libstdc++-v3/include/bits
>
> I had a parallel build fail as follows yesterday.
>
> This same source tree has been built in the same way on the same machine
> multiple times wit
I had a parallel build fail as follows yesterday.
This same source tree has been built in the same way on the same machine
multiple times without these errors ever appearing. An rsync'ed copy of
the source tree has been successfully built on another machine multiple
times without these errors eve
