On 9/10/22 11:42, Arve Barsnes wrote:
On Sat, 10 Sept 2022 at 17:28, Jack <ostrof...@users.sourceforge.net> wrote:
Any thoughts or suggestions?
I feel like this is an error that tends to pop up when your toolchain
is broken. Are you able to re-emerge gcc?
Reasonable thought. I've just kicked of a re-emerge of gcc. I'll post
back when it's done - likely an hour or two.
What's odd is that I've done plenty of other successful emerges since I
first got this error, although I certainly realize that different
packages use very different subsets of the total tool chain.
