From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] gcc update and bug fix
Date: Mon, 17 Oct 2011 18:38:50 -0700 [thread overview]
Message-ID: <cover.1318901607.git.raj.khem@gmail.com> (raw)
This patchset does two things for gcc
1. Updates to latest from FSF gcc-4_6-branch
2. Backport the fix for PR46934
The changes that come from FSF gcc are listed here
http://sakrah.homelinux.org/files/gcc-4.6-ChangeLog-r180099_r180099.txt
3. Bluez4 needed glib.h therefore depend on glib-2.0
The following changes since commit 8bc098475f58b60bfb24ec0fd338e49ac2387c50:
gcc-4.6: Backport PR46934 fix (2011-10-17 18:00:29 -0700)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib kraj/gcc-update
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/gcc-update
Khem Raj (3):
bluez4: Add glib-2.0 to DEPENDS
gcc-4.6: Upgrade SRCREV to latest FSF 4.6 branch
gcc-4.6: Backport PR46934 fix
meta/recipes-connectivity/bluez/bluez4.inc | 2 +-
meta/recipes-connectivity/bluez/bluez4_4.96.bb | 2 +-
meta/recipes-devtools/gcc/gcc-4.6.inc | 5 +-
meta/recipes-devtools/gcc/gcc-4.6/pr46934.patch | 392 +++++++++++++++++++++++
4 files changed, 397 insertions(+), 4 deletions(-)
create mode 100644 meta/recipes-devtools/gcc/gcc-4.6/pr46934.patch
--
1.7.5.4
next reply other threads:[~2011-10-18 1:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 1:38 Khem Raj [this message]
2011-10-18 1:39 ` [PATCH 1/3] bluez4: Add glib-2.0 to DEPENDS Khem Raj
2011-10-18 1:39 ` [PATCH 2/3] gcc-4.6: Upgrade SRCREV to latest FSF 4.6 branch Khem Raj
2011-10-18 1:39 ` [PATCH 3/3] gcc-4.6: Backport PR46934 fix Khem Raj
2011-10-18 7:54 ` Martin Jansa
2011-10-18 14:18 ` Koen Kooi
2011-10-18 16:47 ` Saul Wold
2011-10-18 16:54 ` Koen Kooi
2011-10-20 17:19 ` [PATCH 0/3] gcc update and bug fix 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.1318901607.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 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.