From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: "marcel@holtmann.org" <marcel@holtmann.org>
Subject: Re: [PATCH BlueZ v2 1/1] build: Check if explicit_bzero is missing
Date: Wed, 3 Apr 2019 17:47:03 +0000 [thread overview]
Message-ID: <1554313622.20501.0.camel@intel.com> (raw)
In-Reply-To: <20190401184518.1816-1-brian.gix@intel.com>
On Mon, 2019-04-01 at 11:45 -0700, Brian Gix wrote:
> This check gets around the redefinition of explicit_bzero in ELL
>
> In file included from ell/random.c:34:0:
> ell/missing.h:59:20: error: static declaration of ‘explicit_bzero’ follows non-static declaration
> static inline void explicit_bzero(void *s, size_t n)
> ^~~~~~~~~~~~~~
> In file included from ./ell/util.h:26:0,
> from ell/private.h:26,
> from ell/random.c:33:
> /usr/include/string.h:435:13: note: previous declaration of ‘explicit_bzero’ was here
> extern void explicit_bzero (void *__s, size_t __n) __THROW __nonnull ((1));
> ^~~~~~~~~~~~~~
> ---
> configure.ac | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/configure.ac b/configure.ac
> index ae64ddc0f..0afe1e6db 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -46,6 +46,8 @@ MISC_FLAGS
> AC_ARG_ENABLE(threads, AC_HELP_STRING([--enable-threads],
> [enable threading support]), [enable_threads=${enableval}])
>
> +AC_CHECK_FUNCS(explicit_bzero)
> +
> AC_CHECK_FUNC(signalfd, dummy=yes,
> AC_MSG_ERROR(signalfd support is required))
>
Patch Applied
prev parent reply other threads:[~2019-04-03 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 18:45 [PATCH BlueZ v2 1/1] build: Check if explicit_bzero is missing Brian Gix
2019-04-03 17:47 ` Gix, Brian [this message]
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=1554313622.20501.0.camel@intel.com \
--to=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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 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.