[Buildroot] [Bug 15551] New: Linux extensions are not applied to linux-headers package

[bugzilla@busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=15551

            Bug ID: 15551
           Summary: Linux extensions are not applied to linux-headers
                    package
           Product: buildroot
           Version: 2023.02
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: bradley.gamble@ncipher.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

Created attachment 9586
  --> https://bugs.busybox.net/attachment.cgi?id=9586&action=edit
Example of the difference between the linux and linux-headers trees following
an extension being applied.

Linux extensions are a mechanism for providing new features through
modification to the Linux kernel tree. This is usually in the form of patches
or new files from an out-of-tree source. (See Buildroot manual section 18.22.2.
linux-kernel-extensions).

Currently during a build the Linux extensions are applied to the linux source
tree, but not the linux-headers source tree. In comparison, the global and
Linux patch directories are applied to both the linux and linux-headers source
trees. This can lead issues where the source of the linux-headers does not
represent the kernel running on the target - For example, linux-headers is
consumed by most C libraries.

I have encountered this when attempting to write a patch that modifies an
applied kernel extension. The patch fails to apply to linux-headers as the
source files added by the extension do not exist.

This can be reproduced this by enabling a Linux extension (I've tested with
fbtft and ev3dev-linux-drivers) and performing a build, then comparing the
linux and linux-headers build directories - I have attached a diff example
showing the additions in one source tree but not the other.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot