From: Phil Blundell <philb@gnu.org>
To: oe-core <openembedded-core@lists.openembedded.org>
Subject: [PATCH] gcc-4.6: update to 4.6.1 release
Date: Wed, 13 Jul 2011 17:41:13 +0100 [thread overview]
Message-ID: <1310575274.2378.32.camel@phil-desktop> (raw)
Set SRCREV to match the point at which 4.6.1 was released, update PV appropriately.
Signed-off-by: Phil Blundell <philb@gnu.org>
---
meta/recipes-devtools/gcc/gcc-4.6.inc | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-devtools/gcc/gcc-4.6.inc b/meta/recipes-devtools/gcc/gcc-4.6.inc
index 56064b5..8af5369 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 = "r8"
+PR = "r0"
# Third digit in PV should be incremented after a minor release
# happens from this branch on gcc e.g. currently its 4.6.0
@@ -8,7 +8,7 @@ PR = "r8"
# on branch then PV should be incremented to 4.6.1+svnr${SRCPV}
# to reflect that change
-PV = "4.6.0+svnr${SRCPV}"
+PV = "4.6.1+svnr${SRCPV}"
# BINV should be incremented after updating to a revision
# after a minor gcc release (e.g. 4.6.1 or 4.6.2) has been made
@@ -18,7 +18,7 @@ PV = "4.6.0+svnr${SRCPV}"
BINV = "4.6.1"
-SRCREV = 175150
+SRCREV = 175454
BRANCH = "gcc-4_6-branch"
FILESPATH = "${@base_set_filespath([ '${FILE_DIRNAME}/gcc-4.6' ], d)}"
--
1.7.4.1
next reply other threads:[~2011-07-13 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 16:41 Phil Blundell [this message]
2011-07-14 0:38 ` [PATCH] gcc-4.6: update to 4.6.1 release Kamble, Nitin A
2011-07-19 18:15 ` 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=1310575274.2378.32.camel@phil-desktop \
--to=philb@gnu.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 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.