make headers_install install system headers instead the ones from kernel source
Hi all,
"make headers_install INSTALL_HDR_PATH=<dest> ARCH=<arch>" should copy the headers from kernel source to <dest> (the toolchain) but it copys the headers from my system here. i have tested this command now with kernel 2.6.39 to 3.3-rc4 its same on every tested kernel version.
i have compared the filesize, for example /usr/include/linux/types.h with <dest>/include/linux/types.h and <kernel_src>/include/linux/types.h and the destination file is the same as the one in /usr/include.
I think its a big problem, because many embe
Quoted 11 lines · Stephan Raue
Hi all,
"make
headers_installINSTALL_HDR_PATH=<dest> ARCH=<arch>" should copy the headers from kernel source to <dest> (the toolchain) but it copys the headers from my system here.
i have tested this command now with kernel 2.6.39 to 3.3-rc4 its same on every tested kernel version.i have compared the filesize, for example
/usr/include/linux/types.hwith <dest>/include/linux/types.h and <kernel_src>/include/linux/types.h and the destination file is the same as the one in/usr/include.
Hi Stephan.
during the process of preparign the headers for use in user-space they undergo a processing.
On my system:
types.h in the kernel is 5733 bytes
The exported variant is 1430 bytes.
I think that in your case the reason why they match in size is because your distro uses a kernel exported types.h.
It should be simple to check. Just add a few lines to types.h in the kernel, around a line you know will be present in the user-space version. Export and see if the line is present.
Sam
thanks is working :-) sorry for the noise.
Stephan
Am 19.02.2012 22:57, schrieb Sam Ravnborg:
Quoted 19 lines
Hi Stephan.
during the process of preparign the headers for use in user-space they undergo a processing.
On my system:
types.hin the kernel is 5733 bytes
The exported variant is 1430 bytes.I think that in your case the reason why they match in size is because your distro uses a kernel exported
types.h.It should be simple to check. Just add a few lines to
types.hin the kernel, around a line you know will be present in the user-space version. Export and see if the line is present.Sam