From: Brian Austin <brian.austin@cirrus.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with building ARM cross toolchain using buildroot
Date: Thu, 27 Sep 2007 09:08:20 -0500 [thread overview]
Message-ID: <1190902100.7430.126.camel@localhost.localdomain> (raw)
In-Reply-To: <140561.37392.qm@web7910.mail.in.yahoo.com>
You should not use the toolchain buildroot package provided by cirrus to
build a buildroot toolchain.
please download one from the buildroot website.
http://buildroot.uclibc.org/downloads/snapshots/buildroot-snapshot.tar.bz2
The buildroot package from arm.cirrus.com is a binary one packaged with
the sources.
On Thu, 2007-09-27 at 10:03 +0100, ashok vardhan wrote:
> Hi Sir/Madam,
> We are building a toolchain for ARM9 EDB9315A board using "
> arm-linux-gcc-3.4.3 tar file " provided by " www.arm.cirrus.com ".
> After extracting the tar file, we got two directories " opt " and "
> usr ".
> In that opt directory another directory buildroot is present .
> We started the steps to build the buildroot...........
> The steps are 1. make menuconfig
> 2. make
> After doing the second step i.e make , we are getting errors.
>
> Please provide us some solution regarding the building cross-toolchain
> using buildroot.
>
> Regards,
> Ashok.
>
>
> ______________________________________________________________________
> Now you can chat without downloading messenger. Click here to know
> how.
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2007-09-27 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 9:03 [Buildroot] Problem with building ARM cross toolchain using buildroot ashok vardhan
2007-09-27 11:37 ` Kuten Ivan
2007-09-27 14:08 ` Brian Austin [this message]
2007-09-27 17:07 ` Bernhard Fischer
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=1190902100.7430.126.camel@localhost.localdomain \
--to=brian.austin@cirrus.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