Since commit [df313aa810 pseudo: Fix to work with glibc 2.34
systems] applied, it fixed native only. And nativesdk has
the similar issue
Tweak library search order, make prebuilt lib ahead of recipe lib,
after apply the fix:
...
$ readelf -a lib/pseudo/lib64/libpseudo.so | grep 'Shared library'
From: Kai Kang
When pam is enabled, it complains installed-vs-shipped QA issue:
| ERROR: libcgroup-2.0-r0 do_package: QA Issue: libcgroup:
Files/directories were installed but not shipped in any package:
| /lib/security/pam_cgroup.a
Signed-off-by: Kai Kang
---
On 8/25/21 11:35 PM, Khem Raj wrote:
On 8/25/21 1:10 AM, kai wrote:
From: Kai Kang
libpam disables static build by default, so remove static pam library of
libcgroup. Otherwise it complains QA issue:
| ERROR: libcgroup-2.0-r0 do_package: QA Issue: libcgroup:
Files/directories
This is done when starting up qemu has failed, but is not done
when qemu started ok, but fails later in QMP communication.
Output from runqemu does contain valuable information to find out
why, so rather than fix all the QMP fails to include it, let's just
print it in stop().
Signed-off-by:
Mitigate pathname truncation when installing in a project
with a very long pathname.
Signed-off-by: Joe Slater
---
...pkgdata-increase-command-buffer-size.patch | 46 +++
meta/recipes-support/icu/icu_68.2.bb | 1 +
2 files changed, 47 insertions(+)
create mode 100644
It used to be that 'exit 1' was the way to defer to boot time, but that was
changed long time ago to not be ambiguous like that and cause a real
failure at build time. Deferring to first boot needs to be explicitly
requested with _ontarget() (you can read the definition for it to see what
really
libhidapi-libusb needs to convert from UTF-16LE to WCHAR_T in order to
read various libusb string descriptors.
Signed-off-by: Justin Bronder
---
meta-oe/recipes-support/hidapi/hidapi_git.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta-oe/recipes-support/hidapi/hidapi_git.bb
Quoting Phil Blundell :
That's testing for offline installation. If $D is not set, it's
running on the target.
p.
one last query before i head off for dinner ... so what about
pkg_postinst() routines that do double duty, like this one from
dbus_1.12.20.bb:
PACKAGE_WRITE_DEPS +=
_ontarget() is basically syntactic sugar for $D test, but yes it's the new
preferred form. If you see $D, that means the recipe hasn't been converted.
Alex
On Wed, 25 Aug 2021 at 23:27, Robert P. J. Day
wrote:
>
> Quoting Phil Blundell :
>
> > That's testing for offline installation. If $D is
Quoting Phil Blundell :
That's testing for offline installation. If $D is not set, it's
running on the target.
p.
right, that's exactly what i suspected in my original posting,
i just wanted to make sure, which raises a couple issues.
first, that distinction doesn't seem to be
That's testing for offline installation. If $D is not set, it's running on the
target.
p.
On 25 August 2021 22:12:22 BST, "Robert P. J. Day"
wrote:
>
>Quoting Alexander Kanavin :
>
>> If you show the confusing examples, we could try to figure it out.
>>
>> Alex
>>
>> On Wed, 25 Aug 2021 at
Quoting Alexander Kanavin :
If you show the confusing examples, we could try to figure it out.
Alex
On Wed, 25 Aug 2021 at 22:35, Robert P. J. Day
wrote:
there will be many more questions about pkg_postinst (and related)
routines shortly, but digging into these for the first time, i
If you show the confusing examples, we could try to figure it out.
Alex
On Wed, 25 Aug 2021 at 22:35, Robert P. J. Day
wrote:
>
> there will be many more questions about pkg_postinst (and related)
> routines shortly, but digging into these for the first time, i
> thought that that test checked
there will be many more questions about pkg_postinst (and related)
routines shortly, but digging into these for the first time, i
thought that that test checked whether the routine was being run
at image creation time, or at first-time boot. now i'm not quite
sure what to think after seeing
* All ptests pass on qemux86-64
pluggy 1.0.0 (2021-08-25)
Deprecations and Removals
#116: Remove deprecated implprefix support. Decorate hook
implementations using an instance of HookimplMarker instead.
The deprecation was announced in release 0.7.0.
#120: Remove the
On Wed, 2021-08-25 at 21:31 +0200, Alexander Kanavin wrote:
> On Wed, 25 Aug 2021 at 21:26, Bruce Ashfield wrote:
> > I mentioned meta-virtualization in the non-threaded part of this
> > discussion, so that specific information has been covered. Sakib is a
> > contributor there (and isn't new to
On Wed, 25 Aug 2021 at 21:26, Bruce Ashfield
wrote:
> I mentioned meta-virtualization in the non-threaded part of this
> discussion, so that specific information has been covered. Sakib is a
> contributor there (and isn't new to core), and knows what he's doing,
> hence why I have the luxury of
On Wed, Aug 25, 2021 at 3:14 PM Alexander Kanavin
wrote:
>
> On Wed, 25 Aug 2021 at 21:05, Bruce Ashfield wrote:
>>
>> Let's agree to disagree. Anyone doing toolchain work, needs to have an
>> extra level of caution.
>>
>> I'm constantly dealing with kernel issues and tightly coupled
>>
On Wed, 25 Aug 2021 at 21:05, Bruce Ashfield
wrote:
> Let's agree to disagree. Anyone doing toolchain work, needs to have an
> extra level of caution.
>
> I'm constantly dealing with kernel issues and tightly coupled
> applications in all layers that have nothing in core. I don't simply
> tell
On Wed, Aug 25, 2021 at 2:58 PM Alexander Kanavin
wrote:
>
> On Wed, 25 Aug 2021 at 19:45, Bruce Ashfield wrote:
>>
>> >
>> > bitbake core-image-full-cmdline && bitbake core-image-full-cmdline -c
>> > testimage
>> >
>> > Result:
>> >
>> > World build passes without warnings/errors.
>> >
>> >
On Wed, 25 Aug 2021 at 19:45, Bruce Ashfield
wrote:
> >
> > bitbake core-image-full-cmdline && bitbake core-image-full-cmdline -c
> testimage
> >
> > Result:
> >
> > World build passes without warnings/errors.
> >
> > All image tests passed
>
> But do any of those test images have anything more
On Wed, Aug 25, 2021 at 1:30 PM Sakib Sajal wrote:
>
> Testing done:
>
> bitbake -k world
I assume that only oe-core is in the bblayers ? or is it more extensive ?
>
> bitbake core-image-full-cmdline && bitbake core-image-full-cmdline -c
> testimage
>
> Result:
>
> World build passes without
Testing done:
bitbake -k world
bitbake core-image-full-cmdline && bitbake core-image-full-cmdline -c
testimage
Result:
World build passes without warnings/errors.
All image tests passed
Sakib
On 2021-08-25 1:20 p.m., Sakib Sajal wrote:
go 1.17 includes small enhancements to the
On Wed, Aug 25, 2021 at 1:21 PM Sakib Sajal wrote:
>
> go 1.17 includes small enhancements to the language.
> Release notes: https://golang.org/doc/go1.17
What testing has been done on this update ?
This is late in the current development cycle, and layers like
meta-virt take the brunt of the
go 1.17 includes small enhancements to the language.
Release notes: https://golang.org/doc/go1.17
Signed-off-by: Sakib Sajal
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
.../go/{go-1.16.5.inc => go-1.17.inc} | 6 +-
...ow-CC-and-CXX-to-have-multiple-words.patch | 10 ++-
From: Bruce Ashfield
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
c15b830f7c1c Linux 5.4.142
a17f2f2c8949 KVM: nSVM: always intercept VMLOAD/VMSAVE when nested
(CVE-2021-3656)
7c1c96ffb658 KVM: nSVM: avoid picking up unsupported
From: Bruce Ashfield
Updating linux-yocto/5.10 to the latest korg -stable release that comprises
the following commits:
2c5bd949b1df Linux 5.10.60
3a24e121304a net: dsa: microchip: ksz8795: Use software untagging on CPU
port
1e78179d75fb net: dsa: microchip: ksz8795: Fix VLAN
From: Bruce Ashfield
Updating linux-yocto/5.13 to the latest korg -stable release that comprises
the following commits:
a3f1a03f54fc Linux 5.13.11
41812f4b8448 ovl: prevent private clone if bind mount is not allowed
2b187b56d531 ppp: Fix generating ppp unit id when ifname is not
From: Bruce Ashfield
Updating linux-yocto/5.13 to the latest korg -stable release that comprises
the following commits:
f428e49b8cb1 Linux 5.13.12
639a033fd765 KVM: nSVM: always intercept VMLOAD/VMSAVE when nested
(CVE-2021-3656)
a0949ee63cf9 KVM: nSVM: avoid picking up unsupported
From: Bruce Ashfield
Updating linux-yocto/5.10 to the latest korg -stable release that comprises
the following commits:
5805e5eec901 Linux 5.10.59
25cff25ec606 net: xilinx_emaclite: Do not print real IOMEM pointer
6a002d48a660 ovl: prevent private clone if bind mount is not allowed
From: Bruce Ashfield
Richard,
Nothing too exciting here. These have all build locally and I haven't picked
up any issues (I've stayed off the AB, due to the extra load you mentioned
it has been under).
Cheers,
Bruce
The following changes since commit c3e72164e7a0c51de04a9295e5f50c2e233965f7:
Includes fixes for:
CVE: CVE-2021-3711
CVE: CVE-2021-3712
as described by:
https://www.openssl.org/news/secadv/20210824.txt
Ptest results on qemux86-64 with kvm:
All tests successful.
Files=158, Tests=2532, 93 wallclock secs \
( 1.31 usr 0.14 sys + 73.43 cusr 12.65 csys = 87.53
On 2021-08-24 1:01 p.m., Slater, Joseph wrote:
https://unicode-org.atlassian.net/browse/ICU-21702 has been accepted. My patch
just mitigates the problem but does not take care of issues around lack of
error reporting.
Joe
That's good. Can you update the patch to include that link
and pick
On 8/25/21 1:10 AM, kai wrote:
From: Kai Kang
libpam disables static build by default, so remove static pam library of
libcgroup. Otherwise it complains QA issue:
| ERROR: libcgroup-2.0-r0 do_package: QA Issue: libcgroup:
Files/directories were installed but not shipped in any
Hello Peter,
On Wed, Aug 25, 2021 at 3:21 PM Peter Kjellerstedt
wrote:
>
> Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch was updated
> with the 2.13.0 update (commit 5dad15af), but unfortunately it no
> longer did what it was intended to do. There is also
>
On Wed, Aug 25, 2021 at 9:51 AM Peter Kjellerstedt
wrote:
>
> As I was recently looking at lttng-modules, which supports devupstream, I
> wanted to try to build the devupstream variant. However, neither the
> information in devupstream.bbclass nor the documentation in the manual were
> of any
As I was recently looking at lttng-modules, which supports devupstream, I
wanted to try to build the devupstream variant. However, neither the
information in devupstream.bbclass nor the documentation in the manual were of
any help. Since it uses the BBCLASSEXTEND mechanism, I thought it would
On Wed, Aug 25, 2021 at 9:40 AM Peter Kjellerstedt
wrote:
>
> > -Original Message-
> > From: Bruce Ashfield
> > Sent: den 25 augusti 2021 15:18
> > To: Peter Kjellerstedt
> > Cc: Andrey Zhizhikin ; OE Core mailing list
> >
> > Subject: Re: [OE-core] [PATCH] lttng-modules: Make it build
> -Original Message-
> From: Bruce Ashfield
> Sent: den 25 augusti 2021 15:18
> To: Peter Kjellerstedt
> Cc: Andrey Zhizhikin ; OE Core mailing list
>
> Subject: Re: [OE-core] [PATCH] lttng-modules: Make it build when
> CONFIG_TRACEPOINTS is not enabled again
>
> On Wed, Aug 25, 2021
Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch was updated
with the 2.13.0 update (commit 5dad15af), but unfortunately it no
longer did what it was intended to do. There is also
0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch, which
was based on the former patch, but it
On Wed, Aug 25, 2021 at 8:57 AM Peter Kjellerstedt
wrote:
>
> > -Original Message-
> > From: Andrey Zhizhikin
> > Sent: den 25 augusti 2021 12:20
> > To: Peter Kjellerstedt
> > Cc: Bruce Ashfield ; OE Core mailing list
> >
> > Subject: Re: [OE-core] [PATCH] lttng-modules: Make it build
> -Original Message-
> From: Andrey Zhizhikin
> Sent: den 25 augusti 2021 12:20
> To: Peter Kjellerstedt
> Cc: Bruce Ashfield ; OE Core mailing list
>
> Subject: Re: [OE-core] [PATCH] lttng-modules: Make it build when
> CONFIG_TRACEPOINTS is not enabled again
>
> Hello Peter,
>
> On
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Robert P. J. Day
> Sent: den 25 augusti 2021 14:42
> To: Ross Burton
> Cc: OE Core mailing list
> Subject: Re: [OE-core] should "${D}${systemd_unitdir}/system" =>
>
On Wed, 18 Aug 2021, Ross Burton wrote:
> No, yes. systemd_system_unitdir is newer so it's used less.
>
> Ross
>
> On Wed, 18 Aug 2021 at 08:48, Robert P. J. Day wrote:
> >
> >
> > i've (so far) run across a small number of OE recipes that use the
> > identifier
Signed-off-by: Alexander Kanavin
---
.../harfbuzz/{harfbuzz_2.8.2.bb => harfbuzz_2.9.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/harfbuzz/{harfbuzz_2.8.2.bb => harfbuzz_2.9.0.bb}
(95%)
diff --git
Upstream has converted from gtk-doc to gi-docgen.
Signed-off-by: Alexander Kanavin
---
.../json-glib/{json-glib_1.6.2.bb => json-glib_1.6.4.bb} | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
rename meta/recipes-gnome/json-glib/{json-glib_1.6.2.bb => json-glib_1.6.4.bb}
(77%)
Signed-off-by: Alexander Kanavin
---
meta/recipes-gnome/gi-docgen/gi-docgen_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-gnome/gi-docgen/gi-docgen_git.bb
b/meta/recipes-gnome/gi-docgen/gi-docgen_git.bb
index 8f33bec8da..f319f96b0e 100644
---
Signed-off-by: Alexander Kanavin
---
meta/recipes-extended/libnsl/libnsl2_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-extended/libnsl/libnsl2_git.bb
b/meta/recipes-extended/libnsl/libnsl2_git.bb
index badb71d977..53be67fe85 100644
---
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/vala/{vala_0.52.4.bb => vala_0.52.5.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/vala/{vala_0.52.4.bb => vala_0.52.5.bb} (50%)
diff --git a/meta/recipes-devtools/vala/vala_0.52.4.bb
Signed-off-by: Alexander Kanavin
---
.../openssh/{openssh_8.6p1.bb => openssh_8.7p1.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-connectivity/openssh/{openssh_8.6p1.bb =>
openssh_8.7p1.bb} (98%)
diff --git
Signed-off-by: Alexander Kanavin
---
.../python/{python3-mako_1.1.4.bb => python3-mako_1.1.5.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-mako_1.1.4.bb =>
python3-mako_1.1.5.bb} (82%)
diff --git
Signed-off-by: Alexander Kanavin
---
meta/recipes-core/ell/{ell_0.42.bb => ell_0.43.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-core/ell/{ell_0.42.bb => ell_0.43.bb} (90%)
diff --git a/meta/recipes-core/ell/ell_0.42.bb
b/meta/recipes-core/ell/ell_0.43.bb
Signed-off-by: Alexander Kanavin
---
.../bluez5/{bluez5_5.60.bb => bluez5_5.61.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-connectivity/bluez5/{bluez5_5.60.bb => bluez5_5.61.bb}
(95%)
diff --git
Signed-off-by: Alexander Kanavin
---
.../0001-avoid-start-failure-with-bind-user.patch | 0
.../0001-named-lwresd-V-and-start-log-hide-build-options.patch | 0
.../bind-ensure-searching-for-json-headers-searches-sysr.patch | 0
.../bind/{bind-9.16.19 => bind-9.16.20}/bind9
Signed-off-by: Alexander Kanavin
---
...2.37.1.bb => util-linux-libuuid_2.37.2.bb} | 0
meta/recipes-core/util-linux/util-linux.inc | 3 +-
.../util-linux/CVE-2021-37600.patch | 33 ---
...l-linux_2.37.1.bb => util-linux_2.37.2.bb} | 0
4 files changed, 1
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/git/{git_2.32.0.bb => git_2.33.0.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/git/{git_2.32.0.bb => git_2.33.0.bb} (51%)
diff --git a/meta/recipes-devtools/git/git_2.32.0.bb
License-Update: formatting
Signed-off-by: Alexander Kanavin
---
.../recipes-devtools/ccache/{ccache_4.3.bb => ccache_4.4.bb} | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/ccache/{ccache_4.3.bb => ccache_4.4.bb} (73%)
diff --git
Drop merged 0001-correctly-use-3-parameters-for-close_range.patch
Signed-off-by: Alexander Kanavin
---
...tly-use-3-parameters-for-close_range.patch | 29 ---
.../glib-2.0/glib-2.0/relocate-modules.patch | 2 +-
...{glib-2.0_2.68.3.bb => glib-2.0_2.68.4.bb} | 3 +-
3 files
This lengthens dependency chains unnecessarily;
also -native versions are already included in DEPENDS via binutils.inc:
DEPENDS = "flex-native bison-native zlib-native gnu-config-native
autoconf-native"
I have also checked that nothing in binutils needs anything from target
sysroots of
Removed non-existent header from licensing.
Signed-off-by: Alexander Kanavin
---
.../gnu-efi/{gnu-efi_3.0.13.bb => gnu-efi_3.0.14.bb} | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
rename meta/recipes-bsp/gnu-efi/{gnu-efi_3.0.13.bb => gnu-efi_3.0.14.bb} (93%)
diff --git
Hello Peter,
On Wed, Aug 25, 2021 at 11:41 AM Peter Kjellerstedt
wrote:
>
> Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch was updated
> with the 2.13.0 update (commit 5dad15af), but unfortunately it no longer
> did what it was intended to do.
>
> Signed-off-by: Peter Kjellerstedt
>
Makefile-Do-not-fail-if-CONFIG_TRACEPOINTS-is-not-en.patch was updated
with the 2.13.0 update (commit 5dad15af), but unfortunately it no longer
did what it was intended to do.
Signed-off-by: Peter Kjellerstedt
---
...fail-if-CONFIG_TRACEPOINTS-is-not-en.patch | 42 +++
1 file
From: Kai Kang
libpam disables static build by default, so remove static pam library of
libcgroup. Otherwise it complains QA issue:
| ERROR: libcgroup-2.0-r0 do_package: QA Issue: libcgroup:
Files/directories were installed but not shipped in any package:
| /lib/security/pam_cgroup.a
Hi Sergei,
Thanks for the advice, the latest ofono in oe-core master is 1.32, but
I am in branch Hardknott, so I copied ofono 1.32 from master to my
layer running Hardknott branch, but I could not build ofono 1.32 in
Hardknott:
ERROR: ParseError at
64 matches
Mail list logo
