From: Andrew Oakley <andrew@ado.is-a-geek.net>
To: xen-devel@lists.xensource.com
Subject: libxl compile errors
Date: Wed, 12 May 2010 19:44:19 +0100 [thread overview]
Message-ID: <4BEAF703.2000301@ado.is-a-geek.net> (raw)
I'm getting the following errors (within tools/libxl):
> xl.c: In function 'log_callback':
> xl.c:42: error: ignoring return value of 'write', declared with attribute warn_unused_result
> xl_cmdimpl.c: In function 'dolog':
> xl_cmdimpl.c:155: error: ignoring return value of 'write', declared with attribute warn_unused_result
> xl_cmdimpl.c: In function 'parse_config_data':
> xl_cmdimpl.c:503: error: ignoring return value of 'asprintf', declared with attribute warn_unused_result
> xl_cmdimpl.c: In function 'create_domain':
> xl_cmdimpl.c:959: error: ignoring return value of 'asprintf', declared with attribute warn_unused_result
> xl_cmdimpl.c:1083: error: ignoring return value of 'asprintf', declared with attribute warn_unused_result
> xl_cmdimpl.c:1099: error: ignoring return value of 'daemon', declared with attribute warn_unused_result
> xl_cmdimpl.c: In function 'migrate_domain':
> xl_cmdimpl.c:1832: error: ignoring return value of 'asprintf', declared with attribute warn_unused_result
> xl_cmdimpl.c: In function 'main_migrate':
> xl_cmdimpl.c:2168: error: ignoring return value of 'asprintf', declared with attribute warn_unused_result
In this case I guess we should try to continue the write if insufficient
data was written (could happen if the log file was a pipe for example).
It looks like there are some shared functions for this kind of thin in
libxl_internal.c, but I can't be sure if these should be used and what I
should be passing as ctx.
There may be more of these, I've just turned -Werror off to get it to
build for now. I think the warnings are created by recent versions libc
(or at least the headers). I'm using glibc-2.10.1 and gcc-4.3.4.
reply other threads:[~2010-05-12 18:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BEAF703.2000301@ado.is-a-geek.net \
--to=andrew@ado.is-a-geek.net \
--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 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 NNTP newsgroup(s).