From: Kumar Gala <galak@kernel.crashing.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] gcc: Add ability for tune files to pass in configure options to gcc
Date: Mon, 1 Aug 2011 09:21:40 -0500 [thread overview]
Message-ID: <1312208500-13381-1-git-send-email-galak@kernel.crashing.org> (raw)
Added a ${GCC_EXTRA_OECONF} to the the building up of gcc's
${EXTRA_OECONF}. This is similar to what we have in the glibc recipe
files.
This allows for a tune file to add something like:
GCC_EXTRA_OECONF += "--with-cpu=e5500"
If needed.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
---
meta/recipes-devtools/gcc/gcc-4.6.inc | 2 +-
meta/recipes-devtools/gcc/gcc-configure-common.inc | 2 ++
meta/recipes-devtools/gcc/gcc_4.5.1.bb | 2 +-
meta/recipes-devtools/gcc/gcc_csl-arm-2008q1.bb | 2 +-
4 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-devtools/gcc/gcc-4.6.inc b/meta/recipes-devtools/gcc/gcc-4.6.inc
index 4c1e1e1..b054266 100644
--- a/meta/recipes-devtools/gcc/gcc-4.6.inc
+++ b/meta/recipes-devtools/gcc/gcc-4.6.inc
@@ -1,6 +1,6 @@
require gcc-common.inc
-PR = "r2"
+PR = "r3"
# Third digit in PV should be incremented after a minor release
# happens from this branch on gcc e.g. currently its 4.6.0
diff --git a/meta/recipes-devtools/gcc/gcc-configure-common.inc b/meta/recipes-devtools/gcc/gcc-configure-common.inc
index 9f5ba33..aac6d69 100644
--- a/meta/recipes-devtools/gcc/gcc-configure-common.inc
+++ b/meta/recipes-devtools/gcc/gcc-configure-common.inc
@@ -20,6 +20,7 @@ LANGUAGES ?= "c,c++${FORTRAN}${JAVA}"
SPECIAL_ARCH_LIST = "powerpc"
OPTSPACE = ${@base_contains("SPECIAL_ARCH_LIST", "${TARGET_ARCH}", "", "--enable-target-optspace",d)}
+GCC_EXTRA_OECONF ?= ""
EXTRA_OECONF_BASE ?= ""
EXTRA_OECONF_PATHS ?= ""
EXTRA_OECONF_INITIAL ?= ""
@@ -39,6 +40,7 @@ EXTRA_OECONF = "${@['--enable-clocale=generic', ''][bb.data.getVar('USE_NLS', d,
--enable-libstdcxx-pch \
--program-prefix=${TARGET_PREFIX} \
${OPTSPACE} \
+ ${GCC_EXTRA_OECONF} \
${EXTRA_OECONF_BASE} \
${EXTRA_OECONF_FPU} \
${EXTRA_OECONF_PATHS} \
diff --git a/meta/recipes-devtools/gcc/gcc_4.5.1.bb b/meta/recipes-devtools/gcc/gcc_4.5.1.bb
index 12e42c4..f036cb1 100644
--- a/meta/recipes-devtools/gcc/gcc_4.5.1.bb
+++ b/meta/recipes-devtools/gcc/gcc_4.5.1.bb
@@ -1,4 +1,4 @@
-PR = "r7"
+PR = "r8"
require gcc-${PV}.inc
require gcc-configure-target.inc
require gcc-package-target.inc
diff --git a/meta/recipes-devtools/gcc/gcc_csl-arm-2008q1.bb b/meta/recipes-devtools/gcc/gcc_csl-arm-2008q1.bb
index 2df12ef..9fd2b0a 100644
--- a/meta/recipes-devtools/gcc/gcc_csl-arm-2008q1.bb
+++ b/meta/recipes-devtools/gcc/gcc_csl-arm-2008q1.bb
@@ -1,4 +1,4 @@
-PR = "r4"
+PR = "r5"
require gcc-${PV}.inc
require gcc-configure-target.inc
--
1.7.3.4
next reply other threads:[~2011-08-01 14:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 14:21 Kumar Gala [this message]
2011-08-01 14:30 ` [PATCH] gcc: Add ability for tune files to pass in configure options to gcc Phil Blundell
2011-08-01 14:37 ` Kumar Gala
2011-08-01 16:07 ` Phil Blundell
2011-08-01 16:44 ` Tom Rini
2011-08-01 16:57 ` Richard Purdie
2011-08-02 13:11 ` Kumar Gala
2011-08-02 13:42 ` Richard Purdie
2011-08-08 16:32 ` Kumar Gala
2011-08-08 23:22 ` Richard Purdie
2011-08-08 16:35 ` Kumar Gala
2011-08-08 19:33 ` Richard Purdie
2011-08-02 13:02 ` Phil Blundell
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=1312208500-13381-1-git-send-email-galak@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=openembedded-core@lists.openembedded.org \
/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