Closed GoogleCodeExporter closed 9 years ago
here are the output of the configure script, and the call to make
Original comment by keller.eric
on 4 Sep 2009 at 8:47
Attachments:
configure with "--disable-Werror".
Original comment by fergus.h...@gmail.com
on 4 Sep 2009 at 9:26
I assume it won't be fixed then :) or should I send some patch?
Original comment by keller.eric
on 4 Sep 2009 at 9:36
By all means, please send a patch!
Original comment by fergus.h...@gmail.com
on 4 Sep 2009 at 9:51
Hi Fergus,
I have some question left about distcc coding norm:
- do you have any guide line concerning exception handling in the project?
- what's about perror and errno when a function encounters an error?
- do you use doxygen comment ? (well some part of the code is uncommented)
I will send you some patch as soon as I get a better idea how your project is
managed!
Best regrads
Original comment by keller.eric
on 7 Sep 2009 at 8:41
another question concerning the header files... Is there a reason why not
preventing
the multiple header includes?
for ex.: util.h
#ifndef UTIL_H_
# define UTIL_H_
...
# endif // !UTIL_H_
Original comment by keller.eric
on 7 Sep 2009 at 9:40
Distcc is written in C, not C++.
So exception handling is done with return values.
Most functions return zero on success or a code from exitcode.h on error, and
such
errors are manually propagated up to the caller, taking care to deallocate any
dynamically allocated local variables in the error cases.
Errors should be logged with the logging functions used throughout distcc; I
don't
recall the names off-hand, but you can find that easily by browsing through the
distcc sources. Error messages should always include strerror(errno) in cases
where
errno was set by the call that failed.
As for the lack of include guards in header files... AFAIK there is no good
reason
for that.
Original comment by fergus.h...@gmail.com
on 9 Sep 2009 at 2:39
Just a comment that the solution suggested earlier in this thread of
configure with "--disable-Werror".
is good enough for me, so if you're not planning to step up with a patch, I'll
close
this issue.
Original comment by fergus.h...@gmail.com
on 1 Dec 2009 at 4:41
Original comment by fergus.h...@gmail.com
on 2 Mar 2010 at 8:04
For "make deb" this worked for me: make deb CFLAGS="-Wno-erro"
Original comment by leonboga...@gmail.com
on 27 Oct 2010 at 8:50
Original issue reported on code.google.com by
keller.eric
on 4 Sep 2009 at 8:39