Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] GCC fixes and updates
Date: Wed,  5 Sep 2012 21:35:35 -0700	[thread overview]
Message-ID: <cover.1346905978.git.raj.khem@gmail.com> (raw)

This patchset switches us back to using svn for SRC_URI
and fixes building for armv4 and ppc soft float targets
Finally fixes for libgcc to build with new build sequence
such that its same with gcc-cross and gcc-cross-initial

The following changes since commit 610f8c0c0cab8e258919689fd641faec28b58caf:

  adt-installer: Allow changing YOCTOADT_REPO (2012-09-05 23:27:31 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib kraj/gcc-updates
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/gcc-updates

Khem Raj (4):
  gcc: Switch SRC_URI to use svn
  gcc-4.7: Fix build for armv4/EABI and ppc/Os
  arch-armv4.inc: On armv4 add --fix-v4bx to linker flags for kernel
  gcc-4.7: Backport libgcc fixes to appease the new build sequence

 meta/conf/machine/include/arm/arch-armv4.inc       |    1 +
 meta/recipes-devtools/gcc/gcc-4.7.inc              |   14 +--
 ...-vis_hide-gen-hide-list-Do-not-make-defin.patch |   93 ++++++++++++++++++++
 ...USE_PT_GNU_EH_FRAME-Define-for-systems-us.patch |   49 +++++++++++
 .../gcc-4.7/gcc-armv4-pass-fix-v4bx-to-ld.patch    |   29 ++++++
 .../gcc/gcc-4.7/ppc_no_crtsavres.patch             |   21 +++++
 6 files changed, 202 insertions(+), 5 deletions(-)
 create mode 100644 meta/recipes-devtools/gcc/gcc-4.7/0001-Makefile.in-vis_hide-gen-hide-list-Do-not-make-defin.patch
 create mode 100644 meta/recipes-devtools/gcc/gcc-4.7/0001-crtstuff.c-USE_PT_GNU_EH_FRAME-Define-for-systems-us.patch
 create mode 100644 meta/recipes-devtools/gcc/gcc-4.7/gcc-armv4-pass-fix-v4bx-to-ld.patch
 create mode 100644 meta/recipes-devtools/gcc/gcc-4.7/ppc_no_crtsavres.patch

-- 
1.7.9.5




             reply	other threads:[~2012-09-06  4:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06  4:35 Khem Raj [this message]
2012-09-06  4:35 ` [PATCH 1/4] gcc: Switch SRC_URI to use svn Khem Raj
2012-09-06  7:05   ` Koen Kooi
2012-09-12  2:44   ` Gary Thomas
2012-09-12 14:08     ` Richard Purdie
2012-09-12 15:34       ` Khem Raj
2012-09-13 12:19         ` Björn Stenberg
2012-09-13 13:06           ` Otavio Salvador
2012-09-13 14:22             ` Chris Larson
2012-09-14 11:58               ` Richard Purdie
2012-09-14 12:31                 ` Bruce Ashfield
2012-09-14 12:36                 ` Otavio Salvador
2012-09-14 13:23                   ` Richard Purdie
2012-09-14 13:25                     ` Otavio Salvador
2012-09-14 18:30                       ` [bitbake-devel] " McClintock Matthew-B29882
2012-09-15  6:25                 ` Martin Jansa
2012-09-06  4:35 ` [PATCH 2/4] gcc-4.7: Fix build for armv4/EABI and ppc/Os Khem Raj
2012-09-06  7:04   ` Koen Kooi
2012-09-06  4:35 ` [PATCH 3/4] arch-armv4.inc: On armv4 add --fix-v4bx to linker flags for kernel Khem Raj
2012-09-06  4:35 ` [PATCH 4/4] gcc-4.7: Backport libgcc fixes to appease the new build sequence Khem Raj
2012-09-09  6:02 ` [PATCH 0/4] GCC fixes and updates Khem Raj
2012-09-12 17:43 ` Saul Wold

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.1346905978.git.raj.khem@gmail.com \
    --to=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox