From: Nathan Froyd <froydnj@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] check for PR_SET_NAME being defined
Date: Tue, 21 Jul 2009 07:15:08 -0700 [thread overview]
Message-ID: <1248185708-23715-1-git-send-email-froydnj@codesourcery.com> (raw)
Depending on what glibc/kernel headers you are compiling against,
PR_SET_NAME may or may not be defined. Do the right thing if
PR_SET_NAME isn't defined and skip setting the process name.
---
vl.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/vl.c b/vl.c
index ce213c2..61f7711 100644
--- a/vl.c
+++ b/vl.c
@@ -310,7 +310,7 @@ void hw_error(const char *fmt, ...)
static void set_proc_name(const char *s)
{
-#ifdef __linux__
+#if defined(__linux__) && defined(PR_SET_NAME)
char name[16];
if (!s)
return;
--
1.6.2.4
next reply other threads:[~2009-07-21 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 14:15 Nathan Froyd [this message]
2009-07-22 15:04 ` [Qemu-devel] [PATCH] check for PR_SET_NAME being defined Anthony Liguori
2009-07-22 15:49 ` Nathan Froyd
-- strict thread matches above, loose matches on Subject: below --
2009-08-03 14:32 Nathan Froyd
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=1248185708-23715-1-git-send-email-froydnj@codesourcery.com \
--to=froydnj@codesourcery.com \
--cc=qemu-devel@nongnu.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: 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).