https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279187
--- Comment #3 from Jason E. Hale <jh...@freebsd.org> --- I thought these were good to go too after the exp-run (bug #278693), but after rebuilding with ccache enabled, I have been able to reproduce and confirm the exact failures in bug #279162 and bug #279164 myself. Yes, they were using the standard options as was I. Not going to disbelieve the reports of 3 reputable individuals plus my own observations. Believe me, I am thoroughly frustrated and extremely disappointed after spending countless hours fixing build errors in our 9 chromium-based ports, especially with iridium. OOM errors for qt*-webengine in the official package builders, especially for i386 are irrelevant. Like I said, I had successful initial builds with ninja 1.12.x, but rebuilds with ccache enabled have lead to failure and sadness. I rolled back ninja from 1.12.1 to 1.12.0 initially thinking there may have been a problem with it after the exp-run for ninja 1.12.0 came back successful, but clearly there are more problems to be addressed with even ninja 1.12.0. I have a glorious seven year old core i7 laptop with 32GB of RAM, and even it doesn’t like ninja 1.12.x + qt*-webengine. I’d greatly appreciate help since I’m obviously limited on resources, but the problem is real. -- You are receiving this mail because: You are the assignee for the bug.
