From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] openssl: Fix build on ARM with GCC 4.6.x
Date: Thu, 1 Mar 2012 07:37:27 +0200 [thread overview]
Message-ID: <20120301053726.GA4978@sapphire.tkos.co.il> (raw)
In-Reply-To: <1330558078-3978-1-git-send-email-ismael.luceno@gmail.com>
Hi Ismael,
On Wed, Feb 29, 2012 at 09:27:57PM -0200, Ismael Luceno wrote:
>
> Signed-off-by: Ismael Luceno <ismael.luceno@gmail.com>
> ---
> package/openssl/openssl.mk | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/package/openssl/openssl.mk b/package/openssl/openssl.mk
> index cb29fe4..fda935a 100644
> --- a/package/openssl/openssl.mk
> +++ b/package/openssl/openssl.mk
> @@ -9,7 +9,14 @@ OPENSSL_SITE = http://www.openssl.org/source
> OPENSSL_INSTALL_STAGING = YES
> OPENSSL_DEPENDENCIES = zlib
> OPENSSL_TARGET_ARCH = generic32
> +
> +ifeq ($(BR2_GCC_VERSION_4_6_X)-$(ARCH),y-arm)
> +# workaround for gcc issue
> +# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48308
> +OPENSSL_CFLAGS = $(subst -Os,-O2,$(TARGET_CFLAGS))
> +else
> OPENSSL_CFLAGS = $(TARGET_CFLAGS)
> +endif
Will this work for external and ct-ng toolchains?
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2012-03-01 5:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 23:27 [Buildroot] [PATCH 1/2] openssl: Fix build on ARM with GCC 4.6.x Ismael Luceno
2012-02-29 23:27 ` [Buildroot] [PATCH 2/2] openssl: Add -march and -mcpu flags Ismael Luceno
2012-03-01 5:37 ` Baruch Siach [this message]
2012-03-01 7:32 ` [Buildroot] [PATCH 1/2] openssl: Fix build on ARM with GCC 4.6.x Thomas Petazzoni
2012-03-01 17:32 ` Ismael Luceno
2012-03-01 18:10 ` Baruch Siach
2012-03-03 23:13 ` Ismael Luceno
2012-03-05 5:19 ` Baruch Siach
2012-03-05 6:45 ` Ismael Luceno
2012-03-06 15:21 ` Gustavo Zacarias
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=20120301053726.GA4978@sapphire.tkos.co.il \
--to=baruch@tkos.co.il \
--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