[OE-core] [PATCH] gcc-4.6: update to 4.6.1 release

[Kamble, Nitin A]

Has anybody tried building all arches with commit? If it has worked well then the upgrade to 4.6.1 is good. Otherwise it may affect too many people.

Thanks,
Nitin


> -----Original Message-----
> From: openembedded-core-bounces at lists.openembedded.org
> [mailto:openembedded-core-bounces at lists.openembedded.org] On Behalf Of
> Phil Blundell
> Sent: Wednesday, July 13, 2011 9:41 AM
> To: oe-core
> Subject: [OE-core] [PATCH] gcc-4.6: update to 4.6.1 release
> 
> Set SRCREV to match the point at which 4.6.1 was released, update PV
> appropriately.
> 
> Signed-off-by: Phil Blundell <philb at 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
> 
> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core