From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 2/2] Add missing <sys/types.h> include
Date: Thu, 19 Nov 2015 14:31:48 -0800 [thread overview]
Message-ID: <20151119143148.70764efa@xeon-e3> (raw)
In-Reply-To: <1447967140-29909-3-git-send-email-thomas.petazzoni@free-electrons.com>
On Thu, 19 Nov 2015 22:05:40 +0100
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> The u_intXX_t types are defined in <sys/types.h>, so it should be
> included before using those types. Otherwise, with certain C
> libraries, the build fails with:
>
> In file included from ../include/iptables.h:4:0,
> from m_ipt.c:18:
> ../include/iptables_common.h:47:16: error: unknown type name ‘u_int32_t’
> #define __le32 u_int32_t
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> include/iptables_common.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/iptables_common.h b/include/iptables_common.h
> index 9099667..2c27a4b 100644
> --- a/include/iptables_common.h
> +++ b/include/iptables_common.h
> @@ -43,6 +43,8 @@ extern char *lib_dir;
> extern void init_extensions(void);
> #endif
>
> +#include <sys/types.h>
> +
> #define __be32 u_int32_t
> #define __le32 u_int32_t
> #define __be16 u_int16_t
I would prefer you send this one through the iptables team
since that header file came from there.
prev parent reply other threads:[~2015-11-19 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 21:05 [PATCH iproute2 0/2] Build fixes for the musl C library Thomas Petazzoni
2015-11-19 21:05 ` [PATCH iproute2 1/2] Avoid in6_addr redefinition Thomas Petazzoni
2015-11-19 22:32 ` Stephen Hemminger
2015-11-19 21:05 ` [PATCH iproute2 2/2] Add missing <sys/types.h> include Thomas Petazzoni
2015-11-19 22:31 ` Stephen Hemminger [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=20151119143148.70764efa@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).