Date   

Re: #yocto systemd not able to start sshd after a reboot #yocto

Khem Raj
 

On 9/21/20 5:17 AM, srijan.nandi@... wrote:
/Seems that some leftovers from System V still reside in YOCTO...
Correct???
Yocto project supports sysvinit as init system option as well so no there are no leftovers.

/
Not sure about that.
The problem I faced was because there was a sshd.socket that had the following line in it. The sshd.socket comes with openssh.
Conflicts=sshd.service
So I had two options. either to add the ExecStartPre in the sshd.service file or to remove the Conflicts line in sshd.socket.
I choose to remove the Conflicts line and add the following in the sshd.socket file.
After=network.target
Before=sshd.service
Usually you use socket activation for sshd then you would enable sshd.socket and not sshd.service, socket will be listening on incoming connections on ssh port ( 22 by defaault ) and launch sshd.service whenever there is incoming ssh connection request. I suggest you should perhaps follow this approach as well, its also efficient due to its on-demand launch nature.

Thanks and Regards,
-=Srijan Nandi


Re: preistall package when use a package manager

Khem Raj
 

On 9/21/20 1:28 AM, Matteo Facchinetti wrote:
Hi,
I need to preinstall a package in a specific directory in my target image.
In detail I use RPM package manager and I like to include RPM packages in my target to provide a way to install services only when used.
This is useful when you don't have an internet connection.
Is there a way to do this?
Opinions are welcome.
it seems you want to bundle unstalled packages ( rpms ) in your firmware, perhaps you can look at adding a ROOTFS_POSTPROCESS_COMMAND and copy the needed packages, but you need to be sure that all dependencies(rpms) are also made available as part of this bundle
and you have to check this consistency everytime you update firmware


Regards,
Matteo
Sirius Electronic Systems


Re: RDEPENDS problem

Maciej Pijanowski
 


On 21.09.2020 23:46, Greg Wilson-Lindberg wrote:
 I have a custom recipe that copies a .so, that libMotors.so calls functions in another libcanfestival.so.

When I first added in the copy of the .so
I didn't have an RDEPENDS and Yocto printed out an warning listing the package that it wanted. I added an RDEPENDS_${PN} 
with all of the packages listed, but I'm still getting an error for the first libMotors.so:

ERROR: userconfig-1.0-r0 do_package_qa: QA Issue: /home/sakura/lib/libMotors.so.1.0.0 contained in package userconfig requires libcanfestival.so, but no providers found in RDEPENDS_userconfig? [file-rdeps]

In userdepends I added:

RDEPENDS_${PN} += "canfestival libelf libgcrypt pcsc-lite-lib qtbase qtdeclarative qtserialport zint"

Package canfestival_3-asc in has:

FILES_${PN} = "/usr/lib/libcanfestival.so /usr/lib/libcanfestival_unix.so /usr/lib/libcanfestival_can_socket.so"

which seems to me like it should satisfy the requirements of the RDEPENDS, but it is not. bitbake initially gave me a warning 
that listed canfestival as needing to be added to an RDEPENDS for userconfig. But now it is saying that it can't figure out
what package supplies the libcanfestival.so file.

Can someone help me to understand what is going on? How do I explicitly say that a package supplies a given file?
You could try with PROVIDES: https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-PROVIDES



-- 
Maciej Pijanowski
Embedded Systems Engineer
GPG: 9963C36AAC3B2B46
https://3mdeb.com | @3mdeb_com


[meta-zephyr][morty PATCH] zephyr-kernel: update URLs

Jon Mason
 

URLs no longer point to a valid location. Update to the current
location.

Signed-off-by: Jon Mason <jon.mason@...>
---
classes/zephyr-kernel-src.bbclass | 2 +-
recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/classes/zephyr-kernel-src.bbclass b/classes/zephyr-kernel-src.bbclass
index d7aa81bfaa62..cd1503dc1299 100644
--- a/classes/zephyr-kernel-src.bbclass
+++ b/classes/zephyr-kernel-src.bbclass
@@ -3,7 +3,7 @@
PREFERRED_VERSION_zephyr-kernel ??= "1.6.0"

SRCREV = "d4e799d77a36eaf6d678b357c207411ec32b2d62"
-SRC_URI = "git://gerrit.zephyrproject.org/r/zephyr.git;protocol=https;branch=v1.6.0-branch \
+SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v1.6-branch \
file://Makefile.toolchain.yocto "
PV = "1.6.0"

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb
index df373e850c94..b47e8ac1b7d0 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc"

# tag v1.6.0
SRCREV="d4e799d77a36eaf6d678b357c207411ec32b2d62"
-SRC_URI = "git://gerrit.zephyrproject.org/r/zephyr.git;protocol=https;branch=v1.6.0-branch"
+SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v1.6-branch"
SRC_URI += "file://Makefile.toolchain.yocto"

PV = "1.6.0"
--
2.20.1


[meta-zephyr][PATCH] zephyr-kernel: Add python dependencies

Jon Mason
 

Zephyr refuses to compile due to missing python dependencies.

Signed-off-by: Jon Mason <jon.mason@...>
Signed-off-by: Ross Burton <ross.burton@...>
---
recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 2 ++
1 file changed, 2 insertions(+)

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
index d7147d5b7b86..7e569edb694c 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
@@ -2,6 +2,7 @@

ZEPHYR_INHERIT_CLASSES += "zephyr cmake"
inherit ${ZEPHYR_INHERIT_CLASSES}
+inherit python3native

# There shouldn't be a manifest for zephyr kernels since there is no root
# filesystem.
@@ -20,6 +21,7 @@ export ZEPHYR_BASE="${S}"
# We always need a toolchain to cross-compile.
INHIBIT_DEFAULT_DEPS = "1"
DEPENDS += "gcc-cross-${TARGET_ARCH} libgcc ${TOOLCHAIN_TARGET_TASK} gperf-native"
+DEPENDS += " python3-pyelftools-native python3-pyyaml-native"
CROSS_COMPILE = "${STAGING_BINDIR_TOOLCHAIN}/${TARGET_PREFIX}"

DEPENDS_append_qemuall = " qemu-native qemu-helper-native"
--
2.20.1


RDEPENDS problem

Greg Wilson-Lindberg
 

I have a custom recipe that copies a .so, that libMotors.so calls functions in another libcanfestival.so.

When I first added in the copy of the .so
I didn't have an RDEPENDS and Yocto printed out an warning listing the package that it wanted. I added an RDEPENDS_${PN}
with all of the packages listed, but I'm still getting an error for the first libMotors.so:

ERROR: userconfig-1.0-r0 do_package_qa: QA Issue: /home/sakura/lib/libMotors.so.1.0.0 contained in package userconfig requires libcanfestival.so, but no providers found in RDEPENDS_userconfig? [file-rdeps]

In userdepends I added:

RDEPENDS_${PN} += "canfestival libelf libgcrypt pcsc-lite-lib qtbase qtdeclarative qtserialport zint"

Package canfestival_3-asc in has:

FILES_${PN} = "/usr/lib/libcanfestival.so /usr/lib/libcanfestival_unix.so /usr/lib/libcanfestival_can_socket.so"

which seems to me like it should satisfy the requirements of the RDEPENDS, but it is not. bitbake initially gave me a warning
that listed canfestival as needing to be added to an RDEPENDS for userconfig. But now it is saying that it can't figure out
what package supplies the libcanfestival.so file.

Can someone help me to understand what is going on? How do I explicitly say that a package supplies a given file?


Re: Can't found the zip.h during bitbake #yocto #devtool

Khem Raj
 

Add

DEPENDS += "libzip"

in failing recipe ( .bb) file.

On Mon, Sep 21, 2020 at 12:40 AM Jaymin Dabhi via
lists.yoctoproject.org
<jaymin.dabhi=vivaldi.net@...> wrote:


Team,

I need to include zip.h header file in one of my C code (#include <zip.h>).
I have created a .bb file and added following command for compilation:

${CC} -Wall -I/usr/include/libxml2 -o my_code my_code.c -lxml2 -lzip -lz

But, during bitbake it says:

| In file included from fota_update.c:1:0:
| fota_update.h:5:17: fatal error: zip.h: No such file or directory
| #include <zip.h>
| ^
| compilation terminated.

Using the same compilation command, I am able to compile the code on my PC. But, can't compile with Yocto.

I have tried with lzip and zip packages by adding into local.conf, but didn't work.

Which zip package I need to use for including the zip.h header file?



Re: Yocto recipe for Tailscale #yocto #golang

Randy MacLeod
 

On 2020-09-19 4:58 p.m., Mike Thompson via lists.yoctoproject.org wrote:

I seemed to have resolved all my issues getting a Yocto Bitbake recipe for the Tailscale client and CLI utility.

For future reference and in case it helps others, below is my Bitbake recipe:

Hi Mike,

Could you send your tailscale recipe to meta-openembedded/meta-networking?
    Email: OpenEmbedded Development mailing list <openembedded-devel@...>
    Instructions: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

It looks like all the work is done aside from an email!

../Randy


------------------------------------------------

# tailscale_1.0.5.bb

SUMMARY = "Tailscale client and daemon for Linux"

HOMEPAGE = "github.com/tailscale/tailscale"

SECTION = "net"

 

LICENSE = "CLOSED"

LIC_FILES_CHKSUM = "file://src/${GO_IMPORT}/LICENSE;md5=d995c1c44529856a0f35a5ad43e51cc5"

 

SRC_URI = "git://github.com/tailscale/tailscale.git;nobranch=1;tag=v${PV}"

 

inherit go-mod systemd

 

GO_IMPORT = "tailscale.com"

GO_WORKDIR = "${GO_IMPORT}"

GO_INSTALL = "${GO_IMPORT}/cmd/tailscale ${GO_IMPORT}/cmd/tailscaled"

 

FILES_${PN} += "${systemd_unitdir}/*"

 

do_install() {

    install -d ${D}/${bindir}

    install -d ${D}/${sbindir}

    install ${B}/bin/tailscale ${D}/${bindir}/tailscale

    install ${B}/bin/tailscaled ${D}/${sbindir}/tailscaled

 

    if ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'true', 'false', d)}; then

        install -d ${D}${sysconfdir}/default/

        install -m 0644 ${WORKDIR}/build/src/${GO_IMPORT}/cmd/tailscaled/tailscaled.defaults ${D}${sysconfdir}/default/tailscaled

 

        install -d ${D}${systemd_unitdir}/system

        install -m 0644 ${WORKDIR}/build/src/${GO_IMPORT}/cmd/tailscaled/tailscaled.service ${D}${systemd_unitdir}/system/tailscaled.service

 

        install -d ${D}${sysconfdir}/systemd/system/multi-user.target.wants/

        ln -s ${systemd_unitdir}/system/tailscaled.service ${D}${sysconfdir}/systemd/system/multi-user.target.wants/tailscaled.service

    fi

}

 

SYSTEMD_PACKAGES = "${PN}"

SYSTEMD_SERVICE_${PN} = "tailscaled.service"

SYSTEMD_AUTO_ENABLE = "enable"

------------------------------------------------

 
When installed on my target system, systemd reports the following for the tailscaled daemon:
------------------------------------------------
[[0;1;32m●[[0m tailscaled.service - Tailscale node agent
     Loaded: loaded (/lib/systemd/system/tailscaled.service; enabled; vendor preset: enabled)
     Active: [[0;1;32mactive (running)[[0m since Sat 2020-09-19 20:46:02 UTC; 4min 44s ago
       Docs: https://tailscale.com/kb/
   Main PID: 252 (tailscaled)
      Tasks: 13 (limit: 19081)
     Memory: 56.5M
     CGroup: /system.slice/tailscaled.service
             └─252 /usr/sbin/tailscaled --state=/var/lib/tailscale/tailscaled.state --socket=/run/tailscale/tai
lscaled.sock --port 41641
 
Sep 19 20:48:03 amber tailscaled[252]: 7.2M/39.1M control: cancelMapSafely: synced=false
Sep 19 20:48:03 amber tailscaled[252]: 7.2M/39.1M control: cancelMapSafely: wrote to channel
Sep 19 20:48:03 amber tailscaled[252]: 7.2M/39.1M control: mapRoutine: new map needed while idle.
Sep 19 20:48:03 amber tailscaled[252]: 7.2M/39.1M control: mapRoutine: state:url-visit-required
Sep 19 20:48:03 amber tailscaled[252]: 7.3M/39.1M LinkChange(isExpensive=false); needsRebind=false
Sep 19 20:48:03 amber tailscaled[252]: 7.3M/39.1M magicsock: starting endpoint update (link-change-minor)
Sep 19 20:48:03 amber tailscaled[252]: 7.6M/39.1M LinkChange(isExpensive=false); needsRebind=false
Sep 19 20:48:03 amber tailscaled[252]: 7.6M/39.1M magicsock: starting endpoint update (link-change-minor)
Sep 19 20:48:03 amber tailscaled[252]: 7.5M/39.1M LinkChange(isExpensive=false); needsRebind=false
Sep 19 20:48:03 amber tailscaled[252]: 7.2M/39.1M magicsock: starting endpoint update (link-change-minor)

------------------------------------------------

 
And ifconfig reports the following:
------------------------------------------------

# ifconfig

tailscale0 Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  

          inet6 addr: fe80::7f12:8835:cc06:b3e7/64 Scope:Link

          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1280  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:500 

          RX bytes:0 (0.0 B)  TX bytes:825 (825.0 B)

------------------------------------------------

Thank you to Khem for the tip on looking into "inherit go-mod" and patience while I sorted through this.
 
Mike Thompson
 




-- 
# Randy MacLeod
# Wind River Linux


Re: #yocto systemd not able to start sshd after a reboot #yocto

srijan.nandi@...
 

Seems strange to me too...I had been troubleshooting the sshd.service issue for two days. There was no logs, nothing. I was just hitting the wall. I tried a lot of combinations to get it to work but all failed.

The sshd.service was starting, if I manually did a systemctl start sshd.service. But always failed at startup. At times it would start and then get a signal 15 terminating and would close the daemon.

After not able to resolve the issue, I started checking all the other services. Every other service was starting at bootup just fine except sshd.

Not finding anything else to troubleshoot. I happened to stumble upon the sshd.socket and the Conflicts part of it. Did a hit and trial and it worked. Technically I still am not sure as to why..

-=Srijan Nandi


Re: #yocto systemd not able to start sshd after a reboot #yocto

Zoran
 

There was a sshd.socket file in /lib/systemd/system which had the following line in it.
Interesting... Pushed/forced me to think.

There is no formal dependency between sshd.service and sshd.socket!

[vuser@fedora32-ssd systemd]$ systemctl list-dependencies sshd.service
| grep ssh
sshd.service
● ├─sshd-keygen.target
● │ ├─sshd-keygen@...
● │ ├─sshd-keygen@...
● │ └─sshd-keygen@...
[vuser@fedora32-ssd systemd]$ systemctl list-dependencies sshd.service
| grep socket
● ├─lvm2-lvmetad.socket
● ├─lvm2-lvmpolld.socket
[vuser@fedora32-ssd systemd]$ systemctl list-dependencies sshd.socket
| grep sshd
sshd.socket

Strange... Isn't it?!

Zoran
_______

On Sat, Sep 19, 2020 at 3:37 PM <srijan.nandi@...> wrote:

Hello All,

I finally got it to work!!!

There was a sshd.socket file in /lib/systemd/system which had the following line in it.

Conflicts=sshd.service

I remove it and added the following two lines:

After=network.target
Before=sshd.service

And that did the trick. Now sshd service starts on every boot.

Thanks,
-=Srijan Nandi


Re: [meta-mingw][PATCH] Override SDK_VENDOR

Joshua Watt
 



On Mon, Sep 21, 2020, 8:12 AM Samuli Piippo <samuli.piippo@...> wrote:

On Mon, 21 Sep 2020 at 15:53, Joshua Watt <JPEWhacker@...> wrote:
On Fri, Sep 18, 2020 at 7:30 AM Samuli Piippo <samuli.piippo@...> wrote:
>
> Set SDK_VENDOR to '-w64', which makes the host triplet match what GCC
> expect to find when using mingw32-w64. This enables features that are
> not functional in the classic mingw32, but have been implemented in the
> mingw32-w64.

Does this enable it for the i686 toolchain also? Does that make sense?

This enables it for both x86_64-mingw32 and i686-mingw32 targets and it makes sense
since it's not about the target bitness but the mingw implementation. w64 has support
for both targets and provides improved support over the original mingw32.

Thanks. I figured that was the case. This is testing on the AB.

 
>
> Disable 32bit libs from the runtime component when compiling for 64bit,
> which were enabled as a side effect of the GCC config change.
>
> Signed-off-by: Samuli Piippo <samuli.piippo@...>
> ---
>  conf/machine-sdk/include/mingw32-common.inc                    | 3 +++
>  .../mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb             | 2 ++
>  2 files changed, 5 insertions(+)
>
> diff --git a/conf/machine-sdk/include/mingw32-common.inc b/conf/machine-sdk/include/mingw32-common.inc
> index 9011ded..bc6c91e 100644
> --- a/conf/machine-sdk/include/mingw32-common.inc
> +++ b/conf/machine-sdk/include/mingw32-common.inc
> @@ -1,4 +1,7 @@
>  SDK_OS = "mingw32"
> +SDK_VENDOR_mingw32 = "-w64"
> +SDK_VENDOR_sdkmingw32 = "-w64"
> +
>  NATIVESDKLIBC = "libc-mingw"
>
>  PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-for-gcc_mingw32 = "nativesdk-mingw-w64-runtime"
> diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb
> index cf39c6a..9f79ffe 100644
> --- a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb
> +++ b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb
> @@ -19,6 +19,8 @@ PROVIDES += "virtual/nativesdk-libintl"
>
>  TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}"
>
> +EXTRA_OECONF_x86-64 = "--disable-lib32"
> +
>  do_configure() {
>      oe_runconf
>  }
> --
> 2.17.1
>




Re: [meta-mingw][PATCH] Override SDK_VENDOR

Samuli Piippo
 


On Mon, 21 Sep 2020 at 15:53, Joshua Watt <JPEWhacker@...> wrote:
On Fri, Sep 18, 2020 at 7:30 AM Samuli Piippo <samuli.piippo@...> wrote:
>
> Set SDK_VENDOR to '-w64', which makes the host triplet match what GCC
> expect to find when using mingw32-w64. This enables features that are
> not functional in the classic mingw32, but have been implemented in the
> mingw32-w64.

Does this enable it for the i686 toolchain also? Does that make sense?

This enables it for both x86_64-mingw32 and i686-mingw32 targets and it makes sense
since it's not about the target bitness but the mingw implementation. w64 has support
for both targets and provides improved support over the original mingw32.
 
>
> Disable 32bit libs from the runtime component when compiling for 64bit,
> which were enabled as a side effect of the GCC config change.
>
> Signed-off-by: Samuli Piippo <samuli.piippo@...>
> ---
>  conf/machine-sdk/include/mingw32-common.inc                    | 3 +++
>  .../mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb             | 2 ++
>  2 files changed, 5 insertions(+)
>
> diff --git a/conf/machine-sdk/include/mingw32-common.inc b/conf/machine-sdk/include/mingw32-common.inc
> index 9011ded..bc6c91e 100644
> --- a/conf/machine-sdk/include/mingw32-common.inc
> +++ b/conf/machine-sdk/include/mingw32-common.inc
> @@ -1,4 +1,7 @@
>  SDK_OS = "mingw32"
> +SDK_VENDOR_mingw32 = "-w64"
> +SDK_VENDOR_sdkmingw32 = "-w64"
> +
>  NATIVESDKLIBC = "libc-mingw"
>
>  PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-for-gcc_mingw32 = "nativesdk-mingw-w64-runtime"
> diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb
> index cf39c6a..9f79ffe 100644
> --- a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb
> +++ b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb
> @@ -19,6 +19,8 @@ PROVIDES += "virtual/nativesdk-libintl"
>
>  TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}"
>
> +EXTRA_OECONF_x86-64 = "--disable-lib32"
> +
>  do_configure() {
>      oe_runconf
>  }
> --
> 2.17.1
>




Re: [meta-mingw][PATCH] Override SDK_VENDOR

Joshua Watt
 

On Fri, Sep 18, 2020 at 7:30 AM Samuli Piippo <samuli.piippo@...> wrote:

Set SDK_VENDOR to '-w64', which makes the host triplet match what GCC
expect to find when using mingw32-w64. This enables features that are
not functional in the classic mingw32, but have been implemented in the
mingw32-w64.
Does this enable it for the i686 toolchain also? Does that make sense?


Disable 32bit libs from the runtime component when compiling for 64bit,
which were enabled as a side effect of the GCC config change.

Signed-off-by: Samuli Piippo <samuli.piippo@...>
---
conf/machine-sdk/include/mingw32-common.inc | 3 +++
.../mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb | 2 ++
2 files changed, 5 insertions(+)

diff --git a/conf/machine-sdk/include/mingw32-common.inc b/conf/machine-sdk/include/mingw32-common.inc
index 9011ded..bc6c91e 100644
--- a/conf/machine-sdk/include/mingw32-common.inc
+++ b/conf/machine-sdk/include/mingw32-common.inc
@@ -1,4 +1,7 @@
SDK_OS = "mingw32"
+SDK_VENDOR_mingw32 = "-w64"
+SDK_VENDOR_sdkmingw32 = "-w64"
+
NATIVESDKLIBC = "libc-mingw"

PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-for-gcc_mingw32 = "nativesdk-mingw-w64-runtime"
diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb
index cf39c6a..9f79ffe 100644
--- a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb
+++ b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb
@@ -19,6 +19,8 @@ PROVIDES += "virtual/nativesdk-libintl"

TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}"

+EXTRA_OECONF_x86-64 = "--disable-lib32"
+
do_configure() {
oe_runconf
}
--
2.17.1


Re: #yocto systemd not able to start sshd after a reboot #yocto

srijan.nandi@...
 

Seems that some leftovers from System V still reside in YOCTO... Correct???

Not sure about that. 

The problem I faced was because there was a sshd.socket that had the following line in it. The sshd.socket comes with openssh. 

Conflicts=sshd.service

So I had two options. either to add the ExecStartPre in the sshd.service file or to remove the Conflicts line in sshd.socket. 

I choose to remove the Conflicts line and add the following in the sshd.socket file.

After=network.target
Before=sshd.service

Thanks and Regards,
-=Srijan Nandi


Re: wvdial & wvstream Error

Martin Jansa
 

Are you trying to use it with openssl-1.0.*? Either use openssl-1.1 or revert the changes from https://github.com/apenwarr/wvstreams/pull/2/commits.


On Mon, Sep 21, 2020 at 10:55 AM Zoltan Kerenyi Nagy <kerenyi.nagy.zoltan@...> wrote:
Hi,

I was messing around with wvdial & wvstream for a while. Now the patches are at the correct locations, but still there is a compile error:

Here is the error log:


Could you please point me the error? I suppose, its gonna be a Layer 8 error :-)

Thanks guys!

Zolee




wvdial & wvstream Error

Zoltan Kerenyi Nagy <kerenyi.nagy.zoltan@...>
 

Hi,

I was messing around with wvdial & wvstream for a while. Now the patches are at the correct locations, but still there is a compile error:

Here is the error log:


Could you please point me the error? I suppose, its gonna be a Layer 8 error :-)

Thanks guys!

Zolee


preistall package when use a package manager

Matteo Facchinetti
 

Hi,

I need to preinstall a package in a specific directory in my target image.

In detail I use RPM package manager and I like to include RPM packages in my target to provide a way to install services only when used.
This is useful when you don't have an internet connection.

Is there a way to do this?
Opinions are welcome. 

Regards,
Matteo
Sirius Electronic Systems


[meta-mingw][PATCHv2] ninja: configure for mingw platform

Samuli Piippo
 

Signed-off-by: Samuli Piippo <samuli.piippo@...>
---
recipes-core/images/core-image-mingw-sdktest.bb | 1 +
recipes-devtools/ninja/ninja_%.bbappend | 8 ++++++++
2 files changed, 9 insertions(+)
create mode 100644 recipes-devtools/ninja/ninja_%.bbappend

diff --git a/recipes-core/images/core-image-mingw-sdktest.bb b/recipes-core/images/core-image-mingw-sdktest.bb
index 6215aef..9060c3d 100644
--- a/recipes-core/images/core-image-mingw-sdktest.bb
+++ b/recipes-core/images/core-image-mingw-sdktest.bb
@@ -10,6 +10,7 @@ TOOLCHAIN_HOST_TASK += "\
nativesdk-dbus \
nativesdk-dtc \
nativesdk-libarchive \
+ nativesdk-ninja \
nativesdk-swig \
nativesdk-wayland \
"
diff --git a/recipes-devtools/ninja/ninja_%.bbappend b/recipes-devtools/ninja/ninja_%.bbappend
new file mode 100644
index 0000000..e7ddb4d
--- /dev/null
+++ b/recipes-devtools/ninja/ninja_%.bbappend
@@ -0,0 +1,8 @@
+do_compile_mingw32() {
+ python3 ./configure.py --platform mingw
+ ninja
+}
+
+do_install_mingw32() {
+ install -D -m 0755 ${S}/ninja.exe ${D}${bindir}/ninja.exe
+}
--
2.17.1


Can't found the zip.h during bitbake #yocto #devtool

Jaymin Dabhi
 

Team,

I need to include zip.h header file in one of my C code (#include <zip.h>).
I have created a .bb file and added following command for compilation:
${CC} -Wall -I/usr/include/libxml2 -o my_code my_code.c -lxml2 -lzip -lz
But, during bitbake it says:

| In file included from fota_update.c:1:0:
| fota_update.h:5:17: fatal error: zip.h: No such file or directory
|  #include <zip.h>
|                  ^
| compilation terminated.
Using the same compilation command, I am able to compile the code on my PC. But, can't compile with Yocto.

I have tried with lzip and zip packages by adding into local.conf, but didn't work.

Which zip package I need to use for including the zip.h header file?


[meta-zephyr][PATCH] README.txt: update doc

Naveen Saini
 

Add python dependencies.

Signed-off-by: Naveen Saini <naveen.kumar.saini@...>
---
README.txt | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/README.txt b/README.txt
index 208843b..be1ea39 100644
--- a/README.txt
+++ b/README.txt
@@ -8,11 +8,17 @@ https://wiki.yoctoproject.org/wiki/TipsAndTricks/BuildingZephyrImages
Prerequisites:
==============

-Yocto distro (master)"
+This layer depends on:
+ Yocto distro (master)
+ git://git.yoctoproject.org/poky
+ Python layer (meta-openembedded/meta-python)
+ git://git.openembedded.org/meta-openembedded

Modify local conf by adding:
DISTRO="zephyr"

+Add "meta-openembedded/meta-oe" to BBLAYERS
+Add "meta-openembedded/meta-python" to BBLAYERS
Add "meta-zephyr" to BBLAYERS

Building and Running Zephyr Samples
--
2.27.0