From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot toolchain for arm
Date: Wed, 23 Mar 2011 13:08:55 -0300 [thread overview]
Message-ID: <4D8A1B17.3030201@zacarias.com.ar> (raw)
In-Reply-To: <AANLkTi=o3wKS3BhnGrN+g1emwedgsnN3GtEbMYz4x560@mail.gmail.com>
On 03/23/11 08:50, Chia-Hung Chou wrote:
> I want to build the toolchain to compile into fully thumb
> instruction. In the menuconfig, I add the "--with-mode=thumb" into gcc
> options.
> After I make the buildroot, there are some Errors :
> make[5]: *** [libmudflap.la <http://libmudflap.la>] Error 1
> make[5]: Leaving directory
> '/home/chiahung/buildroot-2011.02/output/toolchain/gcc-4.4.5-final/arm-unknown-linux-uclibic/libmudflap'
> make[4]: *** [all-recursive] Error 1
> make[4]: Leaving directory
> '/home/chiahung/buildroot-2011.02/output/toolchain/gcc-4.4.5-final/arm-unknown-linux-uclibic/libmudflap'
> make[3]: *** [all] Error 2
> make[3]: Leaving directory
> '/home/chiahung/buildroot-2011.02/output/toolchain/gcc-4.4.5-final/arm-unknown-linux-uclibic/libmudflap'
> make[2]: *** [all-target-libmudflap] Error 2
> make[2]: Leaving directory
> '/home/chiahung/buildroot-2011.02/output/toolchain/gcc-4.4.5-final'
> make[1]: *** [all-target-libmudflap] Error 2
> make[1]: Leaving directory
> '/home/chiahung/buildroot-2011.02/output/toolchain/gcc-4.4.5-final'
> make: ***
> [/home/chiahung/buildroot-2011.02/output/toolchain/gcc-4.4.4.5-final/.compiled]
> Error 2
> I try a lot of ways but I still can't solve it. Is there any way to
> solve or to build a toolchain that could compile code into fully thumb
> instruction??
>
> thanks~
Yes, you might want to use "-mthumb" in BR2_TARGET_OPTIMIZATION.
See the gcc manpage.
Regards.
prev parent reply other threads:[~2011-03-23 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 11:50 [Buildroot] Buildroot toolchain for arm Chia-Hung Chou
2011-03-23 16:08 ` Gustavo Zacarias [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=4D8A1B17.3030201@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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