Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pcre: fix compile error for m68k coldfire
Date: Thu, 18 Aug 2016 08:25:35 +0200	[thread overview]
Message-ID: <20160818062535.GA28475@waldemar-brodkorb.de> (raw)

Some very big functions can not be compiled successfully for
m68k coldfire, when -msep-data is used.

Fixes:
  http://autobuild.buildroot.net/results/d31/d311955ada1ffcd7f69e82965c8fe33eabe488cd/

Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
 package/pcre/pcre.mk | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/package/pcre/pcre.mk b/package/pcre/pcre.mk
index a10950d..6352cc8 100644
--- a/package/pcre/pcre.mk
+++ b/package/pcre/pcre.mk
@@ -26,5 +26,11 @@ PCRE_CONF_OPTS += $(if $(BR2_PACKAGE_PCRE_32),--enable-pcre32,--disable-pcre32)
 PCRE_CONF_OPTS += $(if $(BR2_PACKAGE_PCRE_UTF),--enable-utf,--disable-utf)
 PCRE_CONF_OPTS += $(if $(BR2_PACKAGE_PCRE_UCP),--enable-unicode-properties,--disable-unicode-properties)
 
+# fixes gcc error: value -yyyyy out of range
+ifeq ($(BR2_m68k_cf),y)
+PCRE_CFLAGS = $(filter-out -msep-data,$(TARGET_CFLAGS))
+PCRE_CONF_ENV += CFLAGS="$(PCRE_CFLAGS)"
+endif
+
 $(eval $(autotools-package))
 $(eval $(host-autotools-package))
-- 
2.1.4

             reply	other threads:[~2016-08-18  6:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18  6:25 Waldemar Brodkorb [this message]
2016-08-19 21:13 ` [Buildroot] [PATCH] pcre: fix compile error for m68k coldfire Thomas Petazzoni
2016-08-19 21:24   ` Waldemar Brodkorb
2016-08-22 15:30     ` 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=20160818062535.GA28475@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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