From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v2] libsoc: upgrade from version 0.6 to 0.7
Date: Mon, 30 Nov 2015 10:55:05 +0000 [thread overview]
Message-ID: <565C2B09.2020000@communistcode.co.uk> (raw)
In-Reply-To: <1448215516-13579-1-git-send-email-fathi.boudra@linaro.org>
On 22/11/15 18:05, Fathi Boudra wrote:
> update SRCREV
>
> Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
> ---
> changes from v1:
> * don't ship board configs
> * don't oe-stylize
>
> meta-oe/recipes-support/libsoc/{libsoc_0.6.bb => libsoc_0.7.bb} | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> rename meta-oe/recipes-support/libsoc/{libsoc_0.6.bb => libsoc_0.7.bb} (90%)
>
> diff --git a/meta-oe/recipes-support/libsoc/libsoc_0.6.bb b/meta-oe/recipes-support/libsoc/libsoc_0.7.bb
> similarity index 90%
> rename from meta-oe/recipes-support/libsoc/libsoc_0.6.bb
> rename to meta-oe/recipes-support/libsoc/libsoc_0.7.bb
> index 79c171a..3b7436f 100644
> --- a/meta-oe/recipes-support/libsoc/libsoc_0.6.bb
> +++ b/meta-oe/recipes-support/libsoc/libsoc_0.7.bb
> @@ -9,7 +9,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=e0bfebea12a718922225ba987b2126a5"
>
> inherit autotools
>
> -SRCREV = "3643cf161a4b37bfbdfd05437166c4a29ac3ed8d"
> +SRCREV = "4d5c5af71e225cc4e792d2166da3f3e432b08735"
> SRC_URI = "git://github.com/jackmitch/libsoc.git"
>
> S = "${WORKDIR}/git"
>
There might be an issue building this with GCC 5.2, has this been tested? If it
does break I can do a 0.7.1 release and we should use that with the GCC 5.2 fix
included [1].
Cheers,
Jack
[1]
https://github.com/jackmitch/libsoc/commit/0b863612540f67c032ef0efc417538443a00b285
prev parent reply other threads:[~2015-11-30 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 18:05 [meta-oe][PATCH v2] libsoc: upgrade from version 0.6 to 0.7 Fathi Boudra
2015-11-30 10:25 ` Koen Kooi
2015-11-30 10:55 ` Jack Mitchell [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=565C2B09.2020000@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-devel@lists.openembedded.org \
/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