On Sun, Nov 13, 2011 at 19:37, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote: > Matt Madia wrote: >> On Sun, Nov 6, 2011 at 12:33, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote: >> > 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? > > No, the one in .../gcc/gcc/. > >> 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 > > Doesn't look too bad. I would probably have tried to remove the dependencies > on the target(s), but maybe this is the easier solution. It works too! Buildbot detected the successful completion of buildtools. Should I test it on some other host OS's or commit it as-is? Oh also, Urias confirmed that touching the gcc/cp/parse.c (?) file worked as hoped. So, during the week, I'll make time to integrate that into the build_cross_tools script --mmadia