2.18.3 i486-pc-linux-gnu (protocols 1 and 2) (default port 3632)
built May 1 2007 10:25:30 (From the Ubuntu HH package)
All hosts running distcc are running Ubuntu Hardy Heron (8.04)
We're running gcc 2.95 and gcc 4.2.3
We use distcc for building the firmware for our product.
We deem the whole build to be a failure if the compiler emits even a single
warning message. It would be nice if there was an option to suppress
warnings from distcc about 'broken pipe, no route to host' type errors,
where somone in the farm rebooted their box part way through a build. This
way we wouldn't have to leave the boxes running over the weekend etc.
Original issue reported on code.google.com by
michael....@gmail.comon 15 Aug 2008 at 2:37