Hi,
I was fighting with building chromium-x11 using our warrior
based custom distro that was always failing at the same spot.
That spot is when Chromium wants to run cross-compiled binaries
in the v8 directory. The binaries all failed with the same error:
python ../../v8/tools/run.py
ping
Once we enabled multilib, and IMAGE_INSTALL_append packages that also
provided by package target-sdk-provides-dummy,
task populate_sdk will failed, similar error like:
Problem: package
target-sdk-provides-dummy-1.0-r0.sdk_provides_dummy_target conflicts
with perl-dev provided by
From: Kai Kang
v2:
* update commit message
Kai Kang (1):
systemd: provides ${base_sbindir}/udevadm
meta/recipes-core/systemd/systemd_242.bb | 4
1 file changed, 4 insertions(+)
--
2.20.0
--
___
Openembedded-core mailing list
From: Kai Kang
In some udev rules files such as 97-hid2hci.rules from bluez5, it calls
/sbin/udevadm in a rule. eudev provides /usr/bin/udevadm and
/sbin/udevadm which is a link to /usr/bin/udevadm. But systemd only
provides /bin/udevadm. It is not convenient to update the rule file that
udevadm
All,
The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:
Hi Alex:
Ok, I will send a V3 patch.
--
Zheng Ruoqin
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
ADDR.: No.6 Wenzhu Road, Software Avenue,
Nanjing, 210012, China
MAIL : zhengrq.f...@cn.fujistu.com
From: Alexander Kanavin
On Mon, 2019-09-09 at 11:16 -0400, Trevor Gamblin wrote:
> From: Trevor Gamblin
>
> The libevent "regress" test outputs its own pass/fail results,
> e.g. "2/300 TESTS FAILED. (31 skipped)", which will be
> miscounted as an extra test fail in the ptest log. Fixed this
> to ignore the libevent
On Mon, Sep 9, 2019 at 2:01 PM Nicolas Dechesne
wrote:
> On Mon, Sep 9, 2019 at 10:58 PM Andre McCurdy wrote:
> >
> > On Mon, Sep 9, 2019 at 1:25 PM Nicolas Dechesne
> > wrote:
> > >
> > > If this reasoning is correct that means that kernel signing + external
> > > module is broken. Note that I
On 9/9/19 10:31 AM, msft.dant...@gmail.com wrote:
> From: Dan Tran
>
> Fixes CVE-2018-20623, CVE-2018-20651, CVE-2018-20-671, and
> CVE-2018-1000876 for binutils 2.31.1.
thanks. in thud test stagging.( contrib: stable/thud-nmut )
- armin
>
> Signed-off-by: Dan Tran
> ---
>
On Mon, Sep 9, 2019 at 10:58 PM Andre McCurdy wrote:
>
> On Mon, Sep 9, 2019 at 1:25 PM Nicolas Dechesne
> wrote:
> >
> > If this reasoning is correct that means that kernel signing + external
> > module is broken. Note that I am working out of Thud for now, i am
> > sending this email for now
On Mon, Sep 9, 2019 at 1:25 PM Nicolas Dechesne
wrote:
>
> If this reasoning is correct that means that kernel signing + external
> module is broken. Note that I am working out of Thud for now, i am
> sending this email for now to get some feedback, and will try to
> reproduce without all our
hi,
things are getting worse , my initial problem was only the visible
piece of the iceberg ;)
On Thu, Sep 5, 2019 at 5:42 PM Bruce Ashfield wrote:
>
> On Thu, Sep 5, 2019 at 10:43 AM Nicolas Dechesne
> wrote:
> >
> > hi,
> >
> > I was looking into a build issue today, related to signing an
On Mon, 9 Sep 2019 at 18:49, Ross Burton wrote:
> > As I had previously suggested... can you try adding 'python3' to DEPENDS
> > of mesa, and see if that helps please? I think that would allow avoiding
> > this patch altogether.
>
> So why does Meson need *target* Python to be present when
Based on poky master, but for version 1.32
Signed-off-by: Sean Nyekjaer
---
.../libgpg-error-1.32-gawk5-support.patch | 161 ++
.../libgpg-error/libgpg-error_1.32.bb | 1 +
2 files changed, 162 insertions(+)
create mode 100644
Based on poky master, but for version 1.35
Signed-off-by: Sean Nyekjaer
---
.../libgpg-error-1.35-gawk5-support.patch | 161 ++
.../libgpg-error/libgpg-error_1.35.bb | 1 +
2 files changed, 162 insertions(+)
create mode 100644
From: Dan Tran
Fixes CVE-2018-20852, CVE-2019-9740, and CVE-2019-9747
Signed-off-by: Dan Tran
---
.../python/python/bpo-30458-cve-2019-9740.patch| 219 +
.../python/python/bpo-35121-cve-2018-20852.patch | 127
On 9/8/19 10:31 AM, Sean Nyekjaer wrote:
> Based on poky master, but for version 1.35
thanks.
can you include the patch fixup in master too?
From: Dan Tran
Fixes CVE-2018-20623, CVE-2018-20651, CVE-2018-20-671, and
CVE-2018-1000876 for binutils 2.31.1.
Signed-off-by: Dan Tran
---
meta/recipes-devtools/binutils/binutils-2.31.inc | 4 +
.../binutils/binutils/CVE-2018-1000876.patch | 180 +
On 06/09/2019 20:07, Alexander Kanavin wrote:
As I had previously suggested... can you try adding 'python3' to DEPENDS
of mesa, and see if that helps please? I think that would allow avoiding
this patch altogether.
So why does Meson need *target* Python to be present when building Mesa?
Ross
Remove the broken piece of the API documentation template so the documentation
can be generated again.
Signed-off-by: Ross Burton
---
.../gstreamer1.0-libav/gtkdoc-no-tree.patch | 24 +++
.../gstreamer/gstreamer1.0-libav_1.16.0.bb| 6 +
2 files changed, 25
On 9/9/19 11:16 AM, Trevor Gamblin wrote:
From: Trevor Gamblin
The libevent "regress" test outputs its own pass/fail results,
e.g. "2/300 TESTS FAILED. (31 skipped)", which will be
miscounted as an extra test fail in the ptest log. Fixed this
to ignore the libevent results line when counting
From: Trevor Gamblin
The libevent "regress" test outputs its own pass/fail results,
e.g. "2/300 TESTS FAILED. (31 skipped)", which will be
miscounted as an extra test fail in the ptest log. Fixed this
to ignore the libevent results line when counting actual
pass/fail results.
Also removed the
Thanks, now it's future-proof :)
Alex
On Mon, 9 Sep 2019 at 16:54, Fabio Berton
wrote:
> Hi Alexander!
>
> I sent a v2 with python3 in depends and dropped the patch.
>
> Thanks!
>
> On Fri, Sep 6, 2019 at 5:33 PM Alexander Kanavin
> wrote:
> >
> > On Fri, 6 Sep 2019 at 22:12, Otavio Salvador
Hi Alexander!
I sent a v2 with python3 in depends and dropped the patch.
Thanks!
On Fri, Sep 6, 2019 at 5:33 PM Alexander Kanavin wrote:
>
> On Fri, 6 Sep 2019 at 22:12, Otavio Salvador
> wrote:
>>
>> > As I had previously suggested... can you try adding 'python3' to DEPENDS
>> > of mesa,
From: Otavio Salvador
- Add python3 to DEPENDS: mesa commit cb3072488c changed function
that verifies python installation and to this new function works
we need to have Python3 in DEPENDS.
This is a bugfix only set of releases. Check following links for the
relevant release notes:
On Mon, Sep 9, 2019 at 2:52 AM Ross Burton wrote:
>
> There's a 0.177 upgrade on the list (and in mut), is this required for
> that too?
>
if the patch which we are removing with this change is used
then yes it is needed.
> Ross
>
> On 09/09/2019 00:23, Khem Raj wrote:
> > musl relies on the
On Mon, Sep 9, 2019 at 12:44 AM Richard Purdie
wrote:
>
> On Sun, 2019-09-08 at 20:16 -0700, Khem Raj wrote:
> > This helps recipes where they need to explicitly pass the variable
> > and
> > does not entertain the ones from environment
> >
> > Signed-off-by: Khem Raj
> > ---
> >
== Series Details ==
Series: libevent: add granularity to ptest log (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/19759/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
On 9/9/19 9:35 AM, Trevor Gamblin wrote:
From: Trevor Gamblin
The libevent ptest used to report only a global pass or a fail result.
Count individual PASS, FAIL, SKIP results. The SKIP results now
include tests that are disabled in the libevent code.
libevent's ptest output did not comply
From: Trevor Gamblin
The libevent ptest used to report only a global pass or a fail result.
Count individual PASS, FAIL, SKIP results. The SKIP results now
include tests that are disabled in the libevent code.
libevent's ptest output did not comply with the automake-style output
"result:
On Mon, 9 Sep 2019 at 13:19, Zheng, Ruoqin
wrote:
> ->What do these two sed commands do? If we create /etc/rpmrc just above,
> can it have the right content from the beginning?
>
>
>
> Well, in the environment in Yocto Build system, the value of
> ${PACKAGE_ARCHS} include “–nativesdk” as not
On 09/09/2019 14:02, Ross Burton wrote:
On 05/09/2019 12:19, changqing...@windriver.com wrote:
+
${@bb.utils.contains('DISTRO_FEATURES','usrmerge','file://0001-bootchart2-support-usrmerge.patch','',d)}
\
Conditionally applying patches is rarely a good move. Why not always
apply
On 05/09/2019 12:19, changqing...@windriver.com wrote:
+
${@bb.utils.contains('DISTRO_FEATURES','usrmerge','file://0001-bootchart2-support-usrmerge.patch','',d)}
\
Conditionally applying patches is rarely a good move. Why not always
apply this?
Ross
--
Signed-off-by: Ross Burton
---
.../gnutls/libtasn1/fix-gtkdoc.patch | 38 +++
meta/recipes-support/gnutls/libtasn1_4.14.bb | 1 +
2 files changed, 39 insertions(+)
create mode 100644 meta/recipes-support/gnutls/libtasn1/fix-gtkdoc.patch
diff --git
We need to configure rpm to use package architecture from yocto build system.
Install rpmrc and rpm/platform to ${SDKTARGETSYSROOT} because config file in
host-sysroot as /opt/poky/2.7+snapshot/sysroots/x86_64-pokysdk-linux will be
covered by another ARCH which result in prvious config settings
Hi Alex
I’d like to explain it.
->Why not simply ${D}/etc/rpm?
As you see, ${SDKTARGETSYSROOT} for x86_64 is
/opt/poky/2.7+snapshot/sysroots/core2-64-pokysdk-linux.
I make it because config file in host-sysroot as
/opt/poky/2.7+snapshot/sysroots/x86_64-pokysdk-linux will be covered by
On Mon, 9 Sep 2019 at 13:08, Zheng, Ruoqin
wrote:
> I'd like to explain the path ${SDKTARGETSYSROOT} in this patch.
>
> As you see, ${SDKTARGETSYSROOT} for x86_64 is
> /opt/poky/2.7+snapshot/sysroots/core2-64-pokysdk-linux.
>
> I make it because config file in host-sysroot as
>
Hi Alex
I'd like to explain the path ${SDKTARGETSYSROOT} in this patch.
As you see, ${SDKTARGETSYSROOT} for x86_64 is
/opt/poky/2.7+snapshot/sysroots/core2-64-pokysdk-linux.
I make it because config file in host-sysroot as
/opt/poky/2.7+snapshot/sysroots/x86_64-pokysdk-linux will be covered
On Mon, 9 Sep 2019 at 12:58, Zheng Ruoqin
wrote:
> rm -rf ${D}/var
> +install -d ${D}/${SDKTARGETSYSROOT}/etc/rpm
>
Why not simply ${D}/etc/rpm?
> +sed -i 's/-nativesdk//g' ${D}/${SDKTARGETSYSROOT}/etc/rpmrc
> +sed -i 's/-/_/'
We need to configure rpm to use package architecture from yocto build
system.
Signed-off-by: Zheng Ruoqin
---
meta/recipes-devtools/rpm/rpm_4.14.2.1.bb | 15 +++
1 file changed, 15 insertions(+)
diff --git a/meta/recipes-devtools/rpm/rpm_4.14.2.1.bb
| In file included from ../git/lib/alg-des.c:66:
| ../git/lib/alg-des.c: In function '_crypt_des_set_key':
| ../git/lib/byteorder.h:24:1: error: inlining failed in call to 'be32_to_cpu':
call is unlikely and code size would grow [-Werror=inline]
| be32_to_cpu (const unsigned char *buf)
|
On 09/09/2019 06:41, Zang Ruochen wrote:
Signed-off-by: Zang Ruochen
---
meta/recipes-core/libxcrypt/{libxcrypt_4.4.8.bb => libxcrypt_4.4.9.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-core/libxcrypt/{libxcrypt_4.4.8.bb => libxcrypt_4.4.9.bb}
(94%)
diff
There's a 0.177 upgrade on the list (and in mut), is this required for
that too?
Ross
On 09/09/2019 00:23, Khem Raj wrote:
musl relies on the pt_regs definitions from kernel ptrace headers
Signed-off-by: Khem Raj
---
.../elfutils/elfutils_0.176.bb| 1 +
On Sun, 2019-09-08 at 20:16 -0700, Khem Raj wrote:
> This helps recipes where they need to explicitly pass the variable
> and
> does not entertain the ones from environment
>
> Signed-off-by: Khem Raj
> ---
> meta/classes/python3native.bbclass | 6 --
> meta/classes/pythonnative.bbclass |
44 matches
Mail list logo
