Re: Parallel Jobs Bug

[Paul Smith]

On Sun, 2007-01-28 at 00:24 -0800, Bill Harding wrote:

> make -C Anims --no-print-directory -r -f Anims.mk all &&  make -C BGs
> --no-print-directory -r -f BGs.mk all 
> 
> However, at seemingly random intervals throughout the build process
> (usually about 4-5 times per build), I get the following error:
>  
> make[1]: *** read jobs pipe: No such file or directory.  Stop.
> make[1]: *** Waiting for unfinished jobs....
> ShIdleA.ica
> make[1]: *** Waiting for unfinished jobs....
> make: *** [build] Error 2
> Error executing c:\windows\system32\cmd.exe.

This is extremely strange.  First, when asking for help please ALWAYS
provide the version of GNU make you're using, as well as the type and
version of the system you're using it on.  Here it looks like you're
running on some kind of Windows system; in that case please provide
information about how make was built (cygwin?  MINGW?  DOS?  Etc.)  You
might also try asking on the address@hidden mailing list, since the
folks most knowledgeable about the idiosyncrasies of make on Windows
platforms tend to hang out there.

Anyway, a few facts:
      * the code that generates that output is conditionally compiled
        only if MAKE_JOBSERVERS is set, and that macro is set only if
        the configure script detects a number of POSIX-like features in
        your OS.  If you build using the default config.h.W32 etc. and
        don't run configure, that macro is not set and that code does
        not even exist in the program anywhere!
      * If the code is compiled in, it's only invoked if there is a
        jobserver pipe, and there is only a jobserver pipe if one of two
        things is true: a -jN was passed where N>1 was passed to make on
        the compile line, or the option --jobserver-fds (which is an
        internal option passed by make to its submakes and should never
        be given to make externally) was passed to make.

Altogether I can't see how the behavior you're seeing is possible with
the standard version of make.

Please provide the information mentioned above.  Also you should run
make with -d and see if it gives any clues.

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <address@hidden>          Find some GNU make tips at:
 http://www.gnu.org                      http://make.paulandlesley.org
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist