Date   

Re: Building Yocto on M1 Mac

Anders Montonen
 


On 13 Feb 2022, at 21:59, Josef Holzmayr <jester@...> wrote:

Howdy!

On 13. Feb 2022, at 19:04, Alexander Kanavin <alex.kanavin@...> wrote:

Even if you do manage to start a build, performance won't be great.
Yocto, by design, builds the entire stack from source, so a lot of CPU
cores is essential. Don't spend your time waiting, get an
appropriately specced Linux workstation, or an account on a Linux
server that your organization might have for the purpose.

While that is perfectly true from the pure technical facts, I have to add that building in Parallels on a M1 is ok-ish. You have to crank up the VM way beyond the defaults, to something like 6-8core, 16+X GB RAM, but then it’s bearable for the occasional user. When you can’t get your hands on a proper environment, its certainly an option.

Just to give some numbers, building a Dunfell core-image-minimal for the Beaglebone, with a pre-populated DL_DIR took 36 minutes in a Linux VM on a M1 Max Macbook Pro (8 cores, 16GB RAM allocated), and 21 minutes on my 5900X desktop (12/24 cores/threads, 64GB RAM).

-a


[meta-security][PATCH 2/2] parsec-service: fix compile issue.

Armin Kuster
 

| thread 'main' panicked at 'Failed to find tss2-sys library.: Command { command: "\"pkg-config\" \"--libs\" \"--cflags\" \"tss2-sys\" \"tss2-sys >= 2.3.3\"", cause: Os { code: 2, kind: NotFound, message: "No such file or directory" } }', /home/akuster/oss/clean/poky/build/tmp-glibc/work/cortexa57-oe-linux/parsec-service/0.8.1-r0/cargo_home/bitbake/tss-esapi-sys-0.2.0/build.rs:62:10

add inherit pkgconfig

Signed-off-by: Armin Kuster <akuster808@...>
---
.../recipes-parsec/parsec-service/parsec-service_0.8.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-parsec/recipes-parsec/parsec-service/parsec-service_0.8.1.bb b/meta-parsec/recipes-parsec/parsec-service/parsec-service_0.8.1.bb
index 9161872..1cbf2bd 100644
--- a/meta-parsec/recipes-parsec/parsec-service/parsec-service_0.8.1.bb
+++ b/meta-parsec/recipes-parsec/parsec-service/parsec-service_0.8.1.bb
@@ -23,7 +23,7 @@ PACKAGECONFIG[TS] = "trusted-service-provider,,libts,libts"
PARSEC_FEATURES = "${@d.getVar('PACKAGECONFIG_CONFARGS',True).strip().replace(' ', ',')}"
CARGO_BUILD_FLAGS += " --features ${PARSEC_FEATURES}"

-inherit systemd
+inherit pkgconfig systemd
SYSTEMD_SERVICE:${PN} = "parsec.service"

inherit update-rc.d
--
2.25.1


[meta-security][PATCH 1/2] tpm2-tss: update to 3.1.0

Armin Kuster
 

Drop 001-configure.ac-fix-compatibility-with-autoconf-2.70.patch which is included in update.

Signed-off-by: Armin Kuster <akuster808@...>
---
...fix-compatibility-with-autoconf-2.70.patch | 48 -------------------
.../tpm2-tss/tpm2-tss/fixup_hosttools.patch | 26 ++++++++++
.../{tpm2-tss_3.0.3.bb => tpm2-tss_3.1.0.bb} | 16 +++++--
3 files changed, 38 insertions(+), 52 deletions(-)
delete mode 100644 meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss/0001-configure.ac-fix-compatibility-with-autoconf-2.70.patch
create mode 100644 meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss/fixup_hosttools.patch
rename meta-tpm/recipes-tpm2/tpm2-tss/{tpm2-tss_3.0.3.bb => tpm2-tss_3.1.0.bb} (88%)

diff --git a/meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss/0001-configure.ac-fix-compatibility-with-autoconf-2.70.patch b/meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss/0001-configure.ac-fix-compatibility-with-autoconf-2.70.patch
deleted file mode 100644
index cae2e76..0000000
--- a/meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss/0001-configure.ac-fix-compatibility-with-autoconf-2.70.patch
+++ /dev/null
@@ -1,48 +0,0 @@
-From 03cca78d24d716eec792f86f5b0bc69886fad981 Mon Sep 17 00:00:00 2001
-From: Patrick McCarty <patrick.mccarty@...>
-Date: Fri, 18 Dec 2020 01:54:05 +0000
-Subject: [PATCH] configure.ac: fix compatibility with autoconf 2.70
-
-With autoconf 2.70, not quoting the second argument to one of the AS_IF
-macro expansions leads to generation of invalid shell code affecting the
-first nested ERROR_IF_NO_PROG expansion.
-
-The invalid shell code leads to an error resembling:
-
- ./configure: line 18826: syntax error near unexpected token `newline'
- ./configure: line 18826: ` '''
-
-Fix the issue by quoting the second argument to the affected AS_IF,
-similar to the quoting found elsewhere in configure.ac.
-
-Signed-off-by: Patrick McCarty <patrick.mccarty@...>
-
-Upstream-Status: Backport
-Signed-off-by: Armin Kuster <akuster808@...>
-
----
- configure.ac | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-Index: tpm2-tss-3.0.3/configure.ac
-===================================================================
---- tpm2-tss-3.0.3.orig/configure.ac
-+++ tpm2-tss-3.0.3/configure.ac
-@@ -279,7 +279,7 @@ AC_ARG_ENABLE([integration],
- [build and execute integration tests])],,
- [enable_integration=no])
- AS_IF([test "x$enable_integration" = "xyes"],
-- AS_IF([test "$HOSTOS" = "Linux"],
-+ [AS_IF([test "$HOSTOS" = "Linux"],
- [ERROR_IF_NO_PROG([ss])],
- [ERROR_IF_NO_PROG([sockstat])])
- ERROR_IF_NO_PROG([echo])
-@@ -328,7 +328,7 @@ AS_IF([test "x$enable_integration" = "xy
- [AC_MSG_ERROR([No simulator executable found in PATH for testing TCTI.])])
- AC_SUBST([INTEGRATION_TCTI], [$integration_tcti])
- AC_SUBST([INTEGRATION_ARGS], [$integration_args])
-- AC_SUBST([ENABLE_INTEGRATION], [$enable_integration]))
-+ AC_SUBST([ENABLE_INTEGRATION], [$enable_integration])])
- AM_CONDITIONAL([ENABLE_INTEGRATION],[test "x$enable_integration" = "xyes"])
- #
- # sanitizer compiler flags
diff --git a/meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss/fixup_hosttools.patch b/meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss/fixup_hosttools.patch
new file mode 100644
index 0000000..b5579e1
--- /dev/null
+++ b/meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss/fixup_hosttools.patch
@@ -0,0 +1,26 @@
+revert configure: add checks for all tools used by make install
+
+Not appropriate for cross build env.
+
+Upstream-Status: OE [inappropriate]
+Signed-off-by: Armin Kuster <akuster808@...>
+
+Index: tpm2-tss-3.1.0/configure.ac
+===================================================================
+--- tpm2-tss-3.1.0.orig/configure.ac
++++ tpm2-tss-3.1.0/configure.ac
+@@ -471,14 +471,6 @@ AM_CONDITIONAL(SYSD_SYSUSERS, test "x$sy
+ AC_CHECK_PROG(systemd_tmpfiles, systemd-tmpfiles, yes)
+ AM_CONDITIONAL(SYSD_TMPFILES, test "x$systemd_tmpfiles" = "xyes")
+ # Check all tools used by make install
+-AS_IF([test "$HOSTOS" = "Linux"],
+- [ERROR_IF_NO_PROG([groupadd])
+- ERROR_IF_NO_PROG([useradd])
+- ERROR_IF_NO_PROG([id])
+- ERROR_IF_NO_PROG([chown])
+- ERROR_IF_NO_PROG([chmod])
+- ERROR_IF_NO_PROG([mkdir])
+- ERROR_IF_NO_PROG([setfacl])])
+
+ AC_SUBST([PATH])
+
diff --git a/meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss_3.0.3.bb b/meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss_3.1.0.bb
similarity index 88%
rename from meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss_3.0.3.bb
rename to meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss_3.1.0.bb
index 1a36a5b..e0f2d09 100644
--- a/meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss_3.0.3.bb
+++ b/meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss_3.1.0.bb
@@ -7,9 +7,10 @@ SECTION = "tpm"
DEPENDS = "autoconf-archive-native libgcrypt openssl"

SRC_URI = "https://github.com/tpm2-software/${BPN}/releases/download/${PV}/${BPN}-${PV}.tar.gz \
- file://0001-configure.ac-fix-compatibility-with-autoconf-2.70.patch \
- "
-SRC_URI[sha256sum] = "78392be7309baf47f51b122f566ac915fd4d1760ea78571cba2e1484f9b5be17"
+ file://fixup_hosttools.patch \
+ "
+
+SRC_URI[sha256sum] = "8900a6603f74310b749b65f23c3461cde6e2a23a5f61058b21004c25f9cf19e8"

inherit autotools pkgconfig systemd extrausers

@@ -18,14 +19,19 @@ PACKAGECONFIG[oxygen] = ",--disable-doxygen-doc, "
PACKAGECONFIG[fapi] = "--enable-fapi,--disable-fapi,curl json-c "

EXTRA_OECONF += "--enable-static --with-udevrulesdir=${nonarch_base_libdir}/udev/rules.d/"
+EXTRA_OECONF += "--runstatedir=/run"
EXTRA_OECONF:remove = " --disable-static"

-
EXTRA_USERS_PARAMS = "\
useradd -p '' tss; \
groupadd tss; \
"

+do_install:append() {
+ # Remove /run as it is created on startup
+ rm -rf ${D}/run
+}
+
PROVIDES = "${PACKAGES}"
PACKAGES = " \
${PN} \
@@ -75,6 +81,8 @@ FILES:libtss2-staticdev = "${libdir}/libtss*a"

FILES:${PN} = "\
${libdir}/udev \
+ /var/lib/tpm2-tss \
+ /var/run \
${nonarch_base_libdir}/udev \
${sysconfdir}/tmpfiles.d \
${sysconfdir}/tpm2-tss \
--
2.25.1


Re: Building Yocto on M1 Mac

Josef Holzmayr
 

Howdy!

On 13. Feb 2022, at 19:04, Alexander Kanavin <alex.kanavin@...> wrote:

Even if you do manage to start a build, performance won't be great.
Yocto, by design, builds the entire stack from source, so a lot of CPU
cores is essential. Don't spend your time waiting, get an
appropriately specced Linux workstation, or an account on a Linux
server that your organization might have for the purpose.

While that is perfectly true from the pure technical facts, I have to add that building in Parallels on a M1 is ok-ish. You have to crank up the VM way beyond the defaults, to something like 6-8core, 16+X GB RAM, but then it’s bearable for the occasional user. When you can’t get your hands on a proper environment, its certainly an option.

Greetz


Alex

On Sun, 13 Feb 2022 at 15:56, Abhijeet Tripathi
<abhijeettripathi3003@...> wrote:


On Sun, Feb 13, 2022 at 7:09 PM Anders Montonen <Anders.Montonen@...> wrote:

Hi,

On 13 Feb 2022, at 14:24, Abhijeet Tripathi <abhijeettripathi3003@...> wrote:

Hello yocto-devs,

I'm new to the yocto project and trying to set up a build environment on my M1 Mac which is arm64 architecture.

I'm following the steps as mentioned in below link:
https://github.com/crops/docker-win-mac-docs/wiki/Mac-Instructions

But it is always pulling up containers based on amd64 architecture. Are there any updated steps/link to set up a build environment specific to M1 Mac(arm64)?


Looking at Docker Hub, none of the published Crops containers are built for ARM64. You can try building the containers yourself, making sure to pick base distros that are available for ARM64.

Note that there are plenty of reports of Docker performing poorly on Macs, probably because of the file system implementation. You may be better off using a full VM via e.g. UTM.


I initially started with UTM but the problem with virtual machines is that we can only use half the resources of the machine.
This makes the builds slower, so I was looking at the container way.

Can you point me to any documentation which I can use to build customized containers for yocto builds?

Thanks,
Abhijeet



-a









Re: Building Yocto on M1 Mac

Alexander Kanavin
 

Even if you do manage to start a build, performance won't be great.
Yocto, by design, builds the entire stack from source, so a lot of CPU
cores is essential. Don't spend your time waiting, get an
appropriately specced Linux workstation, or an account on a Linux
server that your organization might have for the purpose.

Alex

On Sun, 13 Feb 2022 at 15:56, Abhijeet Tripathi
<abhijeettripathi3003@...> wrote:


On Sun, Feb 13, 2022 at 7:09 PM Anders Montonen <Anders.Montonen@...> wrote:

Hi,

On 13 Feb 2022, at 14:24, Abhijeet Tripathi <abhijeettripathi3003@...> wrote:

Hello yocto-devs,

I'm new to the yocto project and trying to set up a build environment on my M1 Mac which is arm64 architecture.

I'm following the steps as mentioned in below link:
https://github.com/crops/docker-win-mac-docs/wiki/Mac-Instructions

But it is always pulling up containers based on amd64 architecture. Are there any updated steps/link to set up a build environment specific to M1 Mac(arm64)?


Looking at Docker Hub, none of the published Crops containers are built for ARM64. You can try building the containers yourself, making sure to pick base distros that are available for ARM64.

Note that there are plenty of reports of Docker performing poorly on Macs, probably because of the file system implementation. You may be better off using a full VM via e.g. UTM.

I initially started with UTM but the problem with virtual machines is that we can only use half the resources of the machine.
This makes the builds slower, so I was looking at the container way.

Can you point me to any documentation which I can use to build customized containers for yocto builds?

Thanks,
Abhijeet



-a




Re: Possible to ignore a missing file in recipe without error?

Howard
 

Thanks Josef, that sounds like what I want to do isn't really possible   Or if it is, it isn't worth the effort.


Re: Building Yocto on M1 Mac

Abhijeet Tripathi
 


On Sun, Feb 13, 2022 at 7:09 PM Anders Montonen <Anders.Montonen@...> wrote:
Hi,

On 13 Feb 2022, at 14:24, Abhijeet Tripathi <abhijeettripathi3003@...> wrote:

Hello yocto-devs,

I'm new to the yocto project and trying to set up a build environment on my M1 Mac which is arm64 architecture. 

I'm following the steps as mentioned in below link:

But it is always pulling up containers based on amd64 architecture. Are there any updated steps/link to set up a build environment specific to M1 Mac(arm64)?

Looking at Docker Hub, none of the published Crops containers are built for ARM64. You can try building the containers yourself, making sure to pick base distros that are available for ARM64.

Note that there are plenty of reports of Docker performing poorly on Macs, probably because of the file system implementation. You may be better off using a full VM via e.g. UTM.
 
I initially started with UTM but the problem with virtual machines is that we can only use half the resources of the machine.
This makes the builds slower, so I was looking at the container way.

Can you point me to any documentation which I can use to build customized containers for yocto builds?

Thanks,
Abhijeet
 

-a




Re: [meta-mingw] [PATCH 1/2] mingw-w64: Upgrade runtime/headers/winpthreads to 9.0.0

Richard Purdie
 

On Sat, 2022-02-12 at 10:42 -0800, Khem Raj wrote:
Drop upstreamed fixes for rdtsc [1] __udivmoddi4[2]

[1] https://sourceforge.net/p/mingw-w64/mingw-w64/ci/6a0e9165008f731bccadfc41a59719cf7c8efc02/
[2] https://sourceforge.net/p/mingw-w64/mingw-w64/ci/ab0fa5ad3c67d634fd7754d9473d1bb7051f9bf0/

Signed-off-by: Khem Raj <raj.khem@...>
---
...rincs-Check-for-__builtin_ia32_rdtsc.patch | 33 ------------
.../0001-winpthreads-Add-__udivmoddi4.patch | 52 -------------------
recipes-devtools/mingw-w64/mingw-w64.inc | 4 +-
...b => nativesdk-mingw-w64-headers_9.0.0.bb} | 0
...b => nativesdk-mingw-w64-runtime_9.0.0.bb} | 2 -
... nativesdk-mingw-w64-winpthreads_9.0.0.bb} | 2 -
6 files changed, 1 insertion(+), 92 deletions(-)
delete mode 100644 recipes-devtools/mingw-w64/files/0001-intrincs-Check-for-__builtin_ia32_rdtsc.patch
delete mode 100644 recipes-devtools/mingw-w64/files/0001-winpthreads-Add-__udivmoddi4.patch
rename recipes-devtools/mingw-w64/{nativesdk-mingw-w64-headers_8.0.0.bb => nativesdk-mingw-w64-headers_9.0.0.bb} (100%)
rename recipes-devtools/mingw-w64/{nativesdk-mingw-w64-runtime_8.0.0.bb => nativesdk-mingw-w64-runtime_9.0.0.bb} (88%)
rename recipes-devtools/mingw-w64/{nativesdk-mingw-w64-winpthreads_8.0.0.bb => nativesdk-mingw-w64-winpthreads_9.0.0.bb} (87%)

diff --git a/recipes-devtools/mingw-w64/files/0001-intrincs-Check-for-__builtin_ia32_rdtsc.patch b/recipes-devtools/mingw-w64/files/0001-intrincs-Check-for-__builtin_ia32_rdtsc.patch
deleted file mode 100644
index ce4ba81..0000000
--- a/recipes-devtools/mingw-w64/files/0001-intrincs-Check-for-__builtin_ia32_rdtsc.patch
+++ /dev/null
@@ -1,33 +0,0 @@
-From 346de7591f58015d111f4d4f3b001382c04d5557 Mon Sep 17 00:00:00 2001
-From: Khem Raj <raj.khem@...>
-Date: Tue, 13 Apr 2021 18:44:25 -0700
-Subject: [PATCH] intrincs: Check for __builtin_ia32_rdtsc
-
-on modern gcc ( >=4.6 ) __rdtsc function is implemented using
-special builtin function called __builtin_ia32_rdtsc, its actually
-a define in gcc, so __has_builtin check fails for __rdtsc even
-though it is defined to imply __builtin_ia32_rdtsc(), therefore
-check for existence of __builtin_ia32_rdtsc as well
-
-Upstream-Status: Pending
-Signed-off-by: Khem Raj <raj.khem@...>
----
- mingw-w64-crt/intrincs/rdtsc.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/mingw-w64-crt/intrincs/rdtsc.c b/mingw-w64-crt/intrincs/rdtsc.c
-index bf9c03b..df04711 100644
---- a/mingw-w64-crt/intrincs/rdtsc.c
-+++ b/mingw-w64-crt/intrincs/rdtsc.c
-@@ -11,7 +11,7 @@
- #define __has_builtin(x) 0
- #endif
-
--#if !__has_builtin(__rdtsc)
-+#if !__has_builtin(__rdtsc) && !__has_builtin(__builtin_ia32_rdtsc)
- unsigned __int64 __rdtsc(void)
- {
- #ifdef _WIN64
---
-2.31.1
-
diff --git a/recipes-devtools/mingw-w64/files/0001-winpthreads-Add-__udivmoddi4.patch b/recipes-devtools/mingw-w64/files/0001-winpthreads-Add-__udivmoddi4.patch
deleted file mode 100644
index 3eb298e..0000000
--- a/recipes-devtools/mingw-w64/files/0001-winpthreads-Add-__udivmoddi4.patch
+++ /dev/null
@@ -1,52 +0,0 @@
-From 3b0af7327446ae179dc93b6a6ab1074251d348d0 Mon Sep 17 00:00:00 2001
-From: Khem Raj <raj.khem@...>
-Date: Fri, 30 Apr 2021 16:50:36 -0700
-Subject: [PATCH] winpthreads: Add __udivmoddi4
-
-Newer GCC ( 11.1.0+ ) is generating calls to __udivmoddi4 on i686
-architecture, therefore provide an implementation to avoid undefined
-references
-
-Upstream-Status: Pending
-Signed-off-by: Khem Raj <raj.khem@...>
----
- .../winpthreads/src/libgcc/dll_math.c | 16 +++++++++++++++-
- 1 file changed, 15 insertions(+), 1 deletion(-)
-
-diff --git a/mingw-w64-libraries/winpthreads/src/libgcc/dll_math.c b/mingw-w64-libraries/winpthreads/src/libgcc/dll_math.c
-index aeec068..d170967 100644
---- a/mingw-w64-libraries/winpthreads/src/libgcc/dll_math.c
-+++ b/mingw-w64-libraries/winpthreads/src/libgcc/dll_math.c
-@@ -121,6 +121,7 @@ u_quad_t __udivdi3(u_quad_t a, u_quad_t b);
- u_quad_t __umoddi3(u_quad_t a, u_quad_t b);
- int __ucmpdi2(u_quad_t a, u_quad_t b);
- quad_t __divmoddi4(quad_t a, quad_t b, quad_t *rem);
-+u_quad_t __udivmoddi4(u_quad_t a, u_quad_t b, u_quad_t *rem);
-
- #endif /* !_LIBKERN_QUAD_H_ */
-
-@@ -573,7 +574,20 @@ __divmoddi4(a, b, rem)
- return (negq ? -uq : uq);
- }
-
-+/*
-+ * Divide two unsigned quads.
-+ * This function is new in GCC 7.
-+ */
-+u_quad_t
-+__udivmoddi4(a, b, rem)
-+ u_quad_t a, b, *rem;
-+{
-+ u_quad_t q = __udivdi3(a, b);
-+ if (rem)
-+ *rem = a - b * q;
-+ return q;
-+}
-+
- #else
- static int __attribute__((unused)) dummy;
- #endif /*deined (_X86_) && !defined (__x86_64__)*/
--
---
-2.31.1
-
diff --git a/recipes-devtools/mingw-w64/mingw-w64.inc b/recipes-devtools/mingw-w64/mingw-w64.inc
index d40d4a5..322fb79 100644
--- a/recipes-devtools/mingw-w64/mingw-w64.inc
+++ b/recipes-devtools/mingw-w64/mingw-w64.inc
@@ -5,9 +5,7 @@ COMPATIBLE_HOST = ".*-mingw.*"

SRC_URI = "${SOURCEFORGE_MIRROR}/project/mingw-w64/mingw-w64/mingw-w64-release/mingw-w64-v${PV}.tar.bz2"

-SRC_URI[sha256sum] = "44c740ea6ab3924bc3aa169bad11ad3c5766c5c8459e3126d44eabb8735a5762"
+SRC_URI[sha256sum] = "1929b94b402f5ff4d7d37a9fe88daa9cc55515a6134805c104d1794ae22a4181"

UPSTREAM_CHECK_URI = "http://sourceforge.net/projects/mingw-w64/files/mingw-w64/mingw-w64-release/"
UPSTREAM_CHECK_REGEX = "mingw-w64-v(?P<pver>(\d+[\.\-_]*)+)\.tar"
-
-
diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_8.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_9.0.0.bb
similarity index 100%
rename from recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_8.0.0.bb
rename to recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_9.0.0.bb
diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_8.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_9.0.0.bb
similarity index 88%
rename from recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_8.0.0.bb
rename to recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_9.0.0.bb
index 02132c1..e2ca6a5 100644
--- a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_8.0.0.bb
+++ b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_9.0.0.bb
@@ -2,8 +2,6 @@ DESCRIPTION = "Runtime libraries from MinGW-w64 project"

require mingw-w64.inc

-SRC_URI += "file://0001-intrincs-Check-for-__builtin_ia32_rdtsc.patch;striplevel=2"
-
S = "${WORKDIR}/mingw-w64-v${PV}/mingw-w64-crt"
B = "${WORKDIR}/build-${TARGET_SYS}"

diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_8.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_9.0.0.bb
similarity index 87%
rename from recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_8.0.0.bb
rename to recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_9.0.0.bb
index 38092dc..fb7e54e 100644
--- a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_8.0.0.bb
+++ b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_9.0.0.bb
@@ -2,8 +2,6 @@ DESCRIPTION = "Winpthreads runtime libraries from MinGW-w64 project"

require mingw-w64.inc

-SRC_URI += "file://0001-winpthreads-Add-__udivmoddi4.patch;striplevel=3"
-
S = "${WORKDIR}/mingw-w64-v${PV}/mingw-w64-libraries/winpthreads"
B = "${WORKDIR}/build-${TARGET_SYS}"
With these two patches and the binutils upgrade we see a new issue:

https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/4733/steps/12/logs/stdio

Cheers,

Richard


Re: Building Yocto on M1 Mac

Anders Montonen
 

Hi,

On 13 Feb 2022, at 14:24, Abhijeet Tripathi <abhijeettripathi3003@...> wrote:

Hello yocto-devs,

I'm new to the yocto project and trying to set up a build environment on my M1 Mac which is arm64 architecture. 

I'm following the steps as mentioned in below link:

But it is always pulling up containers based on amd64 architecture. Are there any updated steps/link to set up a build environment specific to M1 Mac(arm64)?

Looking at Docker Hub, none of the published Crops containers are built for ARM64. You can try building the containers yourself, making sure to pick base distros that are available for ARM64.

Note that there are plenty of reports of Docker performing poorly on Macs, probably because of the file system implementation. You may be better off using a full VM via e.g. UTM.

-a


Building Yocto on M1 Mac

Abhijeet Tripathi
 

Hello yocto-devs,

I'm new to the yocto project and trying to set up a build environment on my M1 Mac which is arm64 architecture. 

I'm following the steps as mentioned in below link:

But it is always pulling up containers based on amd64 architecture. Are there any updated steps/link to set up a build environment specific to M1 Mac(arm64)?

Thanks,
Abhijeet
 


[meta-mingw] [PATCH 2/2] mingw-w64: Disable parallel build

Khem Raj
 

binutils 2.38 brings up a parallel build issue, work it out by disabling
parallel build for now

Signed-off-by: Khem Raj <raj.khem@...>
---
recipes-devtools/mingw-w64/mingw-w64.inc | 4 ++++
1 file changed, 4 insertions(+)

diff --git a/recipes-devtools/mingw-w64/mingw-w64.inc b/recipes-devtools/mingw-w64/mingw-w64.inc
index 322fb79..ce5d0db 100644
--- a/recipes-devtools/mingw-w64/mingw-w64.inc
+++ b/recipes-devtools/mingw-w64/mingw-w64.inc
@@ -9,3 +9,7 @@ SRC_URI[sha256sum] = "1929b94b402f5ff4d7d37a9fe88daa9cc55515a6134805c104d1794ae2

UPSTREAM_CHECK_URI = "http://sourceforge.net/projects/mingw-w64/files/mingw-w64/mingw-w64-release/"
UPSTREAM_CHECK_REGEX = "mingw-w64-v(?P<pver>(\d+[\.\-_]*)+)\.tar"
+#| Assembler messages:
+#| i686-w64-mingw32-dlltool --as-flags=--32 -m i386 -k --as=i686-w64-mingw32-as --output-lib lib32/libd3dcompiler_41.a --input-def ../mingw-w64-v9.0.0/mingw-w64-crt/lib32/d3dcompiler_41.def
+#| i686-w64-mingw32-dlltool: failed to open temporary tail file: D3DCompiler_dll_t.o: No such file or directory
+PARALLEL_MAKE = ""
--
2.35.1


[meta-mingw] [PATCH 1/2] mingw-w64: Upgrade runtime/headers/winpthreads to 9.0.0

Khem Raj
 

Drop upstreamed fixes for rdtsc [1] __udivmoddi4[2]

[1] https://sourceforge.net/p/mingw-w64/mingw-w64/ci/6a0e9165008f731bccadfc41a59719cf7c8efc02/
[2] https://sourceforge.net/p/mingw-w64/mingw-w64/ci/ab0fa5ad3c67d634fd7754d9473d1bb7051f9bf0/

Signed-off-by: Khem Raj <raj.khem@...>
---
...rincs-Check-for-__builtin_ia32_rdtsc.patch | 33 ------------
.../0001-winpthreads-Add-__udivmoddi4.patch | 52 -------------------
recipes-devtools/mingw-w64/mingw-w64.inc | 4 +-
...b => nativesdk-mingw-w64-headers_9.0.0.bb} | 0
...b => nativesdk-mingw-w64-runtime_9.0.0.bb} | 2 -
... nativesdk-mingw-w64-winpthreads_9.0.0.bb} | 2 -
6 files changed, 1 insertion(+), 92 deletions(-)
delete mode 100644 recipes-devtools/mingw-w64/files/0001-intrincs-Check-for-__builtin_ia32_rdtsc.patch
delete mode 100644 recipes-devtools/mingw-w64/files/0001-winpthreads-Add-__udivmoddi4.patch
rename recipes-devtools/mingw-w64/{nativesdk-mingw-w64-headers_8.0.0.bb => nativesdk-mingw-w64-headers_9.0.0.bb} (100%)
rename recipes-devtools/mingw-w64/{nativesdk-mingw-w64-runtime_8.0.0.bb => nativesdk-mingw-w64-runtime_9.0.0.bb} (88%)
rename recipes-devtools/mingw-w64/{nativesdk-mingw-w64-winpthreads_8.0.0.bb => nativesdk-mingw-w64-winpthreads_9.0.0.bb} (87%)

diff --git a/recipes-devtools/mingw-w64/files/0001-intrincs-Check-for-__builtin_ia32_rdtsc.patch b/recipes-devtools/mingw-w64/files/0001-intrincs-Check-for-__builtin_ia32_rdtsc.patch
deleted file mode 100644
index ce4ba81..0000000
--- a/recipes-devtools/mingw-w64/files/0001-intrincs-Check-for-__builtin_ia32_rdtsc.patch
+++ /dev/null
@@ -1,33 +0,0 @@
-From 346de7591f58015d111f4d4f3b001382c04d5557 Mon Sep 17 00:00:00 2001
-From: Khem Raj <raj.khem@...>
-Date: Tue, 13 Apr 2021 18:44:25 -0700
-Subject: [PATCH] intrincs: Check for __builtin_ia32_rdtsc
-
-on modern gcc ( >=4.6 ) __rdtsc function is implemented using
-special builtin function called __builtin_ia32_rdtsc, its actually
-a define in gcc, so __has_builtin check fails for __rdtsc even
-though it is defined to imply __builtin_ia32_rdtsc(), therefore
-check for existence of __builtin_ia32_rdtsc as well
-
-Upstream-Status: Pending
-Signed-off-by: Khem Raj <raj.khem@...>
----
- mingw-w64-crt/intrincs/rdtsc.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/mingw-w64-crt/intrincs/rdtsc.c b/mingw-w64-crt/intrincs/rdtsc.c
-index bf9c03b..df04711 100644
---- a/mingw-w64-crt/intrincs/rdtsc.c
-+++ b/mingw-w64-crt/intrincs/rdtsc.c
-@@ -11,7 +11,7 @@
- #define __has_builtin(x) 0
- #endif
-
--#if !__has_builtin(__rdtsc)
-+#if !__has_builtin(__rdtsc) && !__has_builtin(__builtin_ia32_rdtsc)
- unsigned __int64 __rdtsc(void)
- {
- #ifdef _WIN64
---
-2.31.1
-
diff --git a/recipes-devtools/mingw-w64/files/0001-winpthreads-Add-__udivmoddi4.patch b/recipes-devtools/mingw-w64/files/0001-winpthreads-Add-__udivmoddi4.patch
deleted file mode 100644
index 3eb298e..0000000
--- a/recipes-devtools/mingw-w64/files/0001-winpthreads-Add-__udivmoddi4.patch
+++ /dev/null
@@ -1,52 +0,0 @@
-From 3b0af7327446ae179dc93b6a6ab1074251d348d0 Mon Sep 17 00:00:00 2001
-From: Khem Raj <raj.khem@...>
-Date: Fri, 30 Apr 2021 16:50:36 -0700
-Subject: [PATCH] winpthreads: Add __udivmoddi4
-
-Newer GCC ( 11.1.0+ ) is generating calls to __udivmoddi4 on i686
-architecture, therefore provide an implementation to avoid undefined
-references
-
-Upstream-Status: Pending
-Signed-off-by: Khem Raj <raj.khem@...>
----
- .../winpthreads/src/libgcc/dll_math.c | 16 +++++++++++++++-
- 1 file changed, 15 insertions(+), 1 deletion(-)
-
-diff --git a/mingw-w64-libraries/winpthreads/src/libgcc/dll_math.c b/mingw-w64-libraries/winpthreads/src/libgcc/dll_math.c
-index aeec068..d170967 100644
---- a/mingw-w64-libraries/winpthreads/src/libgcc/dll_math.c
-+++ b/mingw-w64-libraries/winpthreads/src/libgcc/dll_math.c
-@@ -121,6 +121,7 @@ u_quad_t __udivdi3(u_quad_t a, u_quad_t b);
- u_quad_t __umoddi3(u_quad_t a, u_quad_t b);
- int __ucmpdi2(u_quad_t a, u_quad_t b);
- quad_t __divmoddi4(quad_t a, quad_t b, quad_t *rem);
-+u_quad_t __udivmoddi4(u_quad_t a, u_quad_t b, u_quad_t *rem);
-
- #endif /* !_LIBKERN_QUAD_H_ */
-
-@@ -573,7 +574,20 @@ __divmoddi4(a, b, rem)
- return (negq ? -uq : uq);
- }
-
-+/*
-+ * Divide two unsigned quads.
-+ * This function is new in GCC 7.
-+ */
-+u_quad_t
-+__udivmoddi4(a, b, rem)
-+ u_quad_t a, b, *rem;
-+{
-+ u_quad_t q = __udivdi3(a, b);
-+ if (rem)
-+ *rem = a - b * q;
-+ return q;
-+}
-+
- #else
- static int __attribute__((unused)) dummy;
- #endif /*deined (_X86_) && !defined (__x86_64__)*/
--
---
-2.31.1
-
diff --git a/recipes-devtools/mingw-w64/mingw-w64.inc b/recipes-devtools/mingw-w64/mingw-w64.inc
index d40d4a5..322fb79 100644
--- a/recipes-devtools/mingw-w64/mingw-w64.inc
+++ b/recipes-devtools/mingw-w64/mingw-w64.inc
@@ -5,9 +5,7 @@ COMPATIBLE_HOST = ".*-mingw.*"

SRC_URI = "${SOURCEFORGE_MIRROR}/project/mingw-w64/mingw-w64/mingw-w64-release/mingw-w64-v${PV}.tar.bz2"

-SRC_URI[sha256sum] = "44c740ea6ab3924bc3aa169bad11ad3c5766c5c8459e3126d44eabb8735a5762"
+SRC_URI[sha256sum] = "1929b94b402f5ff4d7d37a9fe88daa9cc55515a6134805c104d1794ae22a4181"

UPSTREAM_CHECK_URI = "http://sourceforge.net/projects/mingw-w64/files/mingw-w64/mingw-w64-release/"
UPSTREAM_CHECK_REGEX = "mingw-w64-v(?P<pver>(\d+[\.\-_]*)+)\.tar"
-
-
diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_8.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_9.0.0.bb
similarity index 100%
rename from recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_8.0.0.bb
rename to recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_9.0.0.bb
diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_8.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_9.0.0.bb
similarity index 88%
rename from recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_8.0.0.bb
rename to recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_9.0.0.bb
index 02132c1..e2ca6a5 100644
--- a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_8.0.0.bb
+++ b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_9.0.0.bb
@@ -2,8 +2,6 @@ DESCRIPTION = "Runtime libraries from MinGW-w64 project"

require mingw-w64.inc

-SRC_URI += "file://0001-intrincs-Check-for-__builtin_ia32_rdtsc.patch;striplevel=2"
-
S = "${WORKDIR}/mingw-w64-v${PV}/mingw-w64-crt"
B = "${WORKDIR}/build-${TARGET_SYS}"

diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_8.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_9.0.0.bb
similarity index 87%
rename from recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_8.0.0.bb
rename to recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_9.0.0.bb
index 38092dc..fb7e54e 100644
--- a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_8.0.0.bb
+++ b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_9.0.0.bb
@@ -2,8 +2,6 @@ DESCRIPTION = "Winpthreads runtime libraries from MinGW-w64 project"

require mingw-w64.inc

-SRC_URI += "file://0001-winpthreads-Add-__udivmoddi4.patch;striplevel=3"
-
S = "${WORKDIR}/mingw-w64-v${PV}/mingw-w64-libraries/winpthreads"
B = "${WORKDIR}/build-${TARGET_SYS}"

--
2.35.1


Pass environment to kernel make

Konstantin Kletschke
 

Dear yocto community
in order to enable the option to use device tree overlays in the kernel
device tree with my bootloader (barebox in this case) I need to pass an
additional environment variable to the kernel (linux-yocto in my case)
make command.

make dtbs DTC_FLAGS=-@

Well make dtbs is working, but DTC_FLAGS=-@ needs to be added.

Is there a best practice to do this, _append/_+= in machine or distro
config or local.conf? Change kernel compile make parameters?

Regards
Konsti

--
INSIDE M2M GmbH
Konstantin Kletschke
Berenbosteler Straße 76 B
30823 Garbsen

Telefon: +49 (0) 5137 90950136
Mobil: +49 (0) 151 15256238
Fax: +49 (0) 5137 9095010

konstantin.kletschke@...
http://www.inside-m2m.de

Geschäftsführung: Michael Emmert, Ingo Haase, Dr. Fred Könemann, Derek Uhlig
HRB: 111204, AG Hannover


Re: Minutes: Yocto Project Weekly Triage Meeting 2/10/2022

Saul Wold
 

On 2/11/22 12:49, Randy MacLeod wrote:
On 2022-02-10 13:50, Trevor Gamblin wrote:

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

*Attendees: *Andrei, Alexandre, Armin, Bruce, Daiane, Joshua, Pavel, Randy, Richard, Saul, Stephen, Steve, Tim, Trevor

*ARs:*

- Saul to address NEEDINFO bugs from Robert Berger
Re-Assigned 14626 - lttng back to myself.

both 14629 & 14709 needs input from Robert.

Sau!


- Randy to search Bugzilla for prelink bugs to close
Done.
I closed 3 prelink issues as obsolete:
1.Prelink: doesn't work on ppc64
https://bugzilla.yoctoproject.org/show_bug.cgi?id=1331
2. Investigate if -mtls-dialect=gnu2 support within the prelinker behavior
https://bugzilla.yoctoproject.org/show_bug.cgi?id=8664
3. On-target binutils produces non-running code when linking with "-Wl,-z,nocopyreloc" on ARM or PPC
"The prelink test suite has two tests (reloc8 and reloc9) that attempt to link an application with "-Wl,-z,nocopyreloc". This worked through "krogoth" but no longer works on master. ..."
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10168
The remaining issues that mention prelink, do NOT appear to be
ones that we can resolve as the prelink package/feature is only involved tangentially.
https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=prelink&list_id=648622
../Randy

*Notes:*

- (Correction) ~43% of AB workers have been switched to SSDs. Failure rate appears lower, but still TBD

*Medium+ 3.5 Unassigned Enhancements/Bugs: *79 (Last week 76)

*Medium+ 3.99 Unassigned Enhancements/Bugs: *39**(Last week 39)

*AB Bugs: *75 (Last week 73)
--
# Randy MacLeod
# Wind River Linux
--
Sau!


Re: Minutes: Yocto Project Weekly Triage Meeting 2/10/2022

Randy MacLeod
 

On 2022-02-10 13:50, Trevor Gamblin wrote:

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

Attendees: Andrei, Alexandre, Armin, Bruce, Daiane, Joshua, Pavel, Randy, Richard, Saul, Stephen, Steve, Tim, Trevor

ARs:

- Saul to address NEEDINFO bugs from Robert Berger

- Randy to search Bugzilla for prelink bugs to close

Done.

I closed 3 prelink issues as obsolete:

1.Prelink: doesn't work on ppc64
   https://bugzilla.yoctoproject.org/show_bug.cgi?id=1331

2. Investigate if -mtls-dialect=gnu2 support within the prelinker behavior
 
  https://bugzilla.yoctoproject.org/show_bug.cgi?id=8664

3.  On-target binutils produces non-running code when linking with "-Wl,-z,nocopyreloc" on ARM or PPC
   
"The prelink test suite has two tests (reloc8 and reloc9) that attempt to link an application with "-Wl,-z,nocopyreloc". This worked through "krogoth" but no longer works on master. ..."

   https://bugzilla.yoctoproject.org/show_bug.cgi?id=10168

The remaining issues that mention prelink, do NOT appear to be
ones that we can resolve as the prelink package/feature is only involved tangentially.

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=prelink&list_id=648622


../Randy


Notes:

- (Correction) ~43% of AB workers have been switched to SSDs. Failure rate appears lower, but still TBD

Medium+ 3.5 Unassigned Enhancements/Bugs: 79 (Last week 76)

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

AB Bugs: 75 (Last week 73)


-- 
# Randy MacLeod
# Wind River Linux


Re: Possible to ignore a missing file in recipe without error?

Josef Holzmayr
 

Howdy!

On 11. Feb 2022, at 20:03, Howard <howard.egan@...> wrote:

Hi:

I have a simple recipe that installs a few miscellaneous files, one of the files may or may not be present and in reality that's ok for the moment, but I don't see a way to do things in a recipe based on the presence or absence of a file. 

The real question is: what is the condition? It must be something that is constant across all of the build. And if can only come from either a .conf file or the environment, otherwise it would not be visible in the recipe.


For example:

LICENSE="CLOSED"

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

# always present file
SRC_URI += "file://myconfig.config"

# sometimes present file - is there a way to conditionally do this statement
SRC_URI += "file://myOtherConfig.config"

A possible approach would be only appending depending on a specific DISTRO_FLAG, via bb.utils.contains. I have done something similar at https://github.com/TheYoctoJester/meta-zinc/blob/5c566c2f7d29d9db15db0c70cd3dd79fa755c351/recipes-zinc/libanswer/libanswer_git.bb#L26

But again, it depends on the exact use case.

Greetz


do_install() {
    install -d ${D}${sysconfdir}
    install -m 0755 ${WORKDIR}/myconfig.config ${D}${sysconfdir}
    #same here
    install -m 0755 ${WORKDIR}/myOtherConfig.config ${D}${sysconfdir}

}

FILES_${PN} += " ${sysconfdir}/myconfig.config "
#same here
FILES_${PN} += " ${sysconfdir}/myOtherConfig.config "


Many thanks
Howard





Re: gpsd recipe not installing clients

mattwood2000@...
 

Thanks everyone.

Looks like this whole thing came down to a typo. I had originally
tried gpsd-utils and got the nothing RPROVIDES error. Missed that it
was in fact gps-utils!

Thanks again, have it working now.

On Fri, Feb 11, 2022 at 11:41 AM Marc Ferland <marc.ferland@...> wrote:

gps-utils is the package you are looking for.
Marc

On Fri, Feb 11, 2022 at 11:32 AM Alexander Kanavin <alex.kanavin@...> wrote:

Check tmp/work/cortexa53-poky-linux/gpsd/3.23.1-r0/packages-split to
see what package the needed binaries go into.

Alex

On Fri, 11 Feb 2022 at 17:23, <mattwood2000@...> wrote:

Hi,

I am trying to include gpsd in a poky build. The core components are
included, i.e gpsd gpsctl and gpsdctl, but the clients like gpspipe
and gpsmon do not make it to the final image.

For context, I'm building for the raspberry pi 3b+ using
core-image-full-cmdline.

I see all of the clients in
tmp/work/cortexa53-poky-linux/gpsd/3.23.1-r0/image/usr/bin however.

What am I missing? I didn't see anything in the recipe that would
indicate a conditional install flag.

Thanks, Matt.




Possible to ignore a missing file in recipe without error?

Howard
 

Hi:

I have a simple recipe that installs a few miscellaneous files, one of the files may or may not be present and in reality that's ok for the moment, but I don't see a way to do things in a recipe based on the presence or absence of a file. 

For example:

LICENSE="CLOSED"

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

# always present file
SRC_URI += "file://myconfig.config"

# sometimes present file - is there a way to conditionally do this statement
SRC_URI += "file://myOtherConfig.config"



do_install() {
    install -d ${D}${sysconfdir}
    install -m 0755 ${WORKDIR}/myconfig.config ${D}${sysconfdir}
    #same here
    install -m 0755 ${WORKDIR}/myOtherConfig.config ${D}${sysconfdir}

}

FILES_${PN} += " ${sysconfdir}/myconfig.config "
#same here
FILES_${PN} += " ${sysconfdir}/myOtherConfig.config "


Many thanks
Howard


Re: gpsd recipe not installing clients

Marc Ferland
 

gps-utils is the package you are looking for.
Marc

On Fri, Feb 11, 2022 at 11:32 AM Alexander Kanavin <alex.kanavin@...> wrote:
>
> Check tmp/work/cortexa53-poky-linux/gpsd/3.23.1-r0/packages-split to
> see what package the needed binaries go into.
>
> Alex
>
> On Fri, 11 Feb 2022 at 17:23, <mattwood2000@...> wrote:
> >
> > Hi,
> >
> > I am trying to include gpsd in a poky build.  The core components are
> > included, i.e gpsd gpsctl and gpsdctl, but the clients like gpspipe
> > and gpsmon do not make it to the final image.
> >
> > For context, I'm building for the raspberry pi 3b+ using
> > core-image-full-cmdline.
> >
> > I see all of the clients in
> > tmp/work/cortexa53-poky-linux/gpsd/3.23.1-r0/image/usr/bin however.
> >
> > What am I missing?  I didn't see anything in the recipe that would
> > indicate a conditional install flag.
> >
> > Thanks, Matt.
> >
> >
> >
>
>
>


Re: gpsd recipe not installing clients

Alexander Kanavin
 

Check tmp/work/cortexa53-poky-linux/gpsd/3.23.1-r0/packages-split to
see what package the needed binaries go into.

Alex

On Fri, 11 Feb 2022 at 17:23, <mattwood2000@...> wrote:

Hi,

I am trying to include gpsd in a poky build. The core components are
included, i.e gpsd gpsctl and gpsdctl, but the clients like gpspipe
and gpsmon do not make it to the final image.

For context, I'm building for the raspberry pi 3b+ using
core-image-full-cmdline.

I see all of the clients in
tmp/work/cortexa53-poky-linux/gpsd/3.23.1-r0/image/usr/bin however.

What am I missing? I didn't see anything in the recipe that would
indicate a conditional install flag.

Thanks, Matt.