Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] First rootfile system build using buildroot
Date: Mon, 31 Aug 2015 22:45:44 +0200	[thread overview]
Message-ID: <20150831224544.22ddf67b@free-electrons.com> (raw)
In-Reply-To: <CAKpDV8uVJjtssJDEx4knqtATvjXzy+kdKtwBoWWLcv-9v4cikg@mail.gmail.com>

Dinesh,

On Mon, 31 Aug 2015 20:07:50 +0530, Dinesh Guleria wrote:

> I am new to buildroot. I am Trying to learn it. I am following this manual.
> http://buildroot.uclibc.org/downloads/manual/manual.html
> 
> So i have started with Rpi.
> 
> I am trying to build my own rootfile system for RPI using buildroot.
> 
> I have downloaded following cross compiler folder from git :--
> https://github.com/raspberrypi/tools/tree/master/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian
> as mentioned in this link :--
> http://hertaville.com/2012/09/28/development-environment-raspberry-pi-cross-compiler/

If you're a beginner with Buildroot, don't start with a customer
compiler. Either use the one generated by Buildroot ("Buildroot
toolchain") or use a pre-defined external toolchain ("Sourcery
CodeBench 2014.05" if you're using the RPi 1, or "Linaro" if you're
using the RPi 2).

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2015-08-31 20:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 14:37 [Buildroot] First rootfile system build using buildroot Dinesh Guleria
2015-08-31 15:18 ` Dinesh Guleria
2015-08-31 15:53   ` Lee, Tommy
2015-08-31 17:17     ` Dinesh Guleria
2015-08-31 20:58       ` Lee, Tommy
2015-09-01  1:09         ` Dinesh Guleria
2015-09-01  6:58           ` Thomas Petazzoni
2015-09-01 11:25             ` Dinesh Guleria
2015-09-01 12:02               ` Dinesh Guleria
2015-09-01 12:14                 ` Vicente Olivert Riera
2015-09-01 13:23                   ` Dinesh Guleria
2015-09-01 15:54           ` Lee, Tommy
2015-09-01 15:57             ` Lee, Tommy
     [not found]               ` <CAKpDV8uny8GAJrEkEBmMdcboOrGuVQ4G09KRtL9yuvgH1XKE=Q@mail.gmail.com>
2015-09-01 17:45                 ` Lee, Tommy
2015-09-02  0:29                   ` Dinesh Guleria
2015-09-02  3:38                     ` Baruch Siach
2015-09-02 11:06                       ` Dinesh Guleria
2015-09-02 11:47                         ` Baruch Siach
2015-09-02 13:54                           ` Dinesh Guleria
2015-09-02 13:59                             ` Vicente Olivert Riera
2015-09-02 14:51                               ` Dinesh Guleria
2015-09-02 14:55                                 ` Vicente Olivert Riera
2015-09-02 16:57                                   ` Dinesh Guleria
2015-09-02 17:16                                     ` Baruch Siach
2015-09-02 17:58                                       ` Dinesh Guleria
2015-09-02 18:13                                         ` Dinesh Guleria
2015-09-02 18:24                                         ` Samuel Martin
2015-09-01  6:56         ` Thomas Petazzoni
2015-08-31 20:45 ` Thomas Petazzoni [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=20150831224544.22ddf67b@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.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