From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot: gcc options
Date: Tue, 19 Nov 2013 09:30:54 -0300 [thread overview]
Message-ID: <528B59FE.6070205@zacarias.com.ar> (raw)
In-Reply-To: <EADA2943BAC14C4AB625A3550A3BE980096DFE7183@SI-MBX04.de.bosch.com>
On 11/19/2013 09:17 AM, Altunbas Sabri (DC-IA/EAH2) wrote:
> Hi Thomas,
>
> my problem is still not solved.
>
> I picked "Buildroot toolchain" and "eglibc" as C-library and get the following error
> ..
> configure: error: unrecognized option: `-mfmovd'
> ..
> With "uclibs" the same behave.
>
> My config is attented
>
> Can you give some hints ?
Hi.
Actually BR2_EXTRA_GCC_CONFIG_OPTIONS isn't for that.
You need to set BR2_TARGET_OPTIMIZATIONS for all the packages to be
built with those CFLAGS, and you need to add them to
GLIBC_EXTRA_CFLAGS/UCLIBC_EXTRA_CFLAGS (depending on which libc you want
to use) - problem is that isn't supported in an easy way at the moment.
The quick way to test it would be to call make with those arguments in
every invocation (actually until your libc is built, for packages
BR2_TARGET_OPTIMIZATIONS does the trick), something like:
make GLIBC_EXTRA_CFLAGS="-madlign -mfmovd"
Regards.
next prev parent reply other threads:[~2013-11-19 12:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 9:03 [Buildroot] buildroot: gcc options Altunbas Sabri
2013-11-15 9:13 ` Thomas De Schampheleire
2013-11-15 9:38 ` Altunbas Sabri
2013-11-15 9:41 ` Thomas De Schampheleire
2013-11-15 9:57 ` Altunbas Sabri
2013-11-15 10:02 ` Thomas De Schampheleire
2013-11-15 10:05 ` Altunbas Sabri
2013-11-15 10:10 ` Thomas De Schampheleire
2013-11-15 10:25 ` Altunbas Sabri
2013-11-15 10:38 ` Thomas De Schampheleire
2013-11-19 12:17 ` Altunbas Sabri
2013-11-19 12:30 ` Gustavo Zacarias [this message]
2013-11-19 17:23 ` Arnout Vandecappelle
2013-11-20 11:45 ` Gustavo Zacarias
2013-11-20 12:10 ` Altunbas Sabri
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=528B59FE.6070205@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