Since revision 187850, I get build failures for libgo due to the use of -Werror and not checking the return value of write: /build/src/gcc-4.7.1/libgo/runtime/print.c: In function 'gwrite': /build/src/gcc-4.7.1/libgo/runtime/print.c:20:3: error: ignoring return value of 'write', declared with attribute warn_unused_result [-Werror=unused-result] cc1: all warnings being treated as errors
Created attachment 27626 [details] Allows me to compile it, I do know if there's any value if checking for errors writing to stderr
Actually this is due to your modifications to gcc to enable fority by default and glibc's bad idea that write needs to be check for error after each write.
Just to be clear, I have not modified the compiler to enable fortify by default, but it is in my CFLAGS... As this is the only place that glibc's decision to enforce a check on the return value of write causes the build to fail with these CFLAGS, it would be nice to include the posted work-around, or equivalently: - runtime_write(2, v, n) + if(runtime_write(2, v, n)) {}
another alternative woul dbe to fix the libgo/ subdir to respect --disable-werror like all the other places in the gcc tree
posted a patch here to add --disable-werror: http://gcc.gnu.org/ml/gcc-patches/2012-12/msg01379.html we need this for ChromiumOS ...
Ian has pushed the patch to trunk: http://gcc.gnu.org/viewcvs?view=revision&revision=195482
This has been fixed.