From: Matthias Brugger <matthias.bgg@gmail.com>
To: Rajat Jain <rajatjain@juniper.net>,
"linux-newbie@vger.kernel.org" <linux-newbie@vger.kernel.org>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: x86_64_defconfig and i386_defconfig: What is the difference?
Date: Tue, 09 Sep 2014 16:06:07 +0200 [thread overview]
Message-ID: <540F094F.3040904@gmail.com> (raw)
In-Reply-To: <a06a49ac87e44c0d89d88514d7a28678@DM2PR05MB671.namprd05.prod.outlook.com>
On 09/09/14 09:58, Rajat Jain wrote:
> Hi,
>
> Can someone tell me if the i386 one is to be used when we want to build for a 32bit machine and the x86_64 is to be used for 64 bit machine?
You can build the kernel with any architecture for any architecture.
This is called cross-compiling. The homepage [0] should explain you how
to do that.
Cheers,
Matthias
[0] http://kernelnewbies.org/FAQ/KernelCrossCompilation
>
> Thanks,
>
> Rajat
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2014-09-09 14:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 7:58 x86_64_defconfig and i386_defconfig: What is the difference? Rajat Jain
2014-09-09 13:21 ` Valdis.Kletnieks
2014-09-09 14:19 ` Paul Bolle
2014-09-09 14:26 ` Valdis.Kletnieks
2014-09-09 14:06 ` Matthias Brugger [this message]
2014-09-09 14:27 ` Valdis.Kletnieks
2014-09-09 14:34 ` Abreu, Ian
2014-09-09 15:11 ` Rajat Jain
2014-09-09 15:28 ` Hubert CHAUMETTE
2014-09-09 17:51 ` Rajat Jain
2014-09-13 1:10 ` Peter Teoh
2014-09-13 3:44 ` Rajat Jain
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=540F094F.3040904@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-newbie@vger.kernel.org \
--cc=rajatjain@juniper.net \
/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