On Fri, Dec 27, 2024 at 11:44 AM Alexander Kanavin
wrote:
>
> On Fri, 27 Dec 2024 at 19:12, Joshua Watt wrote:
> > Ok, I tried it again, and it didn't work for me (or at least, didn't
> > do what I would have liked). You can set MACHINE and DISTRO in config
> > fragments, *but* it doesn't affect
On Fri, 27 Dec 2024 at 15:11, Rafael Beims via lists.openembedded.org
wrote:
> We found a problem related to key exchange that affects Bluez 5.72. This
> problem was already resolved on Bluez 5.79
> (https://github.com/bluez/bluez/commit/366a8c522b648f47147de4852c5c030d69b916b3),
> and now we're w
On Fri, 27 Dec 2024 at 07:54, Varatharajan, Deepesh via
lists.openembedded.org
wrote:
>
> From: Deepesh Varatharajan
>
> The `do_package` task fail with below error due to multiple `libstd.so` files
> installed in lib dir.
>
> -
On Fri, 27 Dec 2024 at 07:54, Varatharajan, Deepesh via
lists.openembedded.org
wrote:
> https://blog.rust-lang.org/2024/09/05/Rust-1.81.0.html
>
> Dropped:
> 0001-cargo-do-not-write-host-information-into-compilation.patch
> hardcodepaths.patch
You need to explain why the patches have been dropped
On Fri, 27 Dec 2024 at 19:12, Joshua Watt wrote:
> Ok, I tried it again, and it didn't work for me (or at least, didn't
> do what I would have liked). You can set MACHINE and DISTRO in config
> fragments, *but* it doesn't affect the machine or distro include in
> bitbake.conf. This means you can't
From: Alexander Kanavin
There was a report that the existing addfragments statement comes in too late,
specifically after the DISTRO/MACHINE includes have already been handled. The
goal
for fragments content is to behave exactly like the settings in local.conf would
and so we need to handle the
On Thu, Dec 26, 2024 at 10:54 PM Varatharajan, Deepesh via
lists.openembedded.org wrote:
> From: Deepesh Varatharajan
>
> The data layout for x86 and ppc targets were different in rust from llvm.
>
>
> -
> er
Ok, I tried it again, and it didn't work for me (or at least, didn't
do what I would have liked). You can set MACHINE and DISTRO in config
fragments, *but* it doesn't affect the machine or distro include in
bitbake.conf. This means you can't really specify MACHINE or DISTRO in
a fragment, or you're
Hello,
We found a problem related to key exchange that affects Bluez 5.72. This
problem was already resolved on Bluez 5.79
(https://github.com/bluez/bluez/commit/366a8c522b648f47147de4852c5c030d69b916b3),
and now we're wondering whether it would be acceptable to update the
Bluez recipe to the
Got it, thanks for the reply
//Hongxu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#209103):
https://lists.openembedded.org/g/openembedded-core/message/209103
Mute This Topic: https://lists.openembedded.org/mt/110290207/21656
Group Owner: openemb
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/scarthgap-1-1-libxml2-Upgrade-2.12.8---2.12.9.patch
FAIL: test Signed-off-by presence: Mbox is missing Signed-off-b
From: Divya Chellam
Changes between 2.12.8 -> 2.12.9
https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.12.9
Security
* [CVE-2024-40896] Fix XXE protection in downstream code
Improvements
* Undeprecate xmlKeepBlanksDefault.
---
.../libxml/{libxml2_2.12.8.bb =
On Thu Dec 26, 2024 at 6:43 AM CET, hongxu via lists.openembedded.org wrote:
> Set license alias other than spdxId to hasConcludedLicense relationship
>
> $ echo 'MACHINE = "qemux86-64"' >> conf/local.conf
> $ bitbake shadow
> $ In tmp/deploy/spdx/3.0.1/corei7-64/recipes/recipe-shadow.spdx.json
> B
13 matches
Mail list logo
