From: Christoph Egger <Christoph.Egger@amd.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: libxl: fix build failure for non-Linux platforms
Date: Thu, 26 May 2011 11:33:00 +0200 [thread overview]
Message-ID: <4DDE1E4C.8030603@amd.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
Move variable definitions into Linux-specific sections where they are
actually used. Fixes warning about unused variables.
Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
[-- Attachment #2: xen_tools_libxl.diff --]
[-- Type: text/plain, Size: 707 bytes --]
diff -r 87ff9d4de6f0 tools/libxl/libxl_exec.c
--- a/tools/libxl/libxl_exec.c Wed May 25 16:04:56 2011 +0200
+++ b/tools/libxl/libxl_exec.c Thu May 26 11:30:41 2011 +0200
@@ -41,8 +41,6 @@ static void check_open_fds(const char *w
const char *env_debug;
int debug;
int i, flags, badness = 0;
- char path[PATH_MAX];
- char link[PATH_MAX+1];
env_debug = getenv("_LIBXL_DEBUG_EXEC_FDS");
if (!env_debug) return;
@@ -53,6 +51,8 @@ static void check_open_fds(const char *w
for (i = 4; i < 256; i++) {
#ifdef __linux__
size_t len;
+ char path[PATH_MAX];
+ char link[PATH_MAX+1];
#endif
flags = fcntl(i, F_GETFD);
if ( flags == -1 ) {
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2011-05-26 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 9:33 Christoph Egger [this message]
2011-05-26 14:55 ` libxl: fix build failure for non-Linux platforms Ian Jackson
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=4DDE1E4C.8030603@amd.com \
--to=christoph.egger@amd.com \
--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.