search for: kernelheaders

...le included from usr/klibc/arch/mips/crt0.S:11: usr/include/arch/mips/machine/asm.h:8:24: error: asm/regdef.h: No such file or directory usr/include/arch/mips/machine/asm.h:9:21: error: asm/asm.h: No such file or directory i'm not sure if you want to export both headers in the make kernelheaders target or if it is the fault of klibc to assume that those are available? -- maks

...commit 69c8f52b. This causes the following message to be emitted when building klibc (which is designed to use kernel headers explicitly): /usr/local/src/git/linux-2.6//include/linux/types.h:13:2: warning: #warning "Attempt to use kernel headers from user space, see http://kernelnewbies.org/KernelHeaders" In order to silence this warning, make sure we define __EXPORTED_HEADERS__ when building klibc userland. Signed-off-by: Mike Waychison <mikew at google.com> --- scripts/Kbuild.klibc | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/scripts/Kbuild.klibc b/scrip...

H. Peter Anvin dixit: >You should be using the output of "make headers_install" to build klibc. Hm. Can we catch that somehow? Like? #ifdef using_uninstalled_kernel_headers # error Go RTFM! #endif ? in the klibc sources, centrally somewhere? Ideally, a klibc header that?d also be included when using klcc to build some? thing, so that both klibc-build time and klibc-use time would

Hello CentOS users, Currently I have compiled kernel version 4.19.37, which the source is from kernel.org. I compiled the kernel by following steps: - get the kernel tarball and unpack it - install prerequisties as described in https://wiki.centos.org/HowTos/Custom_Kernel (in addition bc and openssl-devel) - copy the kernel configuration: $ cp /boot/config-3.10.0-957.21.3.el7.x86_64

...ion > (3.10.0-957.21.3.el7). Is it safe to continue installing from compiled RPM package above, or install kernel manually? In general, you want to keep the distro's kernel-headers unless you also plan to play with glibc. You may find the following article useful: https://kernelnewbies.org/KernelHeaders Akemi

...the arse, and if that's the case, why do you even have variables referring to the kernel source at all? KLIBCKERNELSRC is a local copy of the kernel for our build purposes. Aside from the build spewing: #warning "Attempt to use kernel headers from user space, see http://kernelnewbies.org/KernelHeaders" There is nothing wrong with the build, and it passes all of your testcases (we block some of them as they would fail in the non-root restricted environment, but they pass outside that). http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-libs/klibc/klibc-2.0.3-r1.ebuild?revision=1.1&...

....3.el7). Is it safe to continue installing from compiled RPM package above, or install kernel manually? > In general, you want to keep the distro's kernel-headers unless you > also plan to play with glibc. You may find the following article > useful: > > https://kernelnewbies.org/KernelHeaders > > Akemi > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos So is it safe to install kernel RPMs generated by compilation from kernel.org tarball, or should I stick to manual install?

...he > case, why do you even have variables referring to the kernel source at > all? KLIBCKERNELSRC is a local copy of the kernel for our build > purposes. > > Aside from the build spewing: > #warning "Attempt to use kernel headers from user space, see http://kernelnewbies.org/KernelHeaders" > There is nothing wrong with the build, and it passes all of your > testcases (we block some of them as they would fail in the non-root > restricted environment, but they pass outside that). > > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-libs/klibc/klibc-2.0....