Skip to content

RFC v2: provide 3.0.x and 3.1 libc headers

Bruce Ashfield openembedded-core 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 1 replyIn review

Changes since v1 from the cover letter

- factored common code out into the .inc file. Captured in patch 1/2
- patch 2/2 is the introduction of the new headers

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2linux-libc-headers: factor common code into linux-libc-headers.incmeta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc meta/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.37.2.bb meta/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.39.bb+46 -910 replies
2/2linux-libc-headers: provide 3.0.x and 3.1 headersmeta/conf/distro/include/tcmode-default.inc meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.0.8.bb +1 more+33 -41 reply

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/2] RFC v2: provide 3.0.x and 3.1 libc headers

Richard,

Here's a quick respin of the series to factor out some code.

Changes since v1:

- factored common code out into the .inc file. Captured in patch 1/2
- patch 2/2 is the introduction of the new headers

Original Email is included below:

Here's a RFC patch for updating the toolchain linux-libc headers to 3.x variants.

The reason I'm calling it a RFC is:

- I wrote some anonymous python code (and I'm no python coder) to deal with 2.6 / 3.0 tgz location differences. This could have also been done with a variable set in the recipes and used by the .inc. I wasn't sure of the preferred approach, hence the RFC. I'll take no offense corrections here.

- I changed the .inc, but didn't bump the PR of the existing recipes and didn't remove the existing 2.6 variants. If either of these should have been done, let me know and I'll respin.

- I bumped the default to be 3.1. If that's too agressive for the default, and we'd prefer 3.0.8, let me know and I'll respin.

I built and booted all the qemu machines with the 3.1 kernel headers. So from the testing I was able to do, this looks to be safe and ready to go.

This is based on my yocto repo, I also did the changes in my oe-core repository, but I don't have a oe-core contrib branch that I could push to, so I chose to send the yocto variant. If someone points me to who I email for an oe-core contrib branch, I can push that variant as well.

Cheers,

Bruce

The following changes since commit fc94f925e848684244a38dcffe15cb1192dfbed8:
Martin Jansa (1):
libxml-parser-perl, libxml-simple-perl, expat, sgmlspl-native, git: bump PR to rebuild after perl upgrade

are available in the git repository at:

git://git.pokylinux.org/poky-contrib zedd/libc-headers-v2
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/libc-headers-v2

Bruce Ashfield (2):
linux-libc-headers: factor common code into linux-libc-headers.inc
linux-libc-headers: provide 3.0.x and 3.1 headers

 meta/conf/distro/include/tcmode-default.inc        |    2 +-
 .../linux-libc-headers/linux-libc-headers.inc      |   61 +++++++++++++++++++-
 .../linux-libc-headers_2.6.37.2.bb                 |   46 +--------------
 .../linux-libc-headers_2.6.39.bb                   |   47 +---------------
 .../linux-libc-headers/linux-libc-headers_3.0.8.bb |    9 +++
 .../linux-libc-headers/linux-libc-headers_3.1.bb   |    9 +++
 6 files changed, 79 insertions(+), 95 deletions(-)
 create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.0.8.bb
 create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.1.bb