[OE-core] [PATCH] bdwgc: use github repo for source location

[Saul Wold]

On Mon, 2016-04-04 at 09:18 -0700, Bill Randle wrote:
> The Yocto Autobuilder has been unable to fetch the release package
> from the developer's website at www.hboehm.info, so change recipe
> to fetch from the developer's github repo instead.
> 
> Signed-off-by: Bill Randle <william.c.randle at intel.com>
> ---
>  meta/recipes-support/bdwgc/bdwgc_7.4.2.bb | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/meta/recipes-support/bdwgc/bdwgc_7.4.2.bb
> b/meta/recipes-support/bdwgc/bdwgc_7.4.2.bb
> index 95e358f..7a4110d 100644
> --- a/meta/recipes-support/bdwgc/bdwgc_7.4.2.bb
> +++ b/meta/recipes-support/bdwgc/bdwgc_7.4.2.bb
> @@ -21,12 +21,10 @@ SECTION = "devel"
>  LICENSE = "MIT"
>  LIC_FILES_CHKSUM =
> "file://README.QUICK;md5=55f5088f90a982fed7af9a4897047ef7"
>  
> -SRC_URI = "http://www.hboehm.info/gc/gc_source/gc-${PV}.tar.gz \
> +SRCREV = "e31cdc288ffbee5bf25f948e19deb5a7ce846971"
> +SRC_URI = "git://github.com/ivmai/bdwgc.git;branch=release-7_4 \
>             file://0001-fix-build-with-musl.patch \
>            "

It appears that when you updated to the git location the source base
might have changed and the MUSL patch is no longer applyng correctly.

Please verify that the patch correctly applies.

See the failure in master-next with your patch:

https://autobuilder.yoctoproject.org/main/builders/nightly-no-x11/build
s/76/steps/BuildImages/logs/stdio

This might cause more failures in the Autobuilder, this is the first
that I saw.

Sau!


> -
> -SRC_URI[md5sum] = "12c05fd2811d989341d8c6d81f66af87"
> -SRC_URI[sha256sum] =
> "63320ad7c45460e4a40e03f5aa4c6893783f21a16416c3282b994f933312afa2"
>  FILES_${PN}-doc = "/usr/share"
>  
>  REAL_PV = "${@[d.getVar('PV',1)[:-1],
> d.getVar('PV',1)][(d.getVar('PV',1)[-1]).isdigit()]}"
> -- 
> 2.5.0
>