On 2017-10-08, Mick <michaelkintz...@gmail.com> wrote: > On Sunday, 8 October 2017 18:02:43 BST Grant Edwards wrote: > >> I was afraid it might be failing RAM, but a second attempt failed in >> exactly the same way. I guess I'll delete the ebuild files and the >> source tarball to force a download and then try again.
Same error. > This won't harm, although I would expect portage would complain and > not run the emerge if downloads were corrupted somehow. True, but I couldn't think of anything else to try. I'm building chromium now -- it may be time to give up on firefox. It's been bahaving badly on several of my systems for a while now (burning 100% cpu and using up huge amounts of RAM for minutes at a time while apparently doing nothing). -- Grant
