From mboxrd@z Thu Jan 1 00:00:00 1970 From: valdis.kletnieks@vt.edu (valdis.kletnieks at vt.edu) Date: Mon, 07 May 2018 15:43:40 -0400 Subject: kernel image path In-Reply-To: References: Message-ID: <23601.1525722220@turing-police.cc.vt.edu> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On Tue, 08 May 2018 00:45:25 +0530, Sumit Kumar said: > Sorry, there is a typo : I meant make -jX in a kernel sandbox. The same place it puts it if you don't use -jX. The exact answer will depend on what sort of sandbox you're using, and how exactly you're setting things up, and what system(s) you're building for. For example: on x86_64, by default the kernel ends up in arch/x86/boot/bzImage. If you have your build tree at /usr/src/linux, that means it ends up in /usr/src/linux/arch/x86/boot/bzImage. If you're building in a directory called '/source/kernel' inside a chroot based at '/containers/build-kernel', it will end up in /containers/build-kernel/source/kernel/arch/x86/boot/bzImage (as viewed from outside the chroot). Being more specific will require knowing what exactly you're trying to do.... -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 486 bytes Desc: not available URL: