Neil Bothwick wrote: > On Mon, 7 Dec 2020 14:48:00 -0600, Dale wrote: > >>> Thank you very much ! >>> I really did not expect the error to appear so far up in the build.log >> Back when CPUs were single core, the error messages were fairly close to >> the bottom. After all, it was running one or two pieces of code at a >> time. With newer multi-core/threaded CPUs, that message gets further >> back the more cores/threads you have. > Which is why it helps to repeat the emerge attempt with MAKEOPTS="-j1". > Sometimes that in itself fixes the issue, in which case you can report a > bug. Even if the build still fails, it is much easier to see the symptoms > of the problem when it is not all mixed in with the output from successful > operations. > >
That is true too. There is the occasional failure that -j1 fixes but I haven't seen that in quite a long time. To save time tho, it might be wise to at least try it but I wouldn't hold my breath or anything. Dale :-) :-)
