On Wed, Apr 7, 2010 at 11:34 AM, Natanael Copa <[email protected]> wrote: > On Wed, Apr 7, 2010 at 11:04 AM, Natanael Copa <[email protected]> > wrote: >> On Sun, Apr 4, 2010 at 4:42 PM, Austin Foxley <[email protected]> wrote: >>> On 04/03/2010 11:13 AM, Natanael Copa wrote: >>>> which means that stdout ends up with the error indicator set for some >>>> reason. I suspect this is a bug in uclibc-nptl. >>>> >>>> Interestingly enough, redirecting stdout to a file made the build complete. >>>> >>>> Any ideas on how to trace this down? >>> >>> Does this happen with the 0.9.31-rc? There aren't too many major >>> differences in >>> the stdio code between master and nptl. >> >> Ok, I tried with 0.9.31 and LINUXTHREADS_NEW and yes, same thing happens >> there. > > FWIW, it happens with make -j12 and not with -j1. it start to smell > like a race in Makefiles
Ok, I had 2 problems. One was that parallel builds does not work. Things didnt build in my 0.9.30.x environment. I have solved that now. But I still get write error in the 0.9.31 and nptl environments. So I suppose I need to start bisect? scares me since i belive there are other broken stuff along the way.. Other ideas how to dig this? -- Natanael Copa _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
