Per Jessen wrote: > The problem I'm seeing is (somehow) directly related to output to > stderr. One of the utilities I'm using in my jobs produces output to > both stdout and stderr (5-6 lines of diagnostics etc.) > > I went in and made some minor changes in job.c to deal with stderr > output. > After the child has been forked(), I open temporary file and use > dup2() to direct stderr output that way - and everything suddenly > works! All of my jobs are run, and the output is also no longer > garbled nor truncated.
Just to confirm - I'm using my work-around in all these parallel makes now, which is probably a total of about 10000 jobs/day. Occasionally I'll still see some garbled output, but the jobs are all run. /Per Jessen, Zürich _______________________________________________ Help-make mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-make
