On Sat, 2018-07-07 at 18:54 +, Jason Mancini wrote:
> Thanks Paul! I pulled make from git, copied those latest *.{c,h}
> files over the top of a 4.2.1 tarball. Make is working correctly
> now. I'll check for / file an openSUSE Tumbleweed tracking bug.
> -JasonM
That's good to hear.
FYI, yo
Thanks Paul! I pulled make from git, copied those latest *.{c,h} files over
the top of a 4.2.1 tarball. Make is working correctly now. I'll check for /
file an openSUSE Tumbleweed tracking bug.
-JasonM
___
Help-make mailing list
Help-make@gnu.org
h
On Sat, 2018-07-07 at 10:01 +, Jason Mancini wrote:
> So this has been observed as gnu make not reaping defunct make/sh
> processes on openSUSE Tumbleweed. Presumably all the tokens in the
> shared jobserver read/write fds pipe become tied up by said defunct
> process, and then make behaves as
So this has been observed as gnu make not reaping defunct make/sh processes on
openSUSE Tumbleweed. Presumably all the tokens in the shared jobserver
read/write fds pipe become tied up by said defunct process, and then make
behaves as -j1 at that point. It doesn't happen every time, so it's v
Hello, I have been trying to figure out why I see an odd behavior building
Linux kernel sources that I don't see when building gcc sources. It's not a
hardware issue, I've ruled that out with various testing and bios settings and
monitoring clock speeds, etc.
Basically, on a 6-core/12-thread p
