From: Romuald JEANNE
As vname var is needed in multiubi_mkfs() function, we need to keep it
defined and use it as parameter to the new write_ubi_config() function.
See [YOCTO #15027]
Signed-off-by: Romuald JEANNE
---
meta/classes-recipe/image_types.bbclass | 13 +++--
1 file changed,
2023. 03. 09. 3:32 keltezéssel, Anuj Mittal írta:
On Wed, 2023-03-08 at 18:23 +0100, Zoltan Boszormenyi wrote:
Added cc for the interested parties.
2023. 03. 08. 18:19 keltezéssel, Zoltan Boszormenyi via
lists.openembedded.org írta:
Hi,
I observed the following inconsistencies:
1. opencl-icd
On Wed, 2023-03-08 at 18:23 +0100, Zoltan Boszormenyi wrote:
> Added cc for the interested parties.
>
> 2023. 03. 08. 18:19 keltezéssel, Zoltan Boszormenyi via
> lists.openembedded.org írta:
> > Hi,
> >
> > I observed the following inconsistencies:
> >
> > 1. opencl-icd-loader and ocd-icd both p
All the 3 ' gcc g++ binutil ' are required to run rust on target.
>
> Without binutils getting error 'cannot find ld ' and
>
without g++ getting below error:
>
> root@qemux86-64:~# rustc -o hello main.rs
> error: linking with `x86_64-poky-linux-gcc` failed: exit status: 1
> |
> = note: "x86_6
> I think we should just change the MACHINE, OS, CC and MACHTYPE lines to
> something like "".
So for the correction of this problem, do we need to continue to vote for
patch?
Or accept this patch temporarily, and then roll it back after the bash update?
--
Best Regards
---
RHEL compatible kernels do not support vgem so we disable virgl headless
testing.
Signed-off-by: Michael Halstead
---
meta/lib/oeqa/selftest/cases/runtime_test.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/selftest/cases/runtime_test.py
b/meta/lib/oeqa/s
cups includes a web server. Users can surf to port 631 (default) of a
machine running cups to (potentially, based on configuration, default off)
view jobs, add printers, and perform other forms of administration.
The location of the various resources that are used by the built-in web server
(e.g.
The cups' PACKAGECONFIG is populated based on DISTRO_FEATURES, but a user
is free to enable or disable PACKAGECONFIGs at will. In theory it is
possible that pam is enabled globally in DISTRO_FEATURES but disabled in
cups' PACKAGECONFIG. Checking the PACKAGECONFIG to determine whether or not
pam is
The cups documentation is clear that the correct way to install into an
alternate root directory is to use the BUILDROOT variable. From INSTALL.md:
Use the `BUILDROOT` variable to install to an alternate root directory:
make BUILDROOT=/some/other/root/directory install
DESTDI
As per the release notes for 0.55.0[1], this patch is no longer needed
as Meson now only removes the RPATHs that it adds itself, any RPATHs
added via LDFLAGS or pkgconfig files are left untouched.
[1]
https://mesonbuild.com/Release-notes-for-0-55-0.html#rpath-removal-now-more-careful
Signed-off-
The relevant fix was also backported to 252.4.
Signed-off-by: Ross Burton
---
meta/recipes-core/systemd/systemd_252.5.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-core/systemd/systemd_252.5.bb
b/meta/recipes-core/systemd/systemd_252.5.bb
index 8b92b2cf425..784a2482075
On Wed, 8 Mar 2023 at 22:15, Richard Purdie
wrote:
>
> On Wed, 2023-03-08 at 21:22 +0100, Clément Péron wrote:
> > Hi Richard,
> >
> > On Wed, 8 Mar 2023 at 18:31, Richard Purdie
> > wrote:
> > >
> > > On Wed, 2023-03-08 at 18:14 +0100, Clément Péron wrote:
> > > > Split out the QEMU guest agent
On Wed, 2023-03-08 at 21:22 +0100, Clément Péron wrote:
> Hi Richard,
>
> On Wed, 8 Mar 2023 at 18:31, Richard Purdie
> wrote:
> >
> > On Wed, 2023-03-08 at 18:14 +0100, Clément Péron wrote:
> > > Split out the QEMU guest agent into a separate package. The agent is
> > > intended to be installed
Hi Richard,
On Wed, 8 Mar 2023 at 18:31, Richard Purdie
wrote:
>
> On Wed, 2023-03-08 at 18:14 +0100, Clément Péron wrote:
> > Split out the QEMU guest agent into a separate package. The agent is
> > intended to be installed within a QEMU VM guest where a user is likely
> > to not want to have th
Hi Michael,
On Wed, 8 Mar 2023 at 18:55, Michael Tokarev wrote:
>
> 08.03.2023 20:28, Clément Péron пишет:
> ...
> >> meta/recipes-devtools/qemu/qemu.inc | 35 +++-
> >> .../qemu/qemu/qemu-guest-agent.init | 84 +++
> >> .../qemu/qemu/qemu-guest-agent.u
On Wed, 8 Mar 2023 at 06:28, Böszörményi Zoltán wrote:
> I think that was already brewing with 22.3.x, since that version
> cut off the "classic" drivers, keeping only the gallium ones.
> Like the kernel, Mesa's drivers were implicitly expected to work
> with everything built from the same main ve
Also, enable that, if opengl is in native DISTRO_FEATURES: this allows
mesa-native to build drivers that rely on libllbm, particularly llvmpipe,
which is a (sort of) accelerated software renderer that is the only
option on build hosts without dedicated or supported GPUs.
Signed-off-by: Alexander K
This prevents accidental builds of it when native/nativesdk opengl
is not actually enabled (which may cause undesirable lengthening
of dependency chains or build failures because those dependencies
don't enable options required for mesa).
Signed-off-by: Alexander Kanavin
---
meta/recipes-graphic
Without this, the only available driver would be swrast
(without llvmpipe) which is far too slow to be practical,
and so qemu wouldn't be able to perform accelerated graphics.
Note that mesa-native itself is guarded by presence of 'opengl'
in DISTRO_FEATURES_NATIVE, so building it is entirely opt-
This makes native opengl (and thus accelerated graphics in qemu) opt-in;
the reason is that latest mesa tightly couples hardware drivers with its
libraries,
so we have to build both in mesa-native. Doing so significantly lengthens
the builds, and so cannot be imposed by default.
Add a check and a
With mesa 23.0, it is not longer possible to use the host drivers, as
mesa upstream has added strict checks for matching builds between
drivers and libraries that load them.
Signed-off-by: Alexander Kanavin
---
scripts/runqemu | 25 +
1 file changed, 1 insertion(+), 24 de
On Wed, 8 Mar 2023 at 18:30, Sundeep KOKKONDA
wrote:
> rust files are not linking on target due to missing dependencies and observed
> below error.
> error: linker `x86_64-poky-linux-gcc` not found
>
> Added the required dependencies to run rust on target machine.
> +RDEPENDS:${PN}:append:class-t
On Wed, Mar 8, 2023 at 5:30 PM Sundeep KOKKONDA
wrote:
>
> [YOCTO #14975]
> rust files are not linking on target due to missing dependencies and observed
> below error.
> error: linker `x86_64-poky-linux-gcc` not found
>
> Added the required dependencies to run rust on target machine.
>
> Signed-
On Wed, 2023-03-08 at 18:14 +0100, Clément Péron wrote:
> Split out the QEMU guest agent into a separate package. The agent is
> intended to be installed within a QEMU VM guest where a user is likely
> to not want to have the rest of the QEMU installation within it.
>
> Additionally, an initscript
[YOCTO #14975]
rust files are not linking on target due to missing dependencies and observed
below error.
error: linker `x86_64-poky-linux-gcc` not found
Added the required dependencies to run rust on target machine.
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-devtools/rust/rust_1.67.1.bb
Hi Michael,
On Wed, 8 Mar 2023 at 18:14, Clément Péron via lists.openembedded.org
wrote:
>
> Split out the QEMU guest agent into a separate package. The agent is
> intended to be installed within a QEMU VM guest where a user is likely
> to not want to have the rest of the QEMU installation within
Added cc for the interested parties.
2023. 03. 08. 18:19 keltezéssel, Zoltan Boszormenyi via lists.openembedded.org
írta:
Hi,
I observed the following inconsistencies:
1. opencl-icd-loader and ocd-icd both provide libOpenCL.so.1
2. opencl-icd-loader has PROVIDES="virtual/opencl-icd", ocl-icd
Hi,
I observed the following inconsistencies:
1. opencl-icd-loader and ocd-icd both provide libOpenCL.so.1
2. opencl-icd-loader has PROVIDES="virtual/opencl-icd", ocl-icd hasn't
3. oe-core's piglit recipe explicitly depends on opencl-icd-loader (should be
virtual/opencl-icd)
4. meta-intel r
Add support to the runqemu script for a new option, 'guestagent', that
enables the virtio serial port for host-to-guest communication.
Signed-off-by: Brenda Streiff
Signed-off-by: Clément Péron
---
scripts/runqemu | 14 ++
1 file changed, 14 insertions(+)
diff --git a/scripts/runqe
Split out the QEMU guest agent into a separate package. The agent is
intended to be installed within a QEMU VM guest where a user is likely
to not want to have the rest of the QEMU installation within it.
Additionally, an initscript, udev rules file, and systemd unit file are
added to the package
Split out the QEMU guest agent into a separate package. The agent is
intended to be installed within a QEMU VM guest where a user is likely
to not want to have the rest of the QEMU installation within it.
Additionally, an initscript, udev rules file, and systemd unit file are
added to the package
Add support to the runqemu script for a new option, 'guestagent', that
enables the virtio serial port for host-to-guest communication.
Signed-off-by: Brenda Streiff
Signed-off-by: Clément Péron
---
scripts/runqemu | 14 ++
1 file changed, 14 insertions(+)
diff --git a/scripts/runqe
glibc has it's dependencies handled more manually due to it's place
in the toolchain bootstrap. It depends upon the compiler and indirectly
through that to binutils. This did mean that if binutils changes and the
compiler does not, sstate and hash equivalence could mean that glibc
wouldn't rebuild.
Awesome, thanks! I think any recipe which is using
INHIBIT_DEFAULT_DEPENDENCIES could
run into these sorts of errors.
On Wed, Mar 8, 2023 at 3:53 AM Richard Purdie
wrote:
>
> On Wed, 2023-03-08 at 09:33 +, Richard Purdie via
> lists.openembedded.org wrote:
> > On Wed, 2023-02-22 at 22:58 -08
Changelog:
Fix potential DoS vector in MHD_PostProcessor.(CVE-2023-27371)
Releasing GNU libmicrohttpd 0.9.76 hotfix.
https://github.com/Karlson2k/libmicrohttpd/blob/v0.9.76/ChangeLog
Signed-off-by: Narpat Mali
---
.../{libmicrohttpd_0.9.75.bb => libmicrohttpd_0.9.76.bb}| 2
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-4.1.3.rc1.
We are planning to execute following tests for this cycle:
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. NUC 7
3. ADL
4. T
Hi All,
QA for yocto-4.0.8.rc2 is completed. This is the full report for this release:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new issue found.
Thanks,
Jing Hui
> -O
On 2 Mar 2023, at 21:47, Sudip Mukherjee via lists.openembedded.org
wrote:
>
> The LICENSE did not have complete information.
> Some examples of missing license:
>
> Zlib: deps/zlib/
> ISC: tests/clar/clar.c
> LGPL-2.1-or-later: src/libgit2/xdiff/xdiffi.c
> CC0-1.0: src/util/rand.c
>
> Signed-
On 6 Mar 2023, at 15:10, Anna-Lena Marx via lists.openembedded.org
wrote:
>
> Hi,
> moving the support or the tests to meta-filesystems does not make sense to me.
> Wic is located in oe-core, move support and tests would not really work at
> all and create another dependency.
> It may be an opt
> On 8 Mar 2023, at 12:32, Böszörményi Zoltán wrote:
> The code in pytorch does "import ninja" conditionally,
> so it expects it as a python module. Also, this specific
> package and anything that uses pytorch for its build
> (like torchvision) complains about the same.
That would be:
https:/
2023. 03. 08. 12:43 keltezéssel, Ross Burton írta:
On 7 Mar 2023, at 15:13, Zoltan Boszormenyi via lists.openembedded.org
wrote:
Hi,
Recently, I had to create recipes for a few python modules,
among which a few used cmake to build their C or C++ pieces.
I saw from their build log that they co
On Wed, 2023-03-08 at 09:33 +, Richard Purdie via
lists.openembedded.org wrote:
> On Wed, 2023-02-22 at 22:58 -0800, Khem Raj wrote:
> > Use DT_RUNPATH over DT_RPATH. If DT_RUNPATH is present, LD_LIBRARY_PATH is
> > searched before
> > DT_RUNPATH, Search order is DT_RPATH then LD_LIBRARY_PATH
glibc has it's dependencies handled more manually due to it's place
in the toolchain bootstrap. It depends upon the compiler and indirectly
through that to binutils. This did mean that if binutils changes and the
compiler does not, sstate and hash equivalence could mean that glibc
wouldn't rebuild.
On 7 Mar 2023, at 15:13, Zoltan Boszormenyi via lists.openembedded.org
wrote:
>
> Hi,
>
> Recently, I had to create recipes for a few python modules,
> among which a few used cmake to build their C or C++ pieces.
> I saw from their build log that they complained about
> the missing (optional) "
On 08.03.2023 12:18, Richard Purdie wrote:
Yes, this is still reproducible in a clean build, with a fresh poky
clone. Same steps as before:
git clone https://github.com/yoctoproject/poky.git; cd poky/; .
oe-init-build-env
add to local.conf:
require conf/multilib.conf
MACHINE = "qemuarm64"
MU
- test_skip_kernel_install: This test verifies that the kernel is not
installed in the boot partition when the 'install-kernel-into-boot-dir'
parameter is set to false.
- test_kernel_install: This test verifies that the kernel is installed
in the boot partition when the 'install-kernel-into-boot-di
The issue with installing the kernel image to both rootfs
and boot partition is that some systems rely on the kernel image in
rootfs and not in the boot partition.
This leads to duplication of the kernel image, which can cause
unnecessary storage usage.
This patch provides a solution to the problem
On Wed, 2023-03-08 at 08:52 +0200, Ovidiu Panait wrote:
> On 3/7/23 22:45, 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 Tue, 2023-03-
The previous fix wasn't enough to address all the possible ways the
manifests might be ordered. Rework the previous fix so it is tied
to the multilib cross-canadian code which is causing the problem.
RECIPE_SYSROOT_MANIFEST_SUBDIR is not documented as I'd hope nobody
ever needs to use this outside
On Wed, 2023-02-22 at 22:58 -0800, Khem Raj wrote:
> Use DT_RUNPATH over DT_RPATH. If DT_RUNPATH is present, LD_LIBRARY_PATH is
> searched before
> DT_RUNPATH, Search order is DT_RPATH then LD_LIBRARY_PATH then
> DT_RUNPATH, this order ensures that injecting
> malicious shared objects is way harde
Hi Alexander,
On Mon, 6 Mar 2023 at 07:30, Alexander Kanavin wrote:
>
> Can you please explain the use case? Who would want to enable the
> option, and what could they do when there's a running qemu?
Guest agent communication is useful to retrieve some information about
a running VM.
In my cas
On Wed, 2023-03-08 at 09:40 +0800, wangmy wrote:
> From: Wang Mingyu
>
> Error: Transaction test error:
> file /usr/bin/bashbug conflicts between attempted installs of
> lib32-bash-bashbug-5.2.15-r0.armv7ahf_neon and bash-bashbug-5.2.15-r0.aarch64
>
> The differences between the two files are
On Wed, 2023-03-08 at 09:40 +0800, wangmy wrote:
> From: Wang Mingyu
>
> Error: Transaction test error:
> file /usr/share/pkgconfig/xcb-proto.pc conflicts between attempted installs
> of lib32-xcb-proto-dev-1.15.2-r0.armv7ahf_neon and
> xcb-proto-dev-1.15.2-r0.cortexa57
>
> The differences b
On Wed, 2023-03-08 at 09:40 +0800, wangmy wrote:
> From: Wang Mingyu
>
> Error: Transaction test error:
>file /usr/share/man/man8/dhcpcd.8 conflicts between attempted installs of
> dhcpcd-doc-9.4.1-r0.cortexa57 and lib32-dhcpcd-doc-9.4.1-r0.armv7ahf_neon
>
> The differences between the two
But what is the use case for installing two sets of documentation? Is
it really something that needs to be fixed, or can you simply install
just one of the two packages?
Alex
On Wed, 8 Mar 2023 at 02:40, wangmy wrote:
>
> From: Wang Mingyu
>
> Error: Transaction test error:
>file /usr/share
55 matches
Mail list logo
