From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xensource.com
Subject: new compile error in gx_comm.c in xen-unstable
Date: Tue, 2 Nov 2010 11:34:14 +0100 [thread overview]
Message-ID: <20101102103414.GA13749@aepfle.de> (raw)
Hello,
there is a regression between xen-unstable rev 22314 and 22344,
gx_comm.c does not compile anymore due to -Werror, see below.
I think a simpe 'if (write(args..)) perror("write");' will be good enough.
Olaf
gcc -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -funwind-tables
-fasynchronous-unwind-tables -O1 -fno-omit-frame-pointer
-fno-optimize-sibling-calls -m64 -g -fno-strict-aliasing -std=gnu99
-Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement -O1 -fno-omit-frame-pointer
-fno-optimize-sibling-calls -m64 -g -fno-strict-aliasing -std=gnu99
-Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement -O1 -fno-omit-frame-pointer
-fno-optimize-sibling-calls -m64 -g -fno-strict-aliasing -std=gnu99
-Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF
.subdirs-install.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -O1
-fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
-Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD
-MF .gdbsx.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -O1
-fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
-Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD
-MF .all.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Werror
-Wmissing-prototypes -O1 -fno-omit-frame-pointer
-fno-optimize-sibling-calls -m64 -g -fno-strict-aliasing -std=gnu99
-Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF .gx_comm.o.d
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Werror -Wmissing-prototypes
-c -o gx_comm.o gx_comm.c
cc1: warnings being treated as errors
gx_comm.c: In function 'gx_getpkt':
gx_comm.c:230: error: ignoring return value of 'write', declared with attribute warn_unused_result
gx_comm.c:236: error: ignoring return value of 'write', declared with attribute warn_unused_result
next reply other threads:[~2010-11-02 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 10:34 Olaf Hering [this message]
2010-11-02 16:11 ` [PATCH]: gdbsx: Check return of write() Gianni Tedesco
2010-11-02 23:29 ` Bruce Edge
2010-11-03 8:09 ` Olaf Hering
2010-11-03 11:59 ` Ian Jackson
2010-11-03 14:10 ` Bruce Edge
2010-11-03 14:16 ` Olaf Hering
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=20101102103414.GA13749@aepfle.de \
--to=olaf@aepfle.de \
--cc=xen-devel@lists.xensource.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.