On Mon, Sep 8, 2014 at 1:43 AM, Paul Smith <psm...@gnu.org> wrote: > > Can you give some information on the type of hardware and operating > system you're using? >
Core i7, 64 bit, Ubuntu 12.04 LTS, SSD drive, dm-crypt, ext4. > That message means that while make was printing information to stdout > (note that the only things make itself prints to stdout during a normal > runtime are the "entering/exiting" lines, plus the command line it will > invoke for each rule where it isn't suppressed), the fprintf() command > got an error and wasn't able to write its output properly. > > This error comes from the C runtime library and denotes some kind of > error writing content to stdout. I don't see, offhand, how there could > be any bug in GNU make that would cause this problem. > > Is there anything unique or unusual about the way you're invoking make, > with respect to its stdout? Are you writing the output to a file using > redirection? Reading the output using a pipe (piping make's output to > another program)? Something else? > > Nope just straight 'make -j 12', nothing more. /cjk
_______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
