From: Steve Dickson <SteveD@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>, libtirpc-devel@lists.sourceforge.net
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH [libtirpc]] include stdarg.h when used
Date: Tue, 12 Aug 2014 10:52:15 -0400 [thread overview]
Message-ID: <53EA2A1F.7020006@RedHat.com> (raw)
In-Reply-To: <1407827532-31173-1-git-send-email-vapier@gentoo.org>
On 08/12/2014 03:12 AM, Mike Frysinger wrote:
> The debug.h header uses va_list but doesn't include stdarg.h which
> can lead to random build failures.
>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Committed...
steved.
> ---
> src/debug.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/src/debug.h b/src/debug.h
> index afc8d57..c971ac3 100644
> --- a/src/debug.h
> +++ b/src/debug.h
> @@ -21,6 +21,8 @@
>
> #ifndef _DEBUG_H
> #define _DEBUG_H
> +
> +#include <stdarg.h>
> #include <syslog.h>
>
> extern int libtirpc_debug_level;
>
prev parent reply other threads:[~2014-08-12 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 7:12 [PATCH [libtirpc]] include stdarg.h when used Mike Frysinger
2014-08-12 14:52 ` Steve Dickson [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=53EA2A1F.7020006@RedHat.com \
--to=steved@redhat.com \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.org \
--cc=vapier@gentoo.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).