On 1/11/19 10:00 PM, Randy MacLeod wrote:
Refresh patches using devtool.
Update license since the main code is now covered by
LGPL-2.1+ and the tests under GPL-2.
Fix a MIPS build error with an upstream patch.
Builds are fine for all qemus for both glibc and musl
aside from qemuarm64 and musl,
Refresh patches using devtool.
Update license since the main code is now covered by
LGPL-2.1+ and the tests under GPL-2.
Fix a MIPS build error with an upstream patch.
Signed-off-by: Randy MacLeod
---
...sing-non-glibc-libc-implementation-o.patch | 10 +-
...0001-caps-abbrev.awk-fix-gawk-s-path.
On Wed, Jan 9, 2019 at 11:17 PM Robert Yang
wrote:
> Hi,
>
> I reimplemented glibc's site config and did a lot of tests recently,
> finally,
> I found that it isn't as useful as I had thought, so I'm leaning to remove
> classes/siteconfig.bbclass.
>
> * Here are the test results of with/without g
On Thu, Jan 10, 2019 at 3:54 PM Burton, Ross wrote:
>
> On Thu, 10 Jan 2019 at 23:14, Alistair Francis wrote:
>>
>> > libinput isn't useful without a graphical debugging tool? That seems
>> > quite a stretch.
>>
>> I meant that libinput isn't useful without the gui support.
>>
>> I think that t
A couple of typos and grammar improvements, otherwise a good
improvement for iterative development of a package/image where
sstate isn't useful.
On 12/18/18 2:18 AM, Robert Yang wrote:
The previous ccache.bbclass has the following problems:
- It uses host's ccache for native recipes, but this ma
> -Original Message-
> From: bitbake-devel-boun...@lists.openembedded.org boun...@lists.openembedded.org> On Behalf Of Joshua Watt
> Sent: den 9 januari 2019 18:10
> To: Jacob Kroon ; openembedded-
> c...@lists.openembedded.org; bitbake-de...@lists.openembedded.org
> Subject: Re: [bitbake-
On 1/11/19 9:16 AM, Paul Barker wrote:
On Fri, 11 Jan 2019, at 17:05, Patchwork wrote:
== Series Details ==
Series: Shorten file names in sstate-cache
Revision: 1
URL : https://patchwork.openembedded.org/series/15617/
State : failure
That's weird... the patch applies fine onto master here, I
On Fri, 11 Jan 2019, at 17:05, Patchwork wrote:
> == Series Details ==
>
> Series: Shorten file names in sstate-cache
> Revision: 1
> URL : https://patchwork.openembedded.org/series/15617/
> State : failure
That's weird... the patch applies fine onto master here, I've just tested
applying it t
On Fri, 11 Jan 2019 at 16:53, Burton, Ross wrote:
>> I'm slightly worried that this will break on-target RPM users. Since info is
>> commonly enabled during on-target installations to track which packages have
>> been installed and what their progress is.
>>
>> Has it been test that this does not
== Series Details ==
Series: Shorten file names in sstate-cache
Revision: 1
URL : https://patchwork.openembedded.org/series/15617/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on
On Friday 11 January 2019 at 16:53:47 +, Richard Purdie wrote:
> On Fri, 2019-01-11 at 16:49 +, Mike Crowe wrote:
> > Until now, glibc was responsible for creating an AArch64 dynamic
> > loader symlink if required for ABI compatibility.
> >
> > Unfortunately, using multilib with AArch64 ca
With the recent move to using sha256 checksums in sstate, the lengths of
some file names can now exceed the 255 char limit seen in most Linux
filesystems. When this occurs, bitbake crashes as it is unable to create
the sstate archive or sigfile.
To avoid this issue we need to shorten the length of
As discussed briefly on IRC earlier in the week, here's a patch which attempts
to shorten the file name lengths seen in the sstate cache whilst retaining as
much useful human-readable info as possible.
This has been tested locally by building, wiping out tmp and then re-building to
confirm that ss
On Fri, 2019-01-11 at 16:49 +, Mike Crowe wrote:
> Until now, glibc was responsible for creating an AArch64 dynamic
> loader symlink if required for ABI compatibility.
>
> Unfortunately, using multilib with AArch64 caused the rmdir in
> glibc-package.inc:do_poststash_install_cleanup to fail be
Until now, glibc was responsible for creating an AArch64 dynamic loader
symlink if required for ABI compatibility.
Unfortunately, using multilib with AArch64 caused the rmdir in
glibc-package.inc:do_poststash_install_cleanup to fail because that task
did not expect to find the dynamic loader symli
== Series Details ==
Series: poky: add OpenSUSE LEAP 15.0 to SANITY_TESTED_DISTROS
Revision: 1
URL : https://patchwork.openembedded.org/series/15615/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests hav
We'll switch this when the autobuilder is building on 15.0. Currently the
15.0 worker is there but disabled, presumably it's not up and running yet.
Ross
On Fri, 11 Jan 2019 at 16:06, Richard Weinberger wrote:
> All my build systems (and containers) run LEAP 15.0.
> So far everything worked fi
Op 10-01-19 om 21:52 schreef Marek Vasut:
On 1/10/19 9:49 PM, Marek Vasut wrote:
On 1/10/19 9:48 PM, akuster808 wrote:
On 1/10/19 8:23 AM, Ferry Toth wrote:
After a new checkout I am experiencing multiple errors building Sumo
that might be related:
bison-3.0.4
cross-localedef-native_2.27
c
All my build systems (and containers) run LEAP 15.0.
So far everything worked fine, let's get rid of the warning. :-)
Signed-off-by: Richard Weinberger
---
meta-poky/conf/distro/poky.conf | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/
On Fri, 11 Jan 2019 at 15:50, Mark Hatle wrote:
> I'm slightly worried that this will break on-target RPM users. Since info
> is
> commonly enabled during on-target installations to track which packages
> have
> been installed and what their progress is.
>
> Has it been test that this does not b
I'm slightly worried that this will break on-target RPM users. Since info is
commonly enabled during on-target installations to track which packages have
been installed and what their progress is.
Has it been test that this does not break dnf on the target?
--Mark
On 1/11/19 4:43 AM, Alexander
On Fri, Jan 11, 2019 at 4:50 AM Alexey Brodkin
wrote:
>
> For that we need 2 things:
> 1. Disable JIT in JS as it's not supported for ARC.
>
> 2. Compile with "-mlong-calls" so relocations with
> offsets larger than 25 bits are used, otherwise
> linker fails to link final binaries.
>
> S
On Thu, 10 Jan 2019 at 22:10, Alistair Francis wrote:
> > * Issue A patch file has been added, but does not have a
> Signed-off-by tag [test_signed_off_by_presence]
> > Suggested fixSign off the added patch file
> (meta/recipes-multimedia/gstreamer/files/0002-gstconfig.h.in-init
I'm wondering what the point of checking the output of mount is. If we're
just checking that the image booted then the grep is sufficient right?
Ross
On Fri, 11 Jan 2019 at 09:22, Kang Kai wrote:
> On 2019/1/4 上午10:49, kai.k...@windriver.com wrote:
> > From: Kai Kang
> >
> > It checks output
== Series Details ==
Series: webkitgtk: Enable building for ARC architecture
Revision: 1
URL : https://patchwork.openembedded.org/series/15614/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
For that we need 2 things:
1. Disable JIT in JS as it's not supported for ARC.
2. Compile with "-mlong-calls" so relocations with
offsets larger than 25 bits are used, otherwise
linker fails to link final binaries.
Signed-off-by: Alexey Brodkin
Cc: Alexander Kanavin
Cc: Hongxu Jia
--
The maintainer lost access to the smmap PyPi account so as with gitdb, set the
PyPi name to smmap2.
Signed-off-by: Ross Burton
---
meta/recipes-devtools/python/python-smmap.inc | 6 --
.../python/{python3-smmap_0.9.0.bb => python3-smmap_2.0.5.bb} | 0
2 files chan
Op 10-01-19 om 21:48 schreef akuster808:
On 1/10/19 8:23 AM, Ferry Toth wrote:
After a new checkout I am experiencing multiple errors building Sumo
that might be related:
bison-3.0.4
cross-localedef-native_2.27
coreutils-8.29
On another machine with slightly out-of-date Sumo these problems
Previously there was lots of irrelevant noise in the logs,
because we also wanted to be able to debug postinst issues
easily. I have adjusted the logging levels so that
postinst info is still written to the logs, but other
things are not.
[YOCTO #13119]
Signed-off-by: Alexander Kanavin
---
meta
On 2019/1/4 上午10:49, kai.k...@windriver.com wrote:
From: Kai Kang
It checks output of mount in wic test case test_qemu. But the outputs are
different between sysvinit and systemd. Add assertion for systemd.
Signed-off-by: Kai Kang
---
meta/lib/oeqa/selftest/cases/wic.py | 5 -
1 file c
Backport patches for ld/gold from master
[YOCTO# 13136]
Signed-off-by: Khem Raj
---
.../binutils/binutils-2.31.inc| 2 +
...essed-header-alignment-correctly-by-.patch | 332 ++
...nt-of-uncompressed-section-from-ch_a.patch | 200 +++
3 files changed, 53
Backport patches for ld/gold from master
[YOCTO# 13136]
Signed-off-by: Khem Raj
---
.../binutils/binutils-2.31.inc| 2 +
...essed-header-alignment-correctly-by-.patch | 332 ++
...nt-of-uncompressed-section-from-ch_a.patch | 200 +++
3 files changed, 53
32 matches
Mail list logo
