From: Dan Pattison <dan.pattison@ethertek.ca>
To: buildroot@busybox.net
Subject: [Buildroot] Urgent : at91rm9200 root file system
Date: Fri, 06 Feb 2009 07:21:29 -0800 [thread overview]
Message-ID: <498C5579.10007@ethertek.ca> (raw)
In-Reply-To: <1233928454.4559.27.camel@linux-l8en.site>
Sandeep:
On the command line; navigate to the folder where you want your build
environment installed.
Type out this command:
svn co svn://uclibc.org/trunk/buildroot
It will download the current Buildroot files. Then type out:
make at91rm9200df_defconfig
Then type out:
make
Try that. Also the docs are here
http://buildroot.uclibc.org/buildroot.html
Best Regards,
Dan Pattison
Sandeep Kumar wrote:
> Hi Peter,
>
> Thanks once again for your response.
>
> Sorry!!!, I have not understood your reply. I am some what new to this
> platform. I am working on a linux machine and i do not have the source
> code for the root file system to make it. From where can i get the
> source code to build it for at91rm9200. Where should i execute the
> command sent by you (make at91rm9200df_defconfig; make) without having
> the source code. And if i am making some mistake can you please explain
> me in a little bit detail. I will be very thankful to you.
>
> Regards
> Sandeep
>
>
> On Fri, 2009-02-06 at 13:47 +0100, Peter Korsgaard wrote:
>
>>>>>>> "Sandeep" == Sandeep Kumar <sandeepk@verismonetworks.com> writes:
>>>>>>>
>> Sandeep> Hi peter
>> Sandeep> Thanks for reply.
>>
>> Sandeep> For this I want the root file system source code which i
>> Sandeep> dont have. from where can i get it.
>>
>> Buildroot will download the sources and build the rootfs for you when
>> you run make.
>>
>>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.233 / Virus Database: 270.10.18/1936 - Release Date: 01/29/09 17:57:00
>
>
next prev parent reply other threads:[~2009-02-06 15:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 23:07 [Buildroot] Web Server Dan Pattison
2009-02-04 23:21 ` Peter Korsgaard
2009-02-05 6:19 ` [Buildroot] at91rm9200 toolchain Sandeep Kumar
2009-02-05 13:25 ` Peter Korsgaard
2009-02-06 11:48 ` [Buildroot] Urgent : at91rm9200 root file system Sandeep Kumar
2009-02-06 11:53 ` Peter Korsgaard
[not found] ` <1233924549.4559.17.camel@linux-l8en.site>
[not found] ` <87zlgz91gc.fsf@macbook.be.48ers.dk>
2009-02-06 13:54 ` Sandeep Kumar
2009-02-06 15:21 ` Dan Pattison [this message]
2009-02-06 15:50 ` Sandeep Kumar
2009-02-06 16:02 ` Dan Pattison
2009-02-06 16:25 ` Sandeep Kumar
2009-02-06 17:09 ` Dan Pattison
2009-02-09 9:18 ` Sandeep Kumar
2009-02-09 9:26 ` Peter Korsgaard
2009-02-09 12:00 ` Sandeep Kumar
2009-02-09 13:05 ` Peter Korsgaard
2009-02-10 12:30 ` Sandeep Kumar
2009-02-10 12:30 ` Peter Korsgaard
2009-02-05 18:18 ` [Buildroot] Web Server Dan Pattison
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=498C5579.10007@ethertek.ca \
--to=dan.pattison@ethertek.ca \
--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