summaryrefslogtreecommitdiffstats
path: root/package/kmod/0002-shared-util.c-assert_cc-can-only-be-used-inside-func.patch
diff options
context:
space:
mode:
authorAdam Duskett <aduskett@greenlots.com>2018-08-20 09:53:29 -0700
committerThomas Petazzoni <thomas.petazzoni@bootlin.com>2018-08-20 20:24:53 +0200
commit68a29508974cf1de56b73bcf400944b2e6e2a705 (patch)
tree0770683754ab4be51a8ab090d29c7ca44779f223 /package/kmod/0002-shared-util.c-assert_cc-can-only-be-used-inside-func.patch
parentf8fd7dd182de653d308401e3d2f70adb8e2d166b (diff)
downloadbuildroot-68a29508974cf1de56b73bcf400944b2e6e2a705.tar.gz
buildroot-68a29508974cf1de56b73bcf400944b2e6e2a705.zip
kmod: bump to 25
With the introduction of Python 3.7.0 in commit 6e7e733f3bbd8669e02f097ad5a49ba565e1718e, kmod needs to be bumped to version 25. Fixes: http://autobuild.buildroot.net/results/5ba7f2e9d0802890e275f7da160ad0aad87b6f56/ Signed-off-by: Adam Duskett <aduskett@greenlots.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Diffstat (limited to 'package/kmod/0002-shared-util.c-assert_cc-can-only-be-used-inside-func.patch')
-rw-r--r--package/kmod/0002-shared-util.c-assert_cc-can-only-be-used-inside-func.patch56
1 files changed, 0 insertions, 56 deletions
diff --git a/package/kmod/0002-shared-util.c-assert_cc-can-only-be-used-inside-func.patch b/package/kmod/0002-shared-util.c-assert_cc-can-only-be-used-inside-func.patch
deleted file mode 100644
index 09fe252420..0000000000
--- a/package/kmod/0002-shared-util.c-assert_cc-can-only-be-used-inside-func.patch
+++ /dev/null
@@ -1,56 +0,0 @@
-From 7cd698eb31059012305d8bb7516577c8cd383e32 Mon Sep 17 00:00:00 2001
-From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-Date: Sat, 3 Jun 2017 16:52:37 +0200
-Subject: [PATCH] shared/util.c: assert_cc() can only be used inside functions
-
-shared/macro.h has two versions of assert_cc, one that uses gcc
-_Static_assert(), which requires recent enough gcc versions, and one
-that uses a fake array to trigger a build error. The latter can only
-work inside functions, so assert_cc() should only be used inside
-functions.
-
-Fixes the following build failure when building kmod with old gcc
-versions such as gcc 4.3.x:
-
-shared/util.c:52: error: expected identifier or '(' before 'do'
-shared/util.c:52: error: expected identifier or '(' before 'while'
-
-Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
----
- shared/util.c | 6 ++++--
- 1 file changed, 4 insertions(+), 2 deletions(-)
-
-diff --git a/shared/util.c b/shared/util.c
-index 9de080a..fd2028d 100644
---- a/shared/util.c
-+++ b/shared/util.c
-@@ -49,8 +49,6 @@ static const struct kmod_ext {
- { }
- };
-
--assert_cc(EAGAIN == EWOULDBLOCK);
--
- /* string handling functions and memory allocations */
- /* ************************************************************************ */
-
-@@ -201,6 +199,8 @@ ssize_t read_str_safe(int fd, char *buf, size_t buflen)
- size_t todo = buflen - 1;
- size_t done = 0;
-
-+ assert_cc(EAGAIN == EWOULDBLOCK);
-+
- do {
- ssize_t r = read(fd, buf + done, todo);
-
-@@ -226,6 +226,8 @@ ssize_t write_str_safe(int fd, const char *buf, size_t buflen)
- size_t todo = buflen;
- size_t done = 0;
-
-+ assert_cc(EAGAIN == EWOULDBLOCK);
-+
- do {
- ssize_t r = write(fd, buf + done, todo);
-
---
-2.7.4
-
OpenPOWER on IntegriCloud