From: nathan_lynch@mentor.com (Nathan Lynch)
Subject: [lttng-dev] [PATCH] babeltrace: address warnings and suggestions from autoscan
Date: Tue, 25 Oct 2016 09:51:20 -0500 [thread overview]
Message-ID: <1477407080-11055-1-git-send-email-nathan_lynch@mentor.com> (raw)
Autoscan warns:
autoscan: warning: missing AC_CHECK_HEADERS([sys/param.h]) wanted by:
formats/lttng-live/lttng-live.h:28
autoscan: warning: missing AC_FUNC_STRNLEN wanted by:
include/babeltrace/compat/string.h:59
Autoscan suggests adding AC_CONFIG_SRCDIR to make sure that the
correct source directory is used at configure time.
It also suggests adding checks for a handful of other headers.
Signed-off-by: Nathan Lynch <nathan_lynch at mentor.com>
---
configure.ac | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/configure.ac b/configure.ac
index 450e22491a67..c0e01e8bf640 100644
--- a/configure.ac
+++ b/configure.ac
@@ -5,6 +5,7 @@ AC_INIT([babeltrace],[2.0.0-pre],[jeremie dot galarneau at efficios dot com])
# http://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html
AC_SUBST([BABELTRACE_LIBRARY_VERSION], [1:0:0])
+AC_CONFIG_SRCDIR([bindings/python/babeltrace/python-complements.c])
AC_CONFIG_HEADERS([config.h])
AC_CONFIG_AUX_DIR([config])
AC_CONFIG_MACRO_DIR([m4])
@@ -52,13 +53,19 @@ AC_HEADER_STDBOOL
AC_CHECK_HEADERS([ \
fcntl.h \
float.h \
+ inttypes.h \
libintl.h \
limits.h \
malloc.h \
netdb.h \
netinet/in.h \
stddef.h \
+ stdint.h \
+ stdlib.h \
+ string.h \
+ sys/param.h \
sys/socket.h \
+ unistd.h \
])
if test ! -f "$srcdir/formats/ctf/metadata/ctf-parser.h"; then
@@ -112,6 +119,7 @@ AC_FUNC_MKTIME
AC_FUNC_MMAP
AC_FUNC_REALLOC
AC_FUNC_STRERROR_R
+AC_FUNC_STRNLEN
AC_CHECK_FUNCS([ \
atexit \
dirfd \
--
2.7.4
reply other threads:[~2016-10-25 14:51 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=1477407080-11055-1-git-send-email-nathan_lynch@mentor.com \
--to=nathan_lynch@mentor.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