Date   

Re: [meta-mingw] [PATCH] grpc: remove nl2 requirement since it is optional

Joshua Watt
 



On Sat, Aug 21, 2021, 6:26 AM Richard Purdie <richard.purdie@...> wrote:
On Fri, 2021-08-20 at 20:46 +0000, Sinan Kaya wrote:
> Signed-off-by: Sinan Kaya <okaya@...>
> ---
>  .../openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend  | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend b/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend
> index a72496d..dc0ea42 100644
> --- a/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend
> +++ b/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend
> @@ -1,2 +1,5 @@
> +# doesn't build and not required
> +DEPENDS:remove:mingw32 = "libnsl2"
> +
>  EXTRA_OECMAKE:remove:mingw32 = "-DBUILD_SHARED_LIBS=ON"
>  EXTRA_OECMAKE:append:mingw32 = " -DBUILD_SHARED_LIBS=OFF"

Should we be making that a PACKAGECONFIG which mingw32 could change?

Yes, that's a good idea. Sinan, please make that change in meta-oe, then change this patch to remove it from PACKAGECONFIG


Cheers,

Richard


Re: [meta-mingw] [PATCH] grpc: remove nl2 requirement since it is optional

Richard Purdie
 

On Fri, 2021-08-20 at 20:46 +0000, Sinan Kaya wrote:
Signed-off-by: Sinan Kaya <okaya@...>
---
.../openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend | 3 +++
1 file changed, 3 insertions(+)

diff --git a/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend b/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend
index a72496d..dc0ea42 100644
--- a/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend
+++ b/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend
@@ -1,2 +1,5 @@
+# doesn't build and not required
+DEPENDS:remove:mingw32 = "libnsl2"
+
EXTRA_OECMAKE:remove:mingw32 = "-DBUILD_SHARED_LIBS=ON"
EXTRA_OECMAKE:append:mingw32 = " -DBUILD_SHARED_LIBS=OFF"
Should we be making that a PACKAGECONFIG which mingw32 could change?

Cheers,

Richard


[meta-mingw] [PATCH] grpc: remove nl2 requirement since it is optional

Sinan Kaya <okaya@...>
 

Signed-off-by: Sinan Kaya <okaya@...>
---
.../openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend | 3 +++
1 file changed, 3 insertions(+)

diff --git a/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend b/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend
index a72496d..dc0ea42 100644
--- a/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend
+++ b/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend
@@ -1,2 +1,5 @@
+# doesn't build and not required
+DEPENDS:remove:mingw32 = "libnsl2"
+
EXTRA_OECMAKE:remove:mingw32 = "-DBUILD_SHARED_LIBS=ON"
EXTRA_OECMAKE:append:mingw32 = " -DBUILD_SHARED_LIBS=OFF"
--
2.17.1


[meta-mingw] [PATCH 2/2] c-ares: disable shared build as it is broken

Sinan Kaya <okaya@...>
 

Signed-off-by: Sinan Kaya <okaya@...>
---
.../recipes-support/c-ares/c-ares_%.bbappend | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 dynamic-layers/openembedded-layers/recipes-support/c-ares/c-ares_%.bbappend

diff --git a/dynamic-layers/openembedded-layers/recipes-support/c-ares/c-ares_%.bbappend b/dynamic-layers/openembedded-layers/recipes-support/c-ares/c-ares_%.bbappend
new file mode 100644
index 0000000..8ef58f9
--- /dev/null
+++ b/dynamic-layers/openembedded-layers/recipes-support/c-ares/c-ares_%.bbappend
@@ -0,0 +1,2 @@
+EXTRA_OECMAKE:append:mingw32 = "-DCARES_SHARED=OFF"
+EXTRA_OECMAKE:append:mingw32 = "-DCARES_STATIC=ON"
--
2.17.1


[meta-mingw] [PATCH 1/2] re2: disable shared build as it is broken

Sinan Kaya <okaya@...>
 

Signed-off-by: Sinan Kaya <okaya@...>
---
.../openembedded-layers/recipes-support/re2/re2_%.bbappend | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 dynamic-layers/openembedded-layers/recipes-support/re2/re2_%.bbappend

diff --git a/dynamic-layers/openembedded-layers/recipes-support/re2/re2_%.bbappend b/dynamic-layers/openembedded-layers/recipes-support/re2/re2_%.bbappend
new file mode 100644
index 0000000..16bb5a0
--- /dev/null
+++ b/dynamic-layers/openembedded-layers/recipes-support/re2/re2_%.bbappend
@@ -0,0 +1,2 @@
+EXTRA_OECMAKE:remove:mingw32 = "-DBUILD_SHARED_LIBS=ON"
+EXTRA_OECMAKE:append:mingw32 = "-DBUILD_SHARED_LIBS=OFF"
--
2.17.1


Re: Install packages to an "image" without its dependencies being pulled in. #yocto

Chuck Wolber
 

Yes.

This is a version of the question - "how do I build an image that *ONLY* includes the packages I explicitly specify". This involves bypassing a lot of guards and bitbake tooling, but it can be done.

Your mileage may vary depending on your distro setup. In particular this assumes you are configured to use the IPK package format. The dnf command had significant issues a while back, so I switched from RPM to IPK. If you use RPM, the OPKG_ARGS stuff not going to work for you.

IMAGE_FEATURES = ""
LDCONFIGDEPEND = ""
IMAGE_INSTALL = ""
PACAKGE_INSTALL = ""
OPKG_ARGS += "--no-install-recommends --nodeps --force-depends"

ROOTFS_POSTPROCESS_COMMAND_remove = "systemd_create_users; "
ROOTFS_POSTPROCESS_COMMAND_remove = "rootfs_update_timestamp; "
ROOTFS_POSTPROCESS_COMMAND_remove = "rootfs_reproducible; "

IMAGE_CMD_cpio_prepend() {
    IMAGE_BUILDING_DEBUGFS="true"
}

If you want the pre and postinstall scripts to trigger, you need to add an IMAGE_PREPROCESS_COMMAND function that takes your PACKAGE_INSTALL list and concatenates the package level control, preinst, and postinst scripts. This involves unpacking the ipk found in ${WORKDIR}/oe-rootfs-repo/*/${PKG}_*.ipk. You may also want to post-process the resulting script to remove "set -e" invocations, since those scripts make assumptions about dependencies that you are (hopefully) safe to ignore.

You may also want another IMAGE_PREPROCESS_COMMAND function that deletes stuff that can accidentally overwrite your image rootfs files, like /etc/passwd and /etc/group.

Once you get it all dialed in, you can probably abstract the useful bits to your own image-layer bbclass so you can trivially reuse it.

..Ch:W..


On Fri, Aug 20, 2021 at 12:36 AM <bibibobibo@...> wrote:
Greetings everyone, 

Is there a way to instruct Yocto's image class to install package(s) without its dependencies for an image target (i.e ext4)? For instance, we are trying to build a system where there is a main system partition and another partition that'll host additional lib, etc and during boot up we would overlay them together. Hence, the "other" partition does not really need all the same system libs, etc that already exists on the system partition. This other partition is developed by an external partner so we want to have the autonomy to update separately (i.e not mingled things together with system partition). I am having trouble finding a way to do this because Yocto seem to like to install a package long with all its dependencies (i.e glibc, etc).

PS. I apologize if this is not the right place to ask the question.

Thanks,
Mike




--
"Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire


Re: Wayland and X11 on Yocto

Manuel Wagesreither
 

Am Do, 19. Aug 2021, um 00:22, schrieb Khem Raj:
On Wed, Aug 18, 2021 at 3:06 PM Manuel Wagesreither <ManWag@...> wrote:

Hello all,

I'm building an image to run on various SBCs and would like to equip it with a graphical interface.

There are quite a few things very unclear to me. Can someone help me with that?

* Why is X11 enabled by setting an IMAGE_FEATURE (namely x11, x11-base or x11-sato), while Wayland is enabled by IMAGE_INSTALL only (weston-init and weston)?
x11-* features is primarily to control what kind of x11 packages you
want to include in image e.g.
./meta/recipes-sato/packagegroups/packagegroup-core-x11-sato.bb is
pulled in when x11-sato is added to IMAGE_FEATURES
we have many X11 based images and sato is one of them so thats why its
separated out.

you should really is looking at DISTRO_FEATURES e.g. wayland distro
feature is needed for core-image-weston to build.

* Theory: Is IMAGE_FEATURE +=x11 manipulating IMAGE_INSTALL under the hood so you don't have to do it manually? And as there is no IMAGE_FEATURE "wayland", you have do it manually. Correct?
* Why is Wayland different in that it doesn't need an IMAGE_FEATURE to enable it?
there are not many wayland based compositors or images we have in core
as of now.

* Why does core-image-weston.bb need to enable IMAGE_FEATURE hwcodec, while core-image-x11.bb does not? (Dunfell branch.)
openGL is needed for wayland/weston to work too but hwcodec feature is
infact to pull in machine specific drivers MACHINE_HWCODECS into image
if a given BSP defined it.
e.g. intel bsps define vaapi codecs and mediasdk for specific machines
via MACHINE_HWCODECS
defaults for this image features are empty
Hi Khem, thanks! will need to look into this and digest what you said.

Thanks, regards, Manuel


Re: Pyinstaller recipe #yocto

Konrad Weihmann <kweihmann@...>
 

On 20.08.21 13:57, yasminebenghozzi6@... wrote:
Hello,
So I've been trying to build a pyinstaller recipe, which is this one , but I got those errors.


Pyinstaller recipe #yocto

yasminebenghozzi6@...
 

Hello,

So I've been trying to build a pyinstaller recipe, which is this one , but I got those errors.


Failed dbus on Hardknott oFono 1.31

JH
 

Hi,

I upgraded from Zeus to Hardknotte, I was able to run dbus to get
interface properties, but I failed on Hardknotte ofono 1.31. Has
anyone got oFono 1.31 dbus work?

Thank you.

Kind regards,

- jupiter


Install packages to an "image" without its dependencies being pulled in. #yocto

bibibobibo@...
 

Greetings everyone, 

Is there a way to instruct Yocto's image class to install package(s) without its dependencies for an image target (i.e ext4)? For instance, we are trying to build a system where there is a main system partition and another partition that'll host additional lib, etc and during boot up we would overlay them together. Hence, the "other" partition does not really need all the same system libs, etc that already exists on the system partition. This other partition is developed by an external partner so we want to have the autonomy to update separately (i.e not mingled things together with system partition). I am having trouble finding a way to do this because Yocto seem to like to install a package long with all its dependencies (i.e glibc, etc).

PS. I apologize if this is not the right place to ask the question.

Thanks,
Mike


[meta-gplv2] [PATCH 1/2] layer.conf: Set elfutils version correctly

Richard Purdie
 

We need to set PREFERRED_VERSION for elfutils or the wrong one will be used.

Signed-off-by: Richard Purdie <richard.purdie@...>
---
conf/layer.conf | 1 +
1 file changed, 1 insertion(+)

diff --git a/conf/layer.conf b/conf/layer.conf
index 3abe6b5..b0915d4 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -18,5 +18,6 @@ LAYERSERIES_COMPAT_gplv2 = "honister"

LICENSE_PATH += "${LAYERDIR}/licenses"

+PREFERRED_VERSION_elfutils = "${@['', '0.148']['GPLV3' in (d.getVar('INCOMPATIBLE_LICENSE') or '').upper()]}"
PREFERRED_VERSION_shared-mime-info = "${@['', '1.10']['GPLV3' in (d.getVar('INCOMPATIBLE_LICENSE') or '').upper()]}"
PREFERRED_VERSION_shared-mime-info-native = "${@['', '1.10']['GPLV3' in (d.getVar('INCOMPATIBLE_LICENSE') or '').upper()]}"
--
2.32.0


[meta-gplv2] [PATCH 2/2] elfutils: Work around reproducibility issue

Richard Purdie
 

The version in this layer doesn't reproduce, so disable the warnings/errors
and allow it to build.

Signed-off-by: Richard Purdie <richard.purdie@...>
---
recipes-devtools/elfutils/elfutils_0.148.bb | 3 +++
1 file changed, 3 insertions(+)

diff --git a/recipes-devtools/elfutils/elfutils_0.148.bb b/recipes-devtools/elfutils/elfutils_0.148.bb
index 848e2cf..97d88a2 100644
--- a/recipes-devtools/elfutils/elfutils_0.148.bb
+++ b/recipes-devtools/elfutils/elfutils_0.148.bb
@@ -66,6 +66,9 @@ CFLAGS += "-Wno-error=format-truncation="
# but 0.182 has different license, so to be safe don't backport the fix, just ignore the issue
CFLAGS += "-Wno-error=stringop-overflow="

+# There are fixes in later versions for this but the old version won't be reproducible
+TARGET_CC_ARCH:remove:class-target = " -Wdate-time"
+
EXTRA_OECONF = "--program-prefix=eu- --without-lzma"
EXTRA_OECONF:append:class-native = " --without-bzlib"

--
2.32.0


Yocto Autobuilder: Latency Monitor and AB-INT - Meeting notes: Aug 19, 2021

Randy MacLeod
 

YP AB Intermittent failures meeting
===================================
Aug 19, 2021, 9 AM ET
https://windriver.zoom.us/j/3696693975

Attendees: Tony, Richard, Trevor, Randy, Alex, Saul


Summary:
========

ptest results continue to improve but there's still room
for even more improvement.

The make/ninja load average limit is in but it's not clear
if it's effective yet and it breaks dunfell. Trevor investigating.

There's not much new this week, I've commented on a few existing
activities below and added "Aug 19" in most cases.


If anyone wants to help, we could use more eyes on the logs,
particularly the summary logs and understanding iostat #
when the dd test times out.



Plans for the week:
===================

Richard: lttng-tools and more!
Alex: SWAT plans. September email, training.
Sakib: hook more responsive load average in to latency test. (v3)
Trevor: patch to set PARALLEL_MAKE : -l 50
-> dunfell, gatesgarth, hardknott (Aug 5 - it's a priority)
Investigate dunfell which failed with this change.
- data on WR AB load average.
Tony: go back to school. Thanks for all your work Tony!
Saul:
Randy: Gather more iostat data, graph it!

Meeting Notes:
==============

1. job server

- ninja could be patched with make's more responsive algorithm
next or is this good enough?

- Richard suggested that we extract make's code for measuring the load
average to a separate binary and run it in the periodic io latency
test. Also can we translate it to python?
- Trevor is working on this and had some problems so next week.
(Aug 19 - Trevor is back from vaction so maybe next week.)

- Trevor to see if the load average change really did reduce load
on WR build systems. (Aug 19)

2. AB status

Trevor is learning about buildbot and working on a scheduling bug
(CentOS worker?)

bitbake layer setup tool should allow multiple backends:
eg: kas, a y-a-helper.

ptest cases are improving, we may be close to done!
Let's wait a week to see how things go.
(July29, Aug 5, Aug 19, we're not done...)

- lttng-tools ptest is failing. RP is working on it with upstream.
The timeout (done on Aug 5) increase hasn't helped.


3. Sakib's improvements to the logging are merged.

Sakib generated a summary of all high latency 'top' logs from
~July 23->July 29 by just running his summary script on the
merged raw top logs.

More analysis required....


Still relevant parts of
Previous Meeting Notes:
=======================


4. bitbake server timeout ( no change july 29, Aug 19)

"Timeout while waiting for a reply from the bitbake server (60s)"

5. io stalls (no update: July 29)

Richard said that it would make sense to write an ftrace utility
/ script to monitor io latency and we could install it with sudo
Ch^W mentioned ftrace on IRC.
Sakib and Randy will work on that but not for a week or two
or longer! (Aug 19).

Randy collected iostat data on 3 build server:
https://postimg.cc/gallery/8cN6LYB
We agreed that having -ty-2 be ~ 100 utilization for many hours
in a row is not acceptable and that a threshold of ~ 10 minutes
at 100% utilization may be a reasonable limt. I need to figure out
if I can get data on the fraction of IO done per IO clas since
we do use ionice to do clean-up and other activities.


../Randy


Minutes: Yocto Project Weekly Triage Meeting 8/19/2021

Trevor Gamblin
 

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage

Attendees: Alex, Armin, Bruce, Diane, Joshua, Randy, Richard, Ross, Saul, Stephen, Steve, Tim, Tony, TrevorG

ARs:

N/A

Notes:

- (carried over) Steve encountered build failures such as the one in https://errors.yoctoproject.org/Errors/Details/593109/ when attempting to run dunfell builds with the PARALLEL_MAKE load averaging added. WR is testing/investigating on internal Autobuilder instance - Trevor is still planning on looking into this!

Medium+ 3.4 Unassigned Enhancements/Bugs: 76 (Last week 80)

Medium+ 3.99 Unassigned Enhancements/Bugs: 36 (Last week 30)

AB-INT Bugs: 46 (No change)


Problem with building Go recipe for "Delve" project

Christofer Dutz <christofer.dutz@...>
 

Hi all,

 

after having sorted out all of my programatic-configuration issues I’m currently having an issue where I don’t quite know what I’m doing wrong.

 

We use a too called „Delve“ to debug applications on yocto remotely. This is an application built in Go.

https://github.com/go-delve/delve

 

However as soon as I try to build the layer I built for it, it fails.

 

The reason is that the repo contains one directory that only has test-classes and not a single „build“-class.

 

As the Go tooling seems to execute:

go list -f "{{.ImportPath}}" ./...

 

This also lists up that package and as soon as the yocto go tooling tries to build it, the build fails with:

 

| go build github.com/go-delve/delve/service/test: no non-test Go files in /home/cdutz/Projects/yocto/dunfell/build/tmp/work/aarch64-fslc-linux/delve/1.7.1-r0/build/src/github.com/go-delve/delve/service/test

 

A simple workaround is to simply create an empty go file with only a package in that directory, however this sort of feels like a workaround.

 

Is this possibly a bug in the Yocto Go tooling or am I doing someting stupid?

 

Chris

 


Re: [meta-rockchip][PATCH 2/2] linux-yocto_5.4: Drop bbappend

Trevor Woerner
 

On Wed, Aug 18, 2021 at 2:16 PM Khem Raj <raj.khem@...> wrote:
5.4 recipe has been dropped from oe-core

Signed-off-by: Khem Raj <raj.khem@...>
---
 ...-Keep-rk3288-tinker-SD-card-IO-power.patch | 31 -------------------
 recipes-kernel/linux/linux-yocto_5.4.bbappend |  5 ---
 2 files changed, 36 deletions(-)
 delete mode 100644 recipes-kernel/linux/linux-yocto/0001-ARM-dts-rockchip-Keep-rk3288-tinker-SD-card-IO-power.patch
 delete mode 100644 recipes-kernel/linux/linux-yocto_5.4.bbappend

added to meta-rockchip master
thanks! 


Re: [meta-rockchip][PATCH 1/2] machines: Adjust for new location of tune files in core

Trevor Woerner
 

On Wed, Aug 18, 2021 at 2:16 PM Khem Raj <raj.khem@...> wrote:
Signed-off-by: Khem Raj <raj.khem@...>
---
 conf/machine/include/rk3066.inc | 2 +-
 conf/machine/include/rk3188.inc | 2 +-
 conf/machine/include/rk3288.inc | 2 +-
 conf/machine/include/rk3328.inc | 2 +-
 conf/machine/include/rk3399.inc | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

added to meta-rockchip master
thanks! 


YOCTO Zeus: Qt remote objects compiler repc missing from sdk toolchain #toolchain #sdk #qtremoteobjects #repc

anthony.marchand@...
 

Hello,

I permit myself to contact you because I got a weird issue in my sdk toolchain.

So, as I need "qtremoteobjects" in my embedded linux image, I add it like this:

----------------------------------------------------
QT = " \
qtbase \
qtbase-dev \
qtbase-plugins \
qtbase-mkspecs \
qtbase-tools \
cinematicexperience \
qtgraphicaleffects \
qtquickcontrols \
qtquickcontrols2 \
qtquickcontrols-qmlplugins \
qtsvg \
qtserialport \
qtserialbus \
qtremoteobjects \
qtremoteobjects-dev \
qtmultimedia \
qtwebsockets \
"
PACKAGECONFIG_pn-qtvirtualkeyboard = "lang-fr_FR"
PACKAGECONFIG_DEFAULT_pn-qtbase = "widgets libs freetype tslib gles2 eglfs"
 
TOUCHSCREEN = " \
tslib tslib-conf tslib-tests tslib-calibrate \
"
 
IMAGE_INSTALL += " \
bash \
sudo \
environment \
opkg \
os-release \
${QT} \
"
 
#IMAGE_INSTALL_append_mx6 = " ${MX6TOOL}"
 
IMAGE_FEATURES += " \
ssh-server-openssh \
"
 
export IMAGE_BASENAME = "myimage"

----------------------------------------------------
So it's work fine when I flash it in my card, but after building SDK, "repc" is missing in /sysroots/cortexa9t2hf-neon-poky-linux-gnueabi/usr/bin .  More precisly, it is present, but located in:

/sysroots/cortexa9t2hf-neon-poky-linux-gnueabi/usr/bin/.debug/repc

And when I compile my app, I got the following error:
 
Pre build error --> make[2]: /opt/poky/MY_SDK/sysroots/x86_64-pokysdk-linux/usr/bin/repc: Command not found

because "make" seems to try to find repc in "/usr/bin/repc" rather than "/usr/bin/.debug/repc" . But when I link or move repc from "/usr/bin/.debug/repc" to  "/usr/bin/repc", it gives me a "segment fault error" when I try to make my app.
Does anyone already encontered this problem with qtremote control? Do you have got any idea about what is going wrong?
 
By advance, thanks for all, best reguards.  


Does PACKAGE_EXCLUDE work for Hardknott?

JH
 

Hi,

I set up PACKAGE_EXCLUDE = "python3 python3-dbus", but it still build
pyhon3 and python3-dbus, what could I be wrong here?

Thank you.

Kind regards,

- jh

3301 - 3320 of 57792