From: Constantin Musca <constantinx.musca@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v4 0/3] On-target gcc enhancement
Date: Tue, 29 Jan 2013 17:12:33 +0200 [thread overview]
Message-ID: <cover.1359470548.git.constantinx.musca@intel.com> (raw)
This patchset enables the user to build gcc with configurable multilib options.
The following changes since commit cfb082961a6c9ac3d65738031c4071210529cd07:
bitbake: build.py: Dump out performance data of individual tasks (2013-01-28 14:49:05 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib cmuscax/gcc_enhan8
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=cmuscax/gcc_enhan8
Constantin Musca (3):
autotools.bbclass: add EXTRACONFFUNCS variable
multilib.conf: add TARGET_ARCH & TARGET_SYS to MULTILIB_SAVE_VARNAME
gcc: enable multilib for target gcc
meta/classes/autotools.bbclass | 4 +-
meta/conf/multilib.conf | 2 +-
meta/recipes-devtools/gcc/gcc-4.7.inc | 3 +-
.../gcc/gcc-4.7/use-ml-conf-files-from-B.patch | 87 ++++++++++
meta/recipes-devtools/gcc/gcc-common.inc | 24 +++
meta/recipes-devtools/gcc/gcc-configure-common.inc | 3 +-
meta/recipes-devtools/gcc/gcc-configure-target.inc | 1 +
meta/recipes-devtools/gcc/gcc-multilib-config.inc | 190 +++++++++++++++++++++
meta/recipes-devtools/gcc/libgcc_4.7.bb | 73 ++++++++
9 files changed, 383 insertions(+), 4 deletions(-)
create mode 100644 meta/recipes-devtools/gcc/gcc-4.7/use-ml-conf-files-from-B.patch
create mode 100644 meta/recipes-devtools/gcc/gcc-multilib-config.inc
--
1.7.11.7
next reply other threads:[~2013-01-29 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 15:12 Constantin Musca [this message]
2013-01-29 15:12 ` [PATCH v4 1/3] autotools.bbclass: add EXTRACONFFUNCS variable Constantin Musca
2013-01-29 15:12 ` [PATCH v4 2/3] multilib.conf: add TARGET_ARCH & TARGET_SYS to MULTILIB_SAVE_VARNAME Constantin Musca
2013-01-29 15:12 ` [PATCH v4 3/3] gcc: enable multilib for target gcc Constantin Musca
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=cover.1359470548.git.constantinx.musca@intel.com \
--to=constantinx.musca@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.