From: valdis.kletnieks@vt.edu (valdis.kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kernel image path
Date: Mon, 07 May 2018 15:43:40 -0400 [thread overview]
Message-ID: <23601.1525722220@turing-police.cc.vt.edu> (raw)
In-Reply-To: <CACFOd6Whn_FwY5iZqTsZT_XzySMJPX_2yiOfjbdAJwFA5vmCfg@mail.gmail.com>
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: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20180507/c789b544/attachment.sig>
next prev parent reply other threads:[~2018-05-07 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 19:09 kernel image path Sumit Kumar
2018-05-07 19:15 ` Sumit Kumar
2018-05-07 19:43 ` valdis.kletnieks at vt.edu [this message]
2018-05-07 21:42 ` Sumit Kumar
2018-05-08 4:33 ` valdis.kletnieks at vt.edu
2018-05-08 19:07 ` Sumit Kumar
2018-05-08 19:24 ` valdis.kletnieks at vt.edu
2018-05-08 20:21 ` Sumit Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23601.1525722220@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).