| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <bda6d13a0607171543s26efde85q160b6b0df35aca40@mail.gmail.com> Date: Mon, 17 Jul 2006 15:43:53 -0700 From: "Joshua Hudson" <joshudson@...il.com> To: linux-kernel@...r.kernel.org Subject: make headers_install Just installed a new box, stock kernel didn't come up right. Installed linux-2.6.18-rc2 (had one hard time at that one as keyboard acted strange and network didn't work). The real fun is this: to begin kernel build, I had to restore toolchain to working order like so: # ln -s /usr/src/linux-2.6.18-rc2/include/linux /usr/include/linux # ln -s /usr/src/linux-2.6.18-rc2/include/asm-i386 /usr/include/asm # ln -s /usr/src/linux-2.6.18-rc2/include/asm-generic /usr/include/asm-generic Now the fun part: if I recall, I do make headers_install to install the kernel headers in the right place. Doing this before running those fix lines doesn't work because the build environment is broken. Doing this after looks like it would clobber the kernel headers. Solution? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists