From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH] spice, spice-protocol: Uprev to 0.14.0
Date: Thu, 23 May 2019 21:10:00 +0300 [thread overview]
Message-ID: <20190523181000.GD3348@localhost> (raw)
In-Reply-To: <20190523174735.42541-1-raj.khem@gmail.com>
On Thu, May 23, 2019 at 10:47:35AM -0700, Khem Raj wrote:
>...
> --- a/meta-networking/recipes-support/spice/spice-protocol_git.bb
> +++ b/meta-networking/recipes-support/spice/spice-protocol_git.bb
> @@ -13,9 +13,9 @@ architectures."
> LICENSE = "BSD"
> LIC_FILES_CHKSUM = "file://COPYING;md5=b37311cb5604f3e5cc2fb0fd23527e95"
>
> -PV = "0.12.13+git${SRCPV}"
> +PV = "0.14.0+git${SRCPV}"
>
> -SRCREV = "87441524f4e7b79658e42bd8f1f6c3e3c8649aa5"
> +SRCREV = "f72ece993aeaf23f77e2845562b20e5563e52ba0"
>...
The previous one was a git snapshot but this is a release,
so +git should be dropped from PV.
>...
> Add -Wno-address-of-packed-member needed with gcc9
>
> replace _append += with just _append syntax
>...
> +CFLAGS += "-Wno-address-of-packed-member"
> +
> PACKAGECONFIG_class-native = ""
> PACKAGECONFIG_class-nativesdk = ""
> PACKAGECONFIG ?= "sasl"
> @@ -54,4 +55,4 @@ COMPATIBLE_HOST = '(x86_64|i.86).*-linux'
>
> BBCLASSEXTEND = "native nativesdk"
>
> -EXTRA_OECONF_toolchain-clang += "--disable-werror"
> +EXTRA_OECONF_append_toolchain-clang = " --disable-werror"
>...
Would adding --disable-werror for all toolchains also fix the
gcc 9 build error?
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-05-23 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 17:47 [meta-networking][PATCH] spice, spice-protocol: Uprev to 0.14.0 Khem Raj
2019-05-23 18:10 ` Adrian Bunk [this message]
2019-05-23 19:01 ` Khem Raj
2019-05-30 4:56 ` Hongzhi, Song
2019-05-30 7:23 ` Martin Jansa
2019-05-30 9:14 ` Hongzhi, Song
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=20190523181000.GD3348@localhost \
--to=bunk@stusta.de \
--cc=openembedded-devel@lists.openembedded.org \
--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.