On 09-01-2025 19:11, Richard Purdie wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Thu, 2025-01-09 at 01:25 -0800, Varatharajan, Deepesh via
lists.openembedded.org wro
From: Changqing Li
By default, create-log-dirs is enabled in systemd, and a link
/var/log/README will be created, point to {{DOC_DIR}}/README.logs, but,
for oe, there are two problems here, firstly, DOC_DIR is packaged in
another package systemd-doc, so /var/log/README is a dead link when
system
I know this patch is applied but I still want to bring it to attention
Many packages in other layers depend on fmt. fmt's APIs are not or
not used in a very backward compatible way
some packages provide an option to use vendored version of fmt so in
case of system fmt being not compatible is not
a
Every other architecture has the QEMU_EXTRAOPTIONS assignments in the
tune files, so move the PPC ones too.
Leave the MACHINE_ARCH workarounds present for now as these are masking
a genuine bug (#15647) that needs to be resolved properly.
Signed-off-by: Ross Burton
---
meta/classes-recipe/qemu.
Yes. I was tired and used ‘fixup’ instead of squash’ which would’ve opened
the editor. The incorrect message can be dropped.
Alex
On Thu 9. Jan 2025 at 18.21, Ross Burton wrote:
> On 8 Jan 2025, at 08:42, Alexander Kanavin via lists.openembedded.org
> wrote:
>
> Your commit message says:
>
> >
On 8 Jan 2025, at 08:42, Alexander Kanavin via lists.openembedded.org
wrote:
Your commit message says:
> Do not install cmake files; if someone wants them, please make
> them reproducible and not hardcode-installed into /usr/lib.
But then:
> +Subject: [PATCH] src/libgit2/CMakeLists.txt: insta
On 8 Jan 2025, at 08:42, Alexander Kanavin via lists.openembedded.org
wrote:
>
> Drop pidfd.patch (upstream significantly refactored the code; the patch can
> be tested
> only with very old kernels; upstream submission has not been followed up
> since initial
> MR creation).
Not quite: the re
Hi
On Mon, Dec 30, 2024 at 08:33:17AM +, Jing Hui Tham via
lists.openembedded.org wrote:
> QA for yocto-5.2_M1.rc2 is completed. This is the full report for
> yocto-5.2_M1.rc2:
> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
How are t
On Thu, 2025-01-09 at 01:25 -0800, Varatharajan, Deepesh via
lists.openembedded.org wrote:
> From: Deepesh Varatharajan
>
> https://blog.rust-lang.org/2024/09/05/Rust-1.81.0.html
>
> Drop the following backported patches which is addressed
> with rust v1.81.0 upgrade.
>
> 0001-cargo-do-not-writ
- To avoid false positives such as CVE-2000-0006, add the CVE_PRODUCT
value with the vendor.
- The CVE-2000-0006 has the vendor paul_kranenburg:strace.
- This change has been verified by running do_cve_check task for
strace package.
Signed-off-by: Madhu Marri
---
meta/recipes-devtools/strace/str
On 09-01-2025 15:09, Alexander Kanavin wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
The patchset looks good, thank you. Will you continue with updating
towards 1.82 and
On 09-01-2025 15:04, Deepesh Varatharajan wrote:
On 28-12-2024 00:26, Alexander Kanavin wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Fri, 27 Dec 2024 at 07:54, Va
The patchset looks good, thank you. Will you continue with updating
towards 1.82 and 1.83?
Alex
On Thu, 9 Jan 2025 at 10:31, Varatharajan, Deepesh via
lists.openembedded.org
wrote:
>
> Tested for rust_1.81 update:
>
> bitbake rust
> bitbake cargo
> bitbake nativesdk-rust
> bitbake core-image-mi
On 28-12-2024 00:23, Alexander Kanavin wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Fri, 27 Dec 2024 at 07:54, Varatharajan, Deepesh via
lists.openembedded.org
wrot
On 28-12-2024 00:26, Alexander Kanavin wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Fri, 27 Dec 2024 at 07:54, Varatharajan, Deepesh via
lists.openembedded.org
wrot
Tested for rust_1.81 update:
bitbake rust
bitbake cargo
bitbake nativesdk-rust
bitbake core-image-minimal
bitbake core-image-sato -c do_populate_sdk
bitbake core-image-sato -c testsdk
bitbake world
oe-selftest -r rust
oe-sefltest -r reproducible
oe-selftest results for all archs as below:
Target
From: Deepesh Varatharajan
https://blog.rust-lang.org/2024/09/05/Rust-1.81.0.html
Drop the following backported patches which is addressed
with rust v1.81.0 upgrade.
0001-cargo-do-not-write-host-information-into-compilation.patch
https://github.com/rust-lang/cargo/commit/2db0bab16139d094f689587
From: Deepesh Varatharajan
The data layout for x86 and ppc targets were different in rust from llvm.
-
error: data-layout for target `x86-linux`,
`e-m:e-p:32:32-f64:32:64-f80:32-n8:16:32-S128`,
differs from
From: Deepesh Varatharajan
During the Rust build process, multiple copies of libstd-*.so are generated, as
Rust copies the
required files from the stage2 build artifacts to the target image directory.
When these build
binaries are copied to the image, Yocto's do_package step encounters an error
LTS branches cannot receive major version updates like that. Rather
the patch that updates the git submodule locations needs to be
backported.
Alex
On Thu, 9 Jan 2025 at 03:44, Song, Jiaying (CN) via
lists.openembedded.org
wrote:
>
> From: Jiaying Song
>
> Due to the invalid URL of gitsm, the d
20 matches
Mail list logo
