From 7fb442a320d7fd0ebe43ce090cf1f3a1525cb6d1 Mon Sep 17 00:00:00 2001 From: Khem Raj Date: Wed, 20 Jun 2012 08:18:37 -0700 Subject: gcc-4.7: Update to tip of gcc-4_7-branch since 4.7.1 has been out (From OE-Core rev: 7986e424995a4119b45a09767dc5100a5cdb5161) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie --- meta/recipes-devtools/gcc/gcc-4.7.inc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'meta/recipes-devtools/gcc') diff --git a/meta/recipes-devtools/gcc/gcc-4.7.inc b/meta/recipes-devtools/gcc/gcc-4.7.inc index 34a73b1731..25a1088623 100644 --- a/meta/recipes-devtools/gcc/gcc-4.7.inc +++ b/meta/recipes-devtools/gcc/gcc-4.7.inc @@ -3,12 +3,12 @@ require gcc-common.inc PR = "r2" # Third digit in PV should be incremented after a minor release -# happens from this branch on gcc e.g. currently its 4.7.0 -# when 4.7.1 is releases and we bump SRCREV beyond the release -# on branch then PV should be incremented to 4.7.1+svnr${SRCPV} +# happens from this branch on gcc e.g. currently its 4.7.1 +# when 4.7.2 is releases and we bump SRCREV beyond the release +# on branch then PV should be incremented to 4.7.2+svnr${SRCPV} # to reflect that change -PV = "4.7.0+svnr${SRCPV}" +PV = "4.7.1+svnr${SRCPV}" # BINV should be incremented after updating to a revision # after a minor gcc release (e.g. 4.7.1 or 4.7.2) has been made @@ -16,9 +16,9 @@ PV = "4.7.0+svnr${SRCPV}" # 4.7.1 then the value below will have 2 which will mean 4.7.2 # which will be next minor release and so on. -BINV = "4.7.1" +BINV = "4.7.2" -SRCREV = "186651" +SRCREV = "188658" BRANCH = "gcc-4_7-branch" FILESPATH = "${@base_set_filespath([ '${FILE_DIRNAME}/gcc-4.7' ], d)}" -- cgit v1.2.3-54-g00ecf