From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Problem in compiling kernel
Date: Tue, 28 Jun 2011 22:21:53 +0700 [thread overview]
Message-ID: <BANLkTi=9QOjOVH_N-x82rzV3qAJ-8Crpzg@mail.gmail.com> (raw)
In-Reply-To: <CAEnQRZDt-gabeAHF5qMxwHoJ6_4yrj7UQ8gsS_vZwSs4nxdS9g@mail.gmail.com>
On Tue, Jun 28, 2011 at 18:29, Daniel Baluta <daniel.baluta@gmail.com> wrote:
> Please keep kernelnewbies to CC:, so that other can read about this problem
> if they hit it.
>
> The reason for which it didn't work is that you haven't set a valid
> cross-compiler
> prefix in CROSS_COMPILE
>
> When you set a cross-compiler prefix, the value stored in CROSS_COMPILE is
> concatenated with the name of each tool used to compile your kernel.
>
> For example, objdump will be used as ${CROSS_COMPILE}objdump. You set
> CROSS_COMPILE=Y, and the tool to be used is now named Yobjdump, which
> obviously doesn't exist.
Great job man!!! Your explanation also clearly explain to me how this
option works. Thanks!
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2011-06-28 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 16:21 Problem in compiling kernel Ponkumaran Annadurai
2011-06-27 17:19 ` Mulyadi Santosa
2011-06-27 17:23 ` Daniel Baluta
[not found] ` <BANLkTim0BX-qwbKms4WaRwd80XuH0g_8sg@mail.gmail.com>
2011-06-28 7:43 ` Daniel Baluta
[not found] ` <BANLkTi=09B=FoHVuSoCgROSdO8bkr=2+bQ@mail.gmail.com>
2011-06-28 11:29 ` Daniel Baluta
2011-06-28 12:18 ` Ponkumaran Annadurai
2011-06-28 17:39 ` Ponkumaran Annadurai
2011-06-28 18:08 ` Daniel Baluta
2011-06-29 6:28 ` Mulyadi Santosa
2011-06-29 7:12 ` Daniel Baluta
2011-06-29 13:37 ` Ponkumaran Annadurai
2011-06-29 13:56 ` Daniel Baluta
2011-06-28 15:21 ` Mulyadi Santosa [this message]
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='BANLkTi=9QOjOVH_N-x82rzV3qAJ-8Crpzg@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--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).