This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/53679] Build failure in libgo
- From: "allan at archlinux dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 15 Jun 2012 22:36:54 +0000
- Subject: [Bug go/53679] Build failure in libgo
- Auto-submitted: auto-generated
- References: <bug-53679-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53679
--- Comment #3 from Allan McRae <allan at archlinux dot org> 2012-06-15 22:36:54 UTC ---
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)) {}