From: Serhey Popovych <serhe.popovych@gmail.com>
To: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] Fix compilation with kernel headers < 3.4
Date: Mon, 26 Feb 2018 21:27:10 +0200 [thread overview]
Message-ID: <f8a3af91-b6e5-8081-6fe7-b8dd3d6f4166@gmail.com> (raw)
In-Reply-To: <20180226185112.9657-1-thomas.de_schampheleire@nokia.com>
[-- Attachment #1.1: Type: text/plain, Size: 2095 bytes --]
Thomas De Schampheleire wrote:
> Since commit 596b1c94aa38e21b7a8c8562e8b61ccb744255d2, iproute2 uses types
> __kernel_long_t and __kernel_ulong_t but does not provide internal
> definitions for it.
I tried one time to build with headers from 3.2 (last supported LTS at
the moment) and found that AF_VSOCK is missing. As result of defining
AF_VSOCK we need to adjust AF_MAX. Not sure this is correct at all but
this helps to build with old headers.
diff --git a/misc/ss.c b/misc/ss.c
index 49f9c49..2849bc6 100644
--- a/misc/ss.c
+++ b/misc/ss.c
@@ -46,6 +46,16 @@
#include <linux/sctp.h>
#include <linux/vm_sockets_diag.h>
+#ifndef AF_VSOCK
+#define AF_VSOCK 40
+#if defined(AF_MAX) && AF_MAX < 41
+#undef AF_MAX
+#endif
+#ifndef AF_MAX
+#define AF_MAX 41
+#endif /* AF_MAX */
+#endif /* AF_VSOCK */
>
> This means that compilation using kernel headers that are older than 3.4
> (where these types were added) will fail. This situation may be uncommon for
> native compilation, but not uncommon for cross compilation where the
> toolchains may be a bit older.
>
> Provide the necessary types internally if not provided by the kernel
> headers to fix compilation in such cases.
>
> Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
> ---
> include/uapi/linux/posix_types.h | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/include/uapi/linux/posix_types.h b/include/uapi/linux/posix_types.h
> index 9a7a740b..60f3d378 100644
> --- a/include/uapi/linux/posix_types.h
> +++ b/include/uapi/linux/posix_types.h
> @@ -35,4 +35,13 @@ typedef int __kernel_mqd_t;
>
> #include <asm/posix_types.h>
>
> +/* in case the kernel header asm/posix_types.h is too old (< 3.4) to provide
> + * __kernel_long_t, provide it here */
> +#ifndef __kernel_long_t
> +typedef long __kernel_long_t;
> +#endif
> +#ifndef __kernel_ulong_t
There is no such define. Only __kernel_long_t.
> +typedef unsigned long __kernel_ulong_t;
> +#endif
> +
> #endif /* _LINUX_POSIX_TYPES_H */
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2018-02-26 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 18:51 [PATCH iproute2] Fix compilation with kernel headers < 3.4 Thomas De Schampheleire
2018-02-26 18:58 ` Stephen Hemminger
2018-02-26 19:21 ` Thomas De Schampheleire
2018-02-26 19:27 ` Serhey Popovych [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-26 19:46 Serhey Popovych
2018-02-26 19:48 ` Serhey Popovych
2018-02-26 20:32 ` Thomas De Schampheleire
2018-02-26 20:38 ` Serhey Popovych
2018-02-27 10:16 ` Thomas De Schampheleire
2018-02-27 12:21 ` Serhey Popovych
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=f8a3af91-b6e5-8081-6fe7-b8dd3d6f4166@gmail.com \
--to=serhe.popovych@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=thomas.de_schampheleire@nokia.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).