All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gcc: Upgrade to 4.8.1
Date: Thu, 13 Jun 2013 10:12:33 -0700	[thread overview]
Message-ID: <51B9FD81.6030405@linux.intel.com> (raw)
In-Reply-To: <1370987869-19041-1-git-send-email-raj.khem@gmail.com>

On 06/11/2013 02:57 PM, Khem Raj wrote:
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
>   meta/recipes-devtools/gcc/gcc-4.8.inc |    8 ++++----
>   1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/meta/recipes-devtools/gcc/gcc-4.8.inc b/meta/recipes-devtools/gcc/gcc-4.8.inc
> index 80bd02c..6664f1c 100644
> --- a/meta/recipes-devtools/gcc/gcc-4.8.inc
> +++ b/meta/recipes-devtools/gcc/gcc-4.8.inc
> @@ -6,7 +6,7 @@ require gcc-common.inc
>   # on branch then PV should be incremented to 4.7.2+svnr${SRCPV}
>   # to reflect that change
>
> -PV = "4.8.0"
> +PV = "4.8.1"
>

Khem, Otavio:

Not sure if it was this change or 4.8 in general, but there are a number 
of failures in the FSL-ARM and FSL-PPC builds:

PPC Issues (gettext / mfpr):
http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-ppc/builds/141/steps/Building%20Images/logs/stdio
http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-ppc-lsb/builds/139/steps/Building%20Images/logs/stdio

ARM Issues (both in perf):
http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm/builds/140/steps/Building%20Images/logs/stdio

Can one or both of you look into this.

Thanks
	Sau!


>   # 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
> @@ -14,7 +14,7 @@ PV = "4.8.0"
>   # 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.8.0"
> +BINV = "4.8.1"
>
>   FILESPATH = "${@base_set_filespath([ '${FILE_DIRNAME}/gcc-4.8' ], d)}"
>
> @@ -68,8 +68,8 @@ SRC_URI = "${GNU_MIRROR}/gcc/gcc-${PV}/gcc-${PV}.tar.bz2 \
>   	   file://gcc-4.8-PR56797.patch \
>   	   file://gcc-4.8-build-args.patch \
>   	  "
> -SRC_URI[md5sum] = "e6040024eb9e761c3bea348d1fa5abb0"
> -SRC_URI[sha256sum] = "b037fe5132b71ecad2ea7141ec92292b5d32427bf90fd90cde432b1d5abacc2c"
> +SRC_URI[md5sum] = "3b2386c114cd74185aa3754b58a79304"
> +SRC_URI[sha256sum] = "545b44be3ad9f2c4e90e6880f5c9d4f0a8f0e5f67e1ffb0d45da9fa01bb05813"
>
>   S = "${TMPDIR}/work-shared/gcc-${PV}-${PR}/gcc-${PV}"
>   B = "${WORKDIR}/gcc-${PV}/build.${HOST_SYS}.${TARGET_SYS}"
>


  parent reply	other threads:[~2013-06-13 17:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 21:57 [PATCH] gcc: Upgrade to 4.8.1 Khem Raj
2013-06-11 22:31 ` [RFC][PATCH] gcc-4.8: Backport fix for ICE triggered in pixman Martin Jansa
2013-06-11 22:35   ` Martin Jansa
2013-06-11 22:36     ` Khem Raj
2013-06-11 22:39     ` Khem Raj
2013-06-11 23:00       ` Martin Jansa
2013-06-11 23:16         ` Saul Wold
2013-06-13 17:12 ` Saul Wold [this message]
2013-06-13 19:43   ` [PATCH] gcc: Upgrade to 4.8.1 Khem Raj
2013-06-28 23:47 ` Jonathan Liu
2013-06-29  0:51   ` Khem Raj

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=51B9FD81.6030405@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=raj.khem@gmail.com \
    /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.