From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 2/3] eglibc/arm: doesn't build in thumb(1) mode
Date: Sun, 21 Jul 2013 17:24:15 +0200 [thread overview]
Message-ID: <20130721172415.1a730f0f@skate> (raw)
In-Reply-To: <87li52td8g.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Sat, 20 Jul 2013 00:07:59 +0200, Peter Korsgaard wrote:
> Gustavo> @@ -36,7 +41,8 @@ define EGLIBC_CONFIGURE_CMDS
> Gustavo> # Do the configuration
> Gustavo> (cd $(@D)/build; \
> Gustavo> $(TARGET_CONFIGURE_OPTS) \
> Gustavo> - CFLAGS="-O2" CPPFLAGS="" CXXFLAGS="-O2" \
> Gustavo> + CFLAGS="-O2 $(EGLIBC_EXTRA_CFLAGS)" CPPFLAGS="" \
>
> I know you didn't add this, but why are we forcing -O2 here? Thomas?
Because eglibc must be built with optimizations. See
http://patches.openembedded.org/patch/38849/ for example.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-07-21 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 13:06 [Buildroot] [PATCHv2 1/3] gcc/arm: disable mudflap for thumb(1) Gustavo Zacarias
2013-07-19 13:06 ` [Buildroot] [PATCHv2 2/3] eglibc/arm: doesn't build in thumb(1) mode Gustavo Zacarias
2013-07-19 22:07 ` Peter Korsgaard
2013-07-21 15:24 ` Thomas Petazzoni [this message]
2013-07-21 16:06 ` Peter Korsgaard
2013-07-19 13:06 ` [Buildroot] [PATCHv2 3/3] uclibc/arm: doesn't build in thumb(1) mode with threads Gustavo Zacarias
2013-07-19 22:07 ` [Buildroot] [PATCHv2 1/3] gcc/arm: disable mudflap for thumb(1) Peter Korsgaard
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=20130721172415.1a730f0f@skate \
--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