public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "allan at archlinux dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/53679] New: Build failure in libgo Date: Fri, 15 Jun 2012 07:50:00 -0000 [thread overview] Message-ID: <bug-53679-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53679 Bug #: 53679 Summary: Build failure in libgo Classification: Unclassified Product: gcc Version: 4.7.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go AssignedTo: ian@airs.com ReportedBy: allan@archlinux.org 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
next reply other threads:[~2012-06-15 7:50 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-15 7:50 allan at archlinux dot org [this message] 2012-06-15 15:52 ` [Bug go/53679] " safety0ff.bugz at gmail dot com 2012-06-15 15:53 ` safety0ff.bugz at gmail dot com 2012-06-15 16:42 ` pinskia at gcc dot gnu.org 2012-06-15 22:37 ` allan at archlinux dot org 2012-06-27 23:09 ` vapier at gentoo dot org 2012-12-23 23:32 ` vapier at gentoo dot org 2013-01-26 3:21 ` vapier at gentoo dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-53679-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).