search

GwenNelson / distcc

Automatically exported from code.google.com/p/distcc
GNU General Public License v2.0
0 stars 0 forks source link

Suppress Warnings #18

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
 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.com on 15 Aug 2008 at 2:37

GoogleCodeExporter commented 9 years ago 
Please feel free to provide a patch...

Original comment by fergus.h...@gmail.com on 2 Dec 2008 at 9:47

GoogleCodeExporter commented 9 years ago 
By the way, how are you detecting when the compiler emits a single warning 
message?
Are you using gcc's -Werror option and then checking the exit status returned 
from
gcc?  Would that method be sufficient?  If not, why not?

Original comment by fergus.h...@gmail.com on 3 Dec 2008 at 12:07

GoogleCodeExporter commented 9 years ago 
You're right, I've been slack about hacking at the distcc code and patching it
myself, but to be a little bit frank, I don't have the time to do that at work 
for
such a low priority task. At the moment, yes we do use the Werror flag, but 
it's not
as simple as checking the exit status.  Our build is quite complicated and we 
have
written a ruby script to do it and we grab the output of gcc directly and parse 
that
as we go.  Through the magic of regexes we look for errors in the output as 
well as
checking the exit status of gcc.  This isn't a massive problem, just a 'nice to 
have'
so I might look into it on the weekend even and then post a patch if I come up 
with
something useful.  But to be fair, the odds of me sitting in the sun all day 
rather
than program  pretty high.  (The southern hemisphere is awesome at this time of
year!)  Once again, don't stress about it.  I'd forgotten until this email 
showed up
in my inbox.  Thanks though, every piece of help is appreciated!

Original comment by michael....@gmail.com on 3 Dec 2008 at 8:52

GoogleCodeExporter commented 9 years ago

Original comment by fergus.h...@gmail.com on 8 Dec 2008 at 11:38