[bug #18755] exported var-define and var-define from command line should appear in $(shell ) env

URL: Summary: exported var-define and var-define from command line should appear in $(shell ) env Project: make Submitted by: chjfth Submitted on: Thursday 01/11/07 at 10:23 Severity

Re: EAGAIN in "read jobs pipe"

james coleman wrote: not much! also a build making more calls to make can result in jfactor * number of make calls jobs Only if you're using a totally braindead implementation of make. The whole point of the jobserver pipe is to eliminate this fanout problem. So I might regularily use

Re: EAGAIN in "read jobs pipe"

On Wed, 2007-01-10 at 01:53 -0800, Howard Chu wrote: > An essential design choice. This stuff relies on reads and writes of the > job_fd being atomic and the writes never blocking. POSIX guarantees a 4K > buffer for pipes. Perhaps the code should check the resource limit and > complain if the -

Re: EAGAIN in "read jobs pipe"

Oh dear. Sorry people. I was of course being a bit silly when talking about make -j 16385! Howard Chu wrote: [EMAIL PROTECTED] wrote: Perhaps... On the other hand, if you're using -j 65K, why not just -j? Does you build even have 65K jobs? of course I do not use -j65k ! :-O :-) Very good

Re: EAGAIN in "read jobs pipe"

[EMAIL PROTECTED] wrote: Noticed something else. Something else completely pointless! must not be > 16385 True, if you have 16 KB pipes... gmake -j 16386; # or above hang gmake -j 16385; # or below fire along rapidly Because you're trying to write more into the job tokens

RE: EAGAIN in "read jobs pipe"

>Noticed something else. > >Something else completely pointless! > > must not be > 16385 True, if you have 16 KB pipes... > gmake -j 16386; # or above hang > gmake -j 16385; # or below fire along rapidly Because you're trying to write more into the job tokens pipe than it can hold... You app