linux-libc-headers: Upgrade 3.17 -> 3.17.7
PATCH 1/1 linux-libc-headers: Upgrade 3.17 -> 3.17.7
Whilst we don't usually take linux-libc-headers point release, 3.17.3 fixes a userspace header issue which caused gdb to fail to build on mips. We therefore may as well upgrade to the latest point release.
Signed-off-by Richard Purdie <[email protected]>
meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.17.7.bb new file +7 -0
@@ -0,0 +1,7 @@ +KORG_ARCHIVE_COMPRESSION = "xz" + +require linux-libc-headers.inc + +SRC_URI[md5sum] = "59cc7d0a236b08de743d6d9421f0f2c6" +SRC_URI[sha256sum] = "a3c8e6aee912bfd2e69abf9df5a06058434a8771bcaa1784b5980bf1b5298e1c" +
meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.17.bb deleted +0 -7
@@ -1,7 +0,0 @@ -KORG_ARCHIVE_COMPRESSION = "xz" - -require linux-libc-headers.inc - -SRC_URI[md5sum] = "fb30d0f29214d75cddd2faa94f73d5cf" -SRC_URI[sha256sum] = "f5153ec93c5fcd41b247950e6a9bcbc63fa87beafd112c133a622439a0f76251" -
Quoted 3 lines · Richard Purdie
Whilst we don't usually take linux-libc-headers point release, 3.17.3 fixes a userspace header issue which caused gdb to fail to build on mips. We therefore may as well upgrade to the latest point release.
Agreed. Not what we like to do .. but a full update is better than a single patch.
I have 3.18 headers in testing now, but we'll likely jump over that an go to 3.19+ to match the next kernel update.
Acked-by Bruce Ashfield <[email protected]>
Quoted 31 lines
Signed-off-by Richard Purdie <[email protected]>meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.17.7.bb new file +7
-0@@ -0,0 +1,7 @@ +KORG_ARCHIVE_COMPRESSION = "xz" + +require linux-libc-headers.inc + +SRC_URI[md5sum] = "59cc7d0a236b08de743d6d9421f0f2c6" +SRC_URI[sha256sum] = "a3c8e6aee912bfd2e69abf9df5a06058434a8771bcaa1784b5980bf1b5298e1c" +meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.17.bb deleted +0
-7@@ -1,7 +0,0 @@ -KORG_ARCHIVE_COMPRESSION = "xz" - -require linux-libc-headers.inc - -SRC_URI[md5sum] = "fb30d0f29214d75cddd2faa94f73d5cf" -SRC_URI[sha256sum] = "f5153ec93c5fcd41b247950e6a9bcbc63fa87beafd112c133a622439a0f76251" -