From: mjeanson@efficios.com (Michael Jeanson)
Subject: [lttng-dev] [PATCH babeltrace 1/2] sys/param.h is required for MAXNAMLEN on musl libc
Date: Mon, 30 May 2016 16:39:01 -0400 [thread overview]
Message-ID: <1464640742-24658-1-git-send-email-mjeanson@efficios.com> (raw)
Signed-off-by: Michael Jeanson <mjeanson at efficios.com>
---
formats/lttng-live/lttng-live.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/formats/lttng-live/lttng-live.h b/formats/lttng-live/lttng-live.h
index e00a51e..b315458 100644
--- a/formats/lttng-live/lttng-live.h
+++ b/formats/lttng-live/lttng-live.h
@@ -25,6 +25,7 @@
*/
#include <stdint.h>
+#include <sys/param.h>
#include "lttng-viewer-abi.h"
#define LTTNG_DEFAULT_NETWORK_VIEWER_PORT 5344
--
2.7.4
next reply other threads:[~2016-05-30 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 20:39 Michael Jeanson [this message]
2016-05-30 20:39 ` [lttng-dev] [PATCH babeltrace 2/2] Fix: strerror_r behavior is glibc specific Michael Jeanson
2016-05-31 5:53 ` Jérémie Galarneau
2016-05-31 5:53 ` [lttng-dev] [PATCH babeltrace 1/2] sys/param.h is required for MAXNAMLEN on musl libc Jérémie Galarneau
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=1464640742-24658-1-git-send-email-mjeanson@efficios.com \
--to=mjeanson@efficios.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