[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Welcome to the Slackware Documentation Project
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
howtos:slackware_admin:cross_compiling_the_linux_kernel [2018/06/01 22:23 (UTC)] – [Kernel preparation] bifferos | howtos:slackware_admin:cross_compiling_the_linux_kernel [2018/06/01 22:36 (UTC)] – [Kernel compilation] bifferos |
---|
<code>$ make bzImage CROSS_COMPILE=i486-linux- ARCH=i386</code> | <code>$ make bzImage CROSS_COMPILE=i486-linux- ARCH=i386</code> |
| |
Copy the built kernel to a 32-bit machine and it should boot. If you want to compile/install the modules as well, just make sure you don't forget to use the same CROSS_COMPILE and ARCH variables every time you specify the make commands, everything should use the cross-compiler: 'make modules', 'make modules_install' and so on. You will probably get away without these appended for some commands like 'make clean', but it's safest to just include them whenever you do anything on that kernel, they certainly won't hurt. | Copy the built kernel to a 32-bit machine and it should boot. If you want to compile/install the modules as well, just make sure you don't forget to use the same CROSS_COMPILE and ARCH variables every time you specify the make commands, everything should use the cross-compiler: |
| |
| <code>$ make modules CROSS_COMPILE=i486-linux- ARCH=i386 |
| $ make modules_install CROSS_COMPILE=i486-linux- ARCH=i386</code> |
| |
| and so on. You will probably get away without these appended for some commands like 'make clean', but it's safest to just include them whenever you do any work on that kernel, they certainly won't hurt. |
| |
| |