Am Do, 23. Feb 2023 um 20:46:03 +0100 schrieb Alexander Kanavin
:
Why does gtk4 need to be removed as well in this case?
Because gtk4 is not allowed to build for nativesdk yet, only for
native. I've tested that it'll work, if 'nativesdk' is added to
BBCLASSEXTEND for gtk4, xkeyboard-config
This has already been done for oe-core/master.
Signed-off-by: Joe Slater
---
meta/recipes-support/nghttp2/nghttp2_1.47.0.bb | 4
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-support/nghttp2/nghttp2_1.47.0.bb
b/meta/recipes-support/nghttp2/nghttp2_1.47.0.bb
index
I'm sorry I didn't catch it earlier but this is also the cause of:
ERROR: core-image-sato-1.0-r0 do_rootfs: Multilib check error: duplicate files
Thanks for the patch it seems ok to me
At least it’s not poking at build machine for ld.so.conf anymore
On Thu, Feb 23, 2023 at 9:56 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> Currently binutils in buildtools is searching for /etc/etc/ld.so.conf
> which makes no sense.
Am Do, 23. Feb 2023 um 17:47:20 +0100 schrieb Alexandre Belloni
:
It failed on qemux86-64-x32:
Now that's unruly
I did a test build for qemux86-64-x32. For some reason gir gets
disabled while vala still is requested to be built and thus configure
fails. Not sure, why gir gets disabled here
These are new in binutils 2.40+
Signed-off-by: Khem Raj
---
...risc-v-Handle-R_RISCV_CALL_PLT-reloc.patch | 48 +++
meta/recipes-bsp/grub/grub2.inc | 1 +
2 files changed, 49 insertions(+)
create mode 100644
From: Fawzi KHABER
Remove superfluous DEV_PKG_DEPENDENCY = "" previously used to bypass
${PN}-dev package RDEPENDS on empty ${PN}. DEV_PKG_DEPENDENCY
applies RRECOMMENDS now, all workarounds are not needed anymore.
Related to [YOCTO #6839]
Signed-off-by: Yoann CONGAL
Signed-off-by: Fawzi
From: Fawzi KHABER
Add a package QA check for when a package RRECOMMENDS another that won't
be built because it is empty and ALLOW_EMPTY is not set. This happens
usually when ${PN}-dev RRECOMMENDS ${PN} but ${PN} is empty. This is not
an error but might be something to look into.
Example of a
I cant reproduce this. I've built core-image-sato multilib and rootfs
was created without an issue
Am Fr, 24. Feb 2023 um 00:28:30 +0100 schrieb Alexandre Belloni via
lists.openembedded.org
:
I'm sorry I didn't catch it earlier but this is also the cause of:
ERROR: core-image-sato-1.0-r0
Could this be the cause of this?
https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20230223-79c9rmcw/packages/diff-html/
On 22/02/2023 22:58:16-0800, Khem Raj wrote:
> Use DT_RUNPATH over DT_RPATH. If DT_RUNPATH is present, LD_LIBRARY_PATH is
> searched before
> DT_RUNPAT
- Allow to build the gtk4 widget and vapi
This is needed to build gtk4 based terminals like blackbox
- Update dependencies
- Cleanup recipe
Signed-off-by: Markus Volk
---
.../vte/{vte_0.70.2.bb => vte_0.70.3.bb} | 25 +++
1 file changed, 14 insertions(+), 11 deletions(-)
This was missed when riscv64nc was added
Signed-off-by: Khem Raj
---
meta/conf/machine/include/riscv/tune-riscv.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/machine/include/riscv/tune-riscv.inc
b/meta/conf/machine/include/riscv/tune-riscv.inc
index
On Thu, 23 Feb 2023 at 20:19, Markus Volk wrote:
> +${@bb.utils.contains('DISTRO_FEATURES', 'gobject-introspection-data',
> 'vala', '', d)} \
You need to use GI_DATA_ENABLED variable instead here. Then the
:remove statements with vala in them below will not be needed.
Yes, I messed this up
This series is a work in progress on 2 related bugs :
* [YOCTO #6839] Handle dev package with no main package more gracefully
* [YOCTO #8222] Elide dependency from -dev package on main package if
there are no shared libraries in it
An empty package ${PN} is not generated by default. This has
On Wed, 2023-02-22 at 22:34 -0800, Khem Raj wrote:
> On Wed, Feb 22, 2023 at 5:35 PM Khem Raj wrote:
> >
> > On Wed, Feb 22, 2023 at 3:43 PM Alexandre Belloni
> > wrote:
> > >
> > > Hello,
> > >
> > > This failed on musl:
> > >
> > > > checking minix/config.h usability...
> > > >
- Allow to build the gtk4 widget and vapi
This is needed to build gtk4 based terminals like blackbox
- Update dependencies
- Cleanup recipe
Signed-off-by: Markus Volk
---
.../vte/{vte_0.70.2.bb => vte_0.70.3.bb} | 24 +--
1 file changed, 11 insertions(+), 13 deletions(-)
On Thu, 23 Feb 2023 at 21:04, Markus Volk wrote:
>
> Am Do, 23. Feb 2023 um 20:46:03 +0100 schrieb Alexander Kanavin
> :
>
> Why does gtk4 need to be removed as well in this case?
>
>
> Because gtk4 is not allowed to build for nativesdk yet, only for native. I've
> tested that it'll work, if
for rust. This means that the tests are run per MACHINE
target instead of once overall.
The second issue I noticed is that the test results are not appearing
in the test report. For the build above, this is here:
https://autobuilder.yocto.io/pub/non-release/20230223-9/testresults/testresult-report.txt
an
On Thu, 2023-02-23 at 21:10 +0100, Alexander Kanavin wrote:
> On Thu, 23 Feb 2023 at 21:04, Markus Volk wrote:
> >
> > Am Do, 23. Feb 2023 um 20:46:03 +0100 schrieb Alexander Kanavin
> > :
> >
> > Why does gtk4 need to be removed as well in this case?
> >
> >
> > Because gtk4 is not allowed
sts are run per MACHINE
> target instead of once overall.
>
> The second issue I noticed is that the test results are not appearing
> in the test report. For the build above, this is here:
>
> https://autobuilder.yocto.io/pub/non-release/20230223-9/testresults/testresult-report.t
I agree. The problem I have with these variable names is that it's ambiguous
whether the features will be included or excluded from the backfill. All you
can tell from the names is that the values were 'considered'. What does that
mean? You have to go to the manual to find the full meaning.
Thanks Naveen,
With a large patch like this it would be good if you could provide a
cover letter that summarized what is different in v12, compared to v11.
I've looked at the diff and my summary is below. There are some changes
which I see but would benefit from an explanation.
Finally, please
The dtc project is dual licensed, and includes the text of both licenses as
part of its sources as well as a README documenting its license situation.
Use these sources to verify the licensing, and to monitor if it changes,
rather than a copyright line in a source file.
Signed-off-by: Trevor
Update the description to align with the current goals of the dtc project.
Signed-off-by: Trevor Woerner
---
meta/recipes-kernel/dtc/dtc_1.7.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/dtc/dtc_1.7.0.bb
b/meta/recipes-kernel/dtc/dtc_1.7.0.bb
Am Do, 23. Feb 2023 um 21:27:25 + schrieb Richard Purdie
:
Not necessarily. The question is whether we need gtk4 support in our
SDK? I've prefer not to build/include things we don't need and I'm not
sure where gtk4 is being used there as yet?
Also, I was wrong. Things are not that simple.
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
Signed-off-by: Wang Mingyu
---
meta/recipes-extended/bash/bash_5.2.15.bb | 3 +++
1 file changed, 3
From: Wang Mingyu
Error: Transaction test error:
file /usr/bin/padsp conflicts between attempted installs of
lib32-pulseaudio-misc-16.1-r0.armv7ahf_neon and pulseaudio-misc-16.1-r0.aarch64
Signed-off-by: Wang Mingyu
---
meta/recipes-multimedia/pulseaudio/pulseaudio_16.1.bb | 3 +++
1 file
From: Wang Mingyu
Error: Transaction test error:
file /usr/include/luaconf.h conflicts between attempted installs of
lua-dev-5.4.4-r0.aarch64 and lib32-lua-dev-5.4.4-r0.armv7ahf_neon
Signed-off-by: Wang Mingyu
---
meta/recipes-devtools/lua/lua_5.4.4.bb | 3 +++
1 file changed, 3
From: Wang Mingyu
Error: Transaction test error:
file /usr/bin/vala-gen-introspect-0.56 conflicts between attempted installs
of lib32-vala-0.56.3-r0.armv7ahf_neon and vala-0.56.3-r0.aarch64
file /usr/bin/vapigen-wrapper conflicts between attempted installs of
I have some concerns about this series of patches.
1. The QA check is not checking for RRECOMMENDS on non-existentent
packages, it's only checking for non-existent in-recipe packages. That
is, it's not checking packages from other recipes.
2. If patch 2 is sent, then the patch for 'a general
From: Chee Yang Lee
yocto-check-layer to check all .patch file in layer for
Upstream-status and list down all .patch file without Upstream-Status.
set this test as expected failure for now, so this wont fail the check
layer while still able to capture any patches with malformed or missing
On Fri, 24 Feb 2023 at 04:27, Chen Qi wrote:
> > This recipe is special. Libsoup has a hard dependency on nghttp2, so it
> > can't be moved to meta-oe. But nghttp2-client and nghttp2-server depend on
> > recipes of meta-oe.
>
> Hi Lei,
>
> Which ones? Do you have some local patch or some
> -Original Message-
> From: Richard Purdie
> Sent: Thursday, February 23, 2023 9:49 PM
> To: Bruce Ashfield ; Lee, Chee Yang
>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] checklayer: check for patch file upstream
> status
>
> On Thu, 2023-02-23 at
On Thu, Feb 23, 2023 at 3:34 PM Alexandre Belloni
wrote:
>
> Could this be the cause of this?
>
> https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20230223-79c9rmcw/packages/diff-html/
most likely yes. I will take a look. Lets work on merging the other
binutils and gdb u
On 2/24/23 09:45, leimao...@fujitsu.com wrote:
Hi
I'm sorry I missed this patch.
This does not seem correct. These two packages have FILES specified, and
ALLOW_EMPTY:${PN} is set to "1". I suspect the actually problem lies in
somewhere else.
This recipe is special. Libsoup has a hard
This is the final pull request for the upcoming 4.0.8 release.
The following changes since commit 54c30e509074073b99a7a8890482ba1af2abbab9:
oeqa context.py: fix --target-ip comment to include ssh port number
(2023-02-11 04:06:51 -1000)
are available in the Git repository at:
Hi
I'm sorry I missed this patch.
> This does not seem correct. These two packages have FILES specified, and
> ALLOW_EMPTY:${PN} is set to "1". I suspect the actually problem lies in
> somewhere else.
This recipe is special. Libsoup has a hard dependency on nghttp2, so it can't
be moved to
Hi, Alex
I'm sorry for late reply.
> If neither client nor server packages contain any files, then what is
> installed? Is
> there some other useful package than nghttp2 package pulls in, or does it
> itself
> contain something useful?
I found this conflicting requests error when I added
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
Signed-off-by: Wang Mingyu
---
meta/recipes-connectivity/dhcpcd/dhcpcd_9.4.1.bb | 3 +++
1
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
Signed-off-by: Wang Mingyu
---
Hi Alex,
> Lei, I'd suggest that you make a patch that simply deletes the entries for
> -client
> and -server, and removes a dependency on them from the main package. If
> someone later needs to enable them, it should be done by creating a correct,
> working build configuration, and then
The following changes since commit daaee6fcb0d201f041678af433d8e1cd6f924d09:
build-appliance-image: Update to dunfell head revision (2023-02-13 07:48:21
+)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
On Thu, 2023-02-23 at 08:33 -0500, Bruce Ashfield wrote:
> I don't recall the upstream-status being added as a yocto
> compatibility requirement. Can someone point me to a discussion that I
> missed ?
It isn't a requirement at this time and there isn't any recent
discussion you've missed.
The
On Thu, Feb 23, 2023 at 8:48 AM Richard Purdie
wrote:
>
> On Thu, 2023-02-23 at 08:33 -0500, Bruce Ashfield wrote:
> > I don't recall the upstream-status being added as a yocto
> > compatibility requirement. Can someone point me to a discussion that I
> > missed ?
>
> It isn't a requirement at
I don't recall the upstream-status being added as a yocto
compatibility requirement. Can someone point me to a discussion that I
missed ?
As everyone can recall, I wasn't on board with this being a default QA
check and error, and I'm also not on board with it being a yocto
compliance error.
I
Hi,
I have tried to upgrade the Mesa recipe to use 23.0.0
and tried to enable Rusticl by adding these:
inherit rust
PACKAGECONFIG[rusticl] = "-Dgallium-rusticl=true
-Drust_std=2021,-Dgallium-rusticl=false,libclc spirv-tools spirv-llvm-translator,libclc
spirv-tools spirv-llvm-translator"
I suspect there isn't. You need to write a recipe.
Alex
On Thu, 23 Feb 2023 at 14:56, Zoltan Boszormenyi wrote:
>
> Hi,
>
> I have tried to upgrade the Mesa recipe to use 23.0.0
> and tried to enable Rusticl by adding these:
>
> inherit rust
> PACKAGECONFIG[rusticl] = "-Dgallium-rusticl=true
>
The following changes since commit 62b894d75fb3361ed4d5473ae69188bce390980a:
oeqa context.py: fix --target-ip comment to include ssh port number
(2023-02-11 04:03:34 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/langdale-next
It failed on qemux86-64-x32:
https://autobuilder.yoctoproject.org/typhoon/#/builders/57/builds/6598/steps/11/logs/stdio
On 23/02/2023 08:52:56+0100, Markus Volk wrote:
> - Allow to build the gtk4 widget and vapi
> This is needed to build gtk4 based terminals like blackbox
> - Update
Greetings
Anybody else finding the DISTRO_FEATURES_BACKFILL_CONSIDERED and
MACHINE_FEATURES_BACKFILL_CONSIDERED variable names confusing?
According to the documentation about "feature backfilling"
(https://docs.yoctoproject.org/ref-manual/features.html#ref-features-backfill),
these
On Thu, Feb 23, 2023 at 10:59 AM Michael Opdenacker via
lists.yoctoproject.org
wrote:
>
> Greetings
>
> Anybody else finding the DISTRO_FEATURES_BACKFILL_CONSIDERED and
> MACHINE_FEATURES_BACKFILL_CONSIDERED variable names confusing?
I believe the history there is that those are "features" that
Greetings
I'm trying to document the possible values of INIT_MANAGER.
I'm using the master branch of Poky, and whether I'm using
INIT_MANAGER="none" or INIT_MANAGER="sysvinit" in conf/local.conf, I'm
getting the exact same "core-image-minimal" image (it's not even rebuilt).
Anyway,
On Thu, Feb 23, 2023 at 9:09 AM Michael Opdenacker via
lists.openembedded.org
wrote:
>
> Greetings
>
> I'm trying to document the possible values of INIT_MANAGER.
>
> I'm using the master branch of Poky, and whether I'm using
> INIT_MANAGER="none" or INIT_MANAGER="sysvinit" in conf/local.conf,
Currently binutils in buildtools is searching for /etc/etc/ld.so.conf
which makes no sense. ld_sysconfdir already contains /etc so we need to
drop the /etc from the fixed string.
Signed-off-by: Richard Purdie
---
...3-binutils-nativesdk-Search-for-alternative-ld.so.conf.patch | 2 +-
1 file
none is a confusing name though. Should it be dropped and nodistro
tweaked to use sysvinit?
Alex
On Thu, 23 Feb 2023 at 18:39, Khem Raj wrote:
>
> On Thu, Feb 23, 2023 at 9:09 AM Michael Opdenacker via
> lists.openembedded.org
> wrote:
> >
> > Greetings
> >
> > I'm trying to document the
55 matches
Mail list logo
