From: "Randle, William C" <william.c.randle@intel.com>
To: "richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"Wold, Saul" <saul.wold@intel.com>
Subject: Re: [PATCH] bdwgc: use github repo for source location
Date: Tue, 5 Apr 2016 15:31:11 +0000 [thread overview]
Message-ID: <1459870271.2426.0.camel@intel.com> (raw)
In-Reply-To: <1459864507.7348.164.camel@linuxfoundation.org>
On Tue, 2016-04-05 at 14:55 +0100, Richard Purdie wrote:
On Mon, 2016-04-04 at 18:33 -0700, Saul Wold wrote:
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<http://www.hboehm.info>, so change recipe
to fetch from the developer's github repo instead.
Signed-off-by: Bill Randle <william.c.randle@intel.com<mailto:william.c.randle@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/bui
ld
s/76/steps/BuildImages/logs/stdio
This might cause more failures in the Autobuilder, this is the first
that I saw.
The patch is ok, but ${S} wasn't set correctly. I've tweaked in the
version I merged into master.
Cheers,
Richard
Thanks, guys!
prev parent reply other threads:[~2016-04-05 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 16:18 [PATCH] bdwgc: use github repo for source location Bill Randle
2016-04-05 1:33 ` Saul Wold
2016-04-05 13:55 ` Richard Purdie
2016-04-05 15:31 ` Randle, William C [this message]
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=1459870271.2426.0.camel@intel.com \
--to=william.c.randle@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox