On Sun, Nov 6, 2011 at 12:33, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote: > Matt Madia wrote: >> One of GCC 2's >> build tools, `fixinc` / `fixincl` causes Buildbot to never realize the >> build has completed successfully. From what Oliver and I found out, >> fixinc will spawn a shell process, opens some pipes (or file >> descriptors) for communication, the calling process will crash, >> forcing the child to become its own process group and keep that pipe >> open. Build log output: http://pastebin.com/CfmXr42U (search for >> "*** barf *** barf ***" to see where the trouble starts) >> >> That is why Buildbot never acknowledges the gcc2 buildtools to be >> completed successfully. > > I think the easiest solutions would be to disable the fixincludes target in > gcc's Makefile (respectively Makefile.in). Just to make sure, that'd be buildtools/legacy/gcc/Makefile.in? Earlier today, I found a gcc-2.95.3-no-fixinc.patch patch, for removing fixinc -- but it doesn't seem to (manually) apply to our legacy/gcc directory. http://www.linuxfromscratch.org/patches/blfs/5.1/gcc-2.95.3-no-fixinc.patch from http://www.linuxfromscratch.org/blfs/view/5.1/general/gcc2.html --mmadia