Avoid gcc12 failure to inline function on mips
Signed-off-by: Khem Raj
---
...t-Do-not-use-always_inline-with-mips.patch | 33 +++
meta/recipes-devtools/ccache/ccache_4.6.bb| 5 ++-
2 files changed, 37 insertions(+), 1 deletion(-)
create mode 100644
This is a workaround for issue reported with gcc12 [1]
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105234
Signed-off-by: Khem Raj
---
meta/recipes-support/gnupg/gnupg_2.3.4.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-support/gnupg/gnupg_2.3.4.bb
On Mon, Apr 11, 2022, 3:33 PM Ralph Siemsen
wrote:
> On Mon, Apr 11, 2022 at 6:43 PM Steve Sakoman wrote:
> >
> > I was using qemux86-64 for my experiment, so I guess I need to redo it
> > now using the correct machine!
>
> I have rebuild with MACHINE=qemux86. Same result, all tests appear to
On Mon, Apr 11, 2022 at 6:43 PM Steve Sakoman wrote:
>
> I was using qemux86-64 for my experiment, so I guess I need to redo it
> now using the correct machine!
I have rebuild with MACHINE=qemux86. Same result, all tests appear to pass:
RESULTS - apt.AptRepoTest.test_apt_install_from_repo:
Backport a patch to fix
| ../git/util.cxx:1766:56: error: 'std::pointer_to_unary_function<_Arg,
_Result> std::ptr_fun(_Result (*)(_Arg)) [with _Arg = int; _Result = int]' is
deprecated: use 'std::function' instea
d [-Werror=deprecated-declarations]
| 1766 |
backport patch to silence new array-bounds warnings
Signed-off-by: Khem Raj
---
.../0001-render-Fix-build-with-gcc-12.patch | 90 +++
.../xorg-xserver/xserver-xorg_21.1.3.bb | 1 +
2 files changed, 91 insertions(+)
create mode 100644
These settings are good for developers/maintainers but for distributions
generally disabling them turns out to be better especially when there is
a knob to do so. This fixes build with gcc-12 which find additional
warnings
inlined from 'bt_ctf_object_set_parent' at
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:
On Mon, Apr 11, 2022 at 12:30 PM Ralph Siemsen wrote:
>
> On Mon, Apr 11, 2022 at 2:58 PM Steve Sakoman wrote:
>
> > Let me know if you make any progress!
>
> After a clean build, and messing about with VNC, I am now able to
> 'bitbake core-image-sato:do_testimage'.
>
> > Yes, either change will
On Mon, Apr 11, 2022 at 2:58 PM Steve Sakoman wrote:
> Let me know if you make any progress!
After a clean build, and messing about with VNC, I am now able to
'bitbake core-image-sato:do_testimage'.
> Yes, either change will trigger the error. Without the zlib or xz
> patches all is fine.
[PATCH v3 1/1] apt: add apt selftest to test signed package feeds
Since Gatesgarth apt (1.8.2) has become more strict and doesn’t allow unsigned
repositories by default.
Currently when building images this requirement is worked around by using
[allow-insecure=yes] and
equivalently when
From: Ferry Toth
Since Gatesgarth apt (1.8.2) has become more strict and doesn’t allow unsigned
repositories by default.
Currently when building images this requirement is worked around by using
[allow-insecure=yes] and
equivalently when performing selftest.
Patches "gpg-sign: Add parameters
[PATCH v3 1/1] apt: add apt selftest to test signed package feeds
Since Gatesgarth apt (1.8.2) has become more strict and doesn’t allow unsigned
repositories by default.
Currently when building images this requirement is worked around by using
[allow-insecure=yes] and
equivalently when
On Mon, Apr 11, 2022 at 8:17 AM Ralph Siemsen wrote:
>
> On Mon, Apr 11, 2022 at 1:52 PM Steve Sakoman wrote:
>
> > I see from irc that you've discovered INHERIT += "testimage". I think
> > that might help with the above issue.
>
> Indeed, I added that, which solved the missing do_testimage
On Mon, Apr 11, 2022 at 1:52 PM Steve Sakoman wrote:
> I see from irc that you've discovered INHERIT += "testimage". I think
> that might help with the above issue.
Indeed, I added that, which solved the missing do_testimage problem.
However even after rebuilding core-image sato, I do not have
On Mon, Apr 11, 2022 at 7:31 AM Ralph Siemsen wrote:
>
> On Mon, Apr 4, 2022 at 11:22 AM Steve Sakoman wrote:
>
> > > Unfortunately this triggers other errors too :-(
> > >
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/4987
> > >
On Mon, Apr 4, 2022 at 11:22 AM Steve Sakoman wrote:
> > Unfortunately this triggers other errors too :-(
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/4987
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/4949
Both of these seem to fail in
This file is introduced in newer kernels >= 5.15 but some RISCV machines
still use 5.13 kernels, this ensures that kernel-devsrc can build on
older kernels for RISCV
Signed-off-by: Khem Raj
---
meta/recipes-kernel/linux/kernel-devsrc.bb | 8 ++--
1 file changed, 6 insertions(+), 2
This file is introduced in newer kernels >= 5.15 but some RISCV machines
still use 5.13 kernels, this ensures that kernel-devsrc can build on
older kernels for RISCV
Signed-off-by: Khem Raj
---
meta/recipes-kernel/linux/kernel-devsrc.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
On Mon, Apr 11, 2022 at 6:01 AM Davide Gardenal
wrote:
>
> Hi Quentin,
>
> I just missed the release so I'm going to send a v3 patch now, thanks!
This patch is perhaps still valid for kirkstone. For upgrading to
3.6.1 I already sent a patch yesterday [1]
[1]
This function returns True if any of the specified packages are skipped due to
incompatible license.
License exceptions are obeyed. The user may specify the package's license for
cross-recipe checks.
This allows for additions to packagegroups only for non-incompatible builds. For
example:
On Mon, Apr 11, 2022 at 6:30 AM Jose Quaresma wrote:
>
>
>
> J?rg Vehlow escreveu no dia segunda, 11/04/2022 à(s) 13:35:
>>
>> From: Joerg Vehlow
>>
>> When gos internal linker is used, it uses hardcoded paths to the
>> interpreter (dynamic linker). For x86_64 this hardcoded path is
>>
On Sat, Apr 9, 2022 at 5:17 PM Richard Purdie
wrote:
>
> On Fri, 2022-04-08 at 15:25 -0400, Jon Mason wrote:
> > Changes in v2:
> > * Addressed Khem's comments
> > * Rebased to the latest version
> > * Added distro description for poky-tiny, as this makes it more obvious
> > which distro is
Hello,
with the deprecation of SERIAL_CONSOLE the following was introduced in
bitbake.conf:
3f0d665384e6d1b7aa2854a9cc4f13e0961bacb7 (bitbake.conf: set SERIAL_CONSOLES from
SERIAL_CONSOLE by default)
Since this is done after inclusion of local.conf and .conf any weak
default
done for a
Hello,
I'm already carrying this upgrade from Khem, earlier today.
On 11/04/2022 15:21:45+0200, Davide Gardenal wrote:
> This release contains security fixes
> including CVE-2022-26280 fix.
>
> Signed-off-by: Davide Gardenal
> ---
> Update v3:
> Instead of backporting the patch upgrade to
Hi Jose,
Am 4/11/2022 um 3:30 PM schrieb Jose Quaresma:
>
>
> J?rg Vehlow mailto:l...@jv-coder.de>> escreveu no dia
> segunda, 11/04/2022 à(s) 13:35:
>
> From: Joerg Vehlow mailto:joerg.veh...@aox.de>>
>
> When gos internal linker is used, it uses hardcoded paths to the
>
J?rg Vehlow escreveu no dia segunda, 11/04/2022 à(s)
13:35:
> From: Joerg Vehlow
>
> When gos internal linker is used, it uses hardcoded paths to the
> interpreter (dynamic linker). For x86_64 this hardcoded path is
> /lib64/ld-linux-x86-64.so.2, but yocto's default dynamic linker path
> is
This release contains security fixes
including CVE-2022-26280 fix.
Signed-off-by: Davide Gardenal
---
Update v3:
Instead of backporting the patch upgrade to the latest release with
the CVE fix. Thanks Quentin Schulz for the advise.
Update v2:
Change title from [meta-oe] to
Hi Quentin,
I just missed the release so I'm going to send a v3 patch now, thanks!
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#164223):
https://lists.openembedded.org/g/openembedded-core/message/164223
Mute This Topic:
Hi Davide,
Any reason for not updating to 3.6.1 since it includes this patch (from
the changelog info at least)?
Cheers,
Quentin
On 4/11/22 14:40, Davide Gardenal wrote:
Signed-off-by: Davide Gardenal
---
Update v2:
Change title from [meta-oe] to [oe-core]
---
Signed-off-by: Davide Gardenal
---
Update v2:
Change title from [meta-oe] to [oe-core]
---
.../libarchive/CVE-2022-26280.patch | 31 +++
.../libarchive/libarchive_3.6.0.bb| 4 ++-
2 files changed, 34 insertions(+), 1 deletion(-)
create mode 100644
Signed-off-by: Davide Gardenal
---
.../libarchive/CVE-2022-26280.patch | 31 +++
.../libarchive/libarchive_3.6.0.bb| 4 ++-
2 files changed, 34 insertions(+), 1 deletion(-)
create mode 100644
From: Joerg Vehlow
When gos internal linker is used, it uses hardcoded paths to the
interpreter (dynamic linker). For x86_64 this hardcoded path is
/lib64/ld-linux-x86-64.so.2, but yocto's default dynamic linker path
is /lib64/ld-linux-x86-64.so.2.
Most of the time, the internal linker is not
Signed-off-by: Alexander Kanavin
---
meta/recipes-support/itstool/itstool_2.0.7.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-support/itstool/itstool_2.0.7.bb
b/meta/recipes-support/itstool/itstool_2.0.7.bb
index 5af16995d7..336fb636d5 100644
---
Am 08.04.2022 um 22:03 schrieb Markus Volk via lists.openembedded.org:
also had this issue and found out, that the bluetooth service did come
up, once bluetooth was enabled
My fix was to edit like this
ReadWritePaths=:/var/lib/bluetooth
The colon ensures that the service won't fail if the
On Sun, Apr 10, 2022 at 10:46 PM Markus Volk wrote:
>
>
> Am 11.04.22 um 06:25 schrieb Andre McCurdy:
>
> On Sun, Apr 10, 2022 at 10:29 AM Markus Volk wrote:
>
> this fixes authentication issues with geary and tls connection
>
> Signed-off-by: Markus Volk
> ---
>
The build shows below error while building for arm machines.
Exception: TypeError: int() argument must be a string, a bytes-like object or a
number, not 'NoneType'
Detailed error info :
Steps to reproduce:
1. Set MACHINE ?= "qemuarm" in local.conf & add 'TOOLCHAIN_HOST_TASK:append = "
37 matches
Mail list logo
