On Fri, Jan 5, 2018 at 4:22 PM, Richard Purdie
wrote:
> On Fri, 2018-01-05 at 11:15 -0800, Alistair Francis wrote:
>> On Thu, Jan 4, 2018 at 12:45 AM, Richard Purdie
>> wrote:
>> > I ran the qemu upgrade in some builds and both hang in nightly-musl
>> > whilst trying to build webkitgtk:
>> >
>> >
On Fri, 2018-01-05 at 11:15 -0800, Alistair Francis wrote:
> On Thu, Jan 4, 2018 at 12:45 AM, Richard Purdie
> wrote:
> > I ran the qemu upgrade in some builds and both hang in nightly-musl
> > whilst trying to build webkitgtk:
> >
> > https://autobuilder.yocto.io/builders/nightly-musl/builds/688
On Fri, 2018-01-05 at 21:08 +, Slater, Joseph wrote:
> Neglecting buildhistory, there is only one recipe, I think, that uses
> SSTATEPOSTINSTFUNCS -- php-native, and that does not work. Since
> there is nothing to compare to, I do not know if sysconfdir is set
> incorrectly, or if the function
Neglecting buildhistory, there is only one recipe, I think, that uses
SSTATEPOSTINSTFUNCS -- php-native, and that does not work. Since there is
nothing to compare to, I do not know if sysconfdir is set incorrectly, or if
the function is supposed to realize it is under sysroot-destdir and adjust
On Thu, Jan 4, 2018 at 12:45 AM, Richard Purdie
wrote:
> On Tue, 2018-01-02 at 14:58 -0800, Alistair Francis wrote:
>> On Thu, Dec 21, 2017 at 1:56 PM, Alistair Francis
>> wrote:
>> >
>> > Use the latest QEMU release 2.11. Remove all patches that are no
>> > longer
>> > required as they have been
No it's not, but I googled it for you and https://github.com/libo/Enigma2
suggests that GPLv2 is the license.
Ross
On 27 December 2017 at 10:01, Benjamin Hagemann wrote:
> Hello,
>
> this mailinglist is maintainer of the enigma2-plugin-extensions-pictureplayer,
> right?
> Under which licence is
On 01/05/2018 07:37 PM, Ovidiu Panait wrote:
CPython (aka Python) up to 2.7.13 is vulnerable to an integer overflow in
the PyString_DecodeEscape function in stringobject.c, resulting in
heap-based buffer overflow (and possible arbitrary code execution).
What about python 3.x that this patch als
CPython (aka Python) up to 2.7.13 is vulnerable to an integer overflow in
the PyString_DecodeEscape function in stringobject.c, resulting in
heap-based buffer overflow (and possible arbitrary code execution).
Upstream patches:
https://github.com/python/cpython/commit/c3c9db89273fabc62ea1b48389d9
Signed-off-by: Ross Burton
---
meta/recipes-extended/psmisc/psmisc.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-extended/psmisc/psmisc.inc
b/meta/recipes-extended/psmisc/psmisc.inc
index 527a1d590f3..82ef947709a 100644
--- a/meta/recipes-extended/psmis
Cryptodev only breaks with 4.13 and 4.14.
4.12 builds successfully with and without this patch.
Daniel
On 01/05/2018 04:59 PM, Daniel Schultz wrote:
Hi,
On 01/05/2018 04:25 PM, Richard Purdie wrote:
On Fri, 2018-01-05 at 15:37 +0100, Daniel Schultz wrote:
Commit message from the included pat
If you have a recipe which does not include SRCPV in PV but does set
SRCREV = "${AUTOREV}" and you run do_fetch, then change the repo to a
new commit then run do_unpack, do_unpack will fail since the new commit
doesn't exist in the repo that was fetched.
The problem is the revision chosen is not r
We see occasional network glitches which break this test. Use our own
mirror (which has a .gz instead of .bz2) to avoid the errors, we're not
trying to test network connectivity.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/runtime/cases/buildcpio.py | 3 +--
1 file changed, 1 insertion(+), 2
Hi,
On 01/05/2018 04:25 PM, Richard Purdie wrote:
On Fri, 2018-01-05 at 15:37 +0100, Daniel Schultz wrote:
Commit message from the included patch:
"Linux kernel has added -Werror=designated-init around 4.11
(c834f0e8a8b)
triggering build errors with gcc 5 and 6 (but not with gcc 4)"
Backport f
'bitbake -c checkpkg world' is moved to class initializer to avoid
it being run twice in a row.
Signed-off-by: Alexander Kanavin
---
meta/lib/oeqa/selftest/cases/distrodata.py | 32 +-
1 file changed, 27 insertions(+), 5 deletions(-)
diff --git a/meta/lib/oeqa/selfte
Signed-off-by: Alexander Kanavin
---
meta/conf/distro/include/maintainers.inc | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/conf/distro/include/maintainers.inc
b/meta/conf/distro/include/maintainers.inc
index 4fb7cd32813..bc9c7b0d8d1 100644
--- a/meta/conf/distro/in
The packages loosely follow the debian package names. In that way more
projects, e.g. Qt5 for 16-bit, are able use system libraries. This does
not change the existing default package.
Signed-off-by: Stefan Müller-Klieser
---
meta/recipes-support/libpcre/libpcre2_10.30.bb | 7 +--
1 file chan
On Fri, 2018-01-05 at 15:37 +0100, Daniel Schultz wrote:
> Commit message from the included patch:
> "Linux kernel has added -Werror=designated-init around 4.11
> (c834f0e8a8b)
> triggering build errors with gcc 5 and 6 (but not with gcc 4)"
>
> Backport from https://github.com/cryptodev-linux/cry
On 01/05/2018 01:47 PM, Burton, Ross wrote:
Do we even need gnomebase-meson with this? I can see a future where
GNOME is entirely Meson and then we could just switch the default
GNOMEBASEBUILDCLASS from autotools to meson.
(prior art being the tarball compression type)
I'm fine with this.
Commit message from the included patch:
"Linux kernel has added -Werror=designated-init around 4.11 (c834f0e8a8b)
triggering build errors with gcc 5 and 6 (but not with gcc 4)"
Backport from https://github.com/cryptodev-linux/cryptodev-linux
Based on commit f0d69774afb27ffc62bf353465fba145e70cb85a
To make it easier to debug problems with renaming caused by debian.bbclass,
explicitly log when packages are renamed.
Signed-off-by: Ross Burton
---
meta/classes/debian.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/debian.bbclass b/meta/classes/debian.b
This recipe installs the test suite by copying the entire build tree into
/usr/share/ptest, which is both wasteful and breaks packaging as lz4-ptest then
gets renamed by debian.bbclass to liblz4.
Signed-off-by: Ross Burton
---
meta/recipes-support/lz4/lz4_1.7.4.bb | 10 +-
1 file changed
When the gtk-doc API documentation is enabled (via the api-documentation
DISTRO_FEATURE, typically) this recipe fails to build:
WORKDIR/build/docs/validate/gst-validate-scan: line 117:
WORKDIR/build/docs/validate/.libs/lt-gst-validate-scan:
No such file or directory
Forcibly disable the gt
On Fri, 2018-01-05 at 12:29 +0100, Steffen Sledz wrote:
> On 04.01.2018 15:39, Richard Purdie wrote:
> >
> > In basic terms, you need a machine which:
> >
> > * Sets TARGET_ARCH to the right thing (i686 or x86_64)
> > * Sets TARGET_OS to mingw32
> >
> > and then some distro config which sets up
Do we even need gnomebase-meson with this? I can see a future where GNOME
is entirely Meson and then we could just switch the default
GNOMEBASEBUILDCLASS from autotools to meson.
(prior art being the tarball compression type)
Ross
On 4 January 2018 at 13:12, Alexander Kanavin <
alexander.kana..
If api-documentation is enabled:
| make[3]: Entering directory
'/data/poky-tmp/master/build/work/corei7-64-poky-linux/gst-validate/1.12.4-r0/build/docs/plugins'
| DOC Preparing build
| DOC Preparing build
| DOC Scanning header files
| DOC Scanning header files
| DOC Introspecti
On 04.01.2018 15:39, Richard Purdie wrote:
> In basic terms, you need a machine which:
>
> * Sets TARGET_ARCH to the right thing (i686 or x86_64)
> * Sets TARGET_OS to mingw32
>
> and then some distro config which sets up the toolchain when mingw is
> the target os to the values like meta-mingw/c
26 matches
Mail list logo
