Difference between revisions of "Bering-uClibc 7.x - Developer Guide - Providing kernel headers"
From bering-uClibc
Line 18: | Line 18: | ||
As we are moving away from the tarball code containers to a true git environment creating these tarballs has become obsolete. | As we are moving away from the tarball code containers to a true git environment creating these tarballs has become obsolete. | ||
− | Please note, that toolchains can support different kernel versions, which may be useful especially in transitions to | + | '''Please note, that toolchains can support different kernel versions, which may be useful especially in transitions to newer versions, where not all toolchains will be supported immediately. It is advised to keep the kernel headers for the oldest kernel a toolchain uses.''' |
---- | ---- | ||
{| summary="Navigation footer" width="100%" | {| summary="Navigation footer" width="100%" |
Revision as of 18:59, 2 October 2019
Providing kernel headers | ||
---|---|---|
Prev | Bering-uClibc 7.x - Developer Guide | Next |
Building the kernel headers tarball is different from building all other Packages.
The kernel headers are a requirement to build the toolchain. The command
./buildtool.pl headers linux
builds those headers in the directory headers
in the buildtool root directory and creates a link in repo/toolchain/linux-headers
.
As we are moving away from the tarball code containers to a true git environment creating these tarballs has become obsolete.
Please note, that toolchains can support different kernel versions, which may be useful especially in transitions to newer versions, where not all toolchains will be supported immediately. It is advised to keep the kernel headers for the oldest kernel a toolchain uses.
Prev | Up | Next |