Re: very strange build failure in external/gpl3/gcc/lib/libstdc++-v3/include/bits

At Fri, 8 Oct 2021 19:44:02 +0000 (UTC), RVP <[email protected]> wrote:
Subject: Re: very strange build failure in external/gpl3/gcc/lib/libstdc++-v3/include/bits
>
> On Fri, 8 Oct 2021, Greg A. Woods wrote:
>
> > If two identical 'mv' commands run in the same directory (with no other
> > commands running there in between) then the second one is going to
> > report an ENOENT error.  Given these 'mv' commands are on the tail of a
> > command list that creates the source file, they have to run very nearly
> > in parallel in order to trigger the observed failure.
> >
>
> GCC comes with a move-if-change script to do just this kind of file-rename
> juggling. Try using that in the rule instead of the home-brew commands...
>
> /usr/src/external/gpl3/gcc/dist/move-if-change

I think that would be very thin wallpaper for such a problem.  :-)

There are possibly other lurking problems for such a parallel build
failure, so fixing the root cause really would be the better solution.

--
					Greg A. Woods <[email protected]>

Kelowna, BC     +1 250 762-7675           RoboHack <[email protected]>
Planix, Inc. <[email protected]>     Avoncote Farms <[email protected]>

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRuK6dmwVAucmRxuh9mfXG3eL/0fwUCYWHaJQAKCRBmfXG3eL/0
fzziAKCXWw3juQxEo7qj4+yG6d03rAeBLACdGX6Q2psEhn9ZqNw1qAY21+k6GHU=
=zu2R
-----END PGP SIGNATURE-----