Kerin Millar wrote: > Try without distcc, with a conservative MAKEOPTS setting and always > ensure that the toolchain is built in this order: binutils, gcc, glibc. > Failing that, you could bootstrap (be wary of /etc clobbering by > baselayout) or roll the affected package again in a "clean" chroot > before exporting it to the host.
I hadn't thought of that at all..the toolchain on the distcc server isn't hardened at all. I'll try it again local only. Thanks for pointing that out. Matt
