|
Force binary package install
It was definitely an architecture mismatch. I checked the architecture of the files with objdump. That is what threw me off in the first place. I simply checked the versions. They were off but I could
It was definitely an architecture mismatch. I checked the architecture of the files with objdump. That is what threw me off in the first place. I simply checked the versions. They were off but I could
|
By
Rudolf J Streif
· #57329
·
|
|
Force binary package install
Thanks, Richard. I was sidetracked by other stuff, hence the delay. Please see below. That's the objdump on libc.so.6 on the target (aarch64, Honister): Version definitions: 1 0x01 0x0865f4e6 libc.so.
Thanks, Richard. I was sidetracked by other stuff, hence the delay. Please see below. That's the objdump on libc.so.6 on the target (aarch64, Honister): Version definitions: 1 0x01 0x0865f4e6 libc.so.
|
By
Rudolf J Streif
· #57326
·
|
|
Force binary package install
It's Yocto that creates the spec file for rpm. Apparently, besides relying on what is declared in RDEPENDS, it actually iterates over the files and appends the dependencies (and their versions). It re
It's Yocto that creates the spec file for rpm. Apparently, besides relying on what is declared in RDEPENDS, it actually iterates over the files and appends the dependencies (and their versions). It re
|
By
Rudolf J Streif
· #57302
·
|
|
Force binary package install
Yes, thank you. ERROR: xxx-single-group-0.1-r0 do_package_qa: QA Issue: /opt/binstuf/linux-allwinneryocto-armle-opengles_2.0-obj/lib/libfbxsdk.so contained in package xxx-single-group requires libpthr
Yes, thank you. ERROR: xxx-single-group-0.1-r0 do_package_qa: QA Issue: /opt/binstuf/linux-allwinneryocto-armle-opengles_2.0-obj/lib/libfbxsdk.so contained in package xxx-single-group requires libpthr
|
By
Rudolf J Streif
· #57300
·
|
|
Force binary package install
Not exactly as is because of customer names, but below is a sanitized version: SUMMARY = "Binary Stuff" LICENSE = "CLOSED" SRC_URI = "file://binary_installer.tgz \ " do_install() { install -d -m 0755
Not exactly as is because of customer names, but below is a sanitized version: SUMMARY = "Binary Stuff" LICENSE = "CLOSED" SRC_URI = "file://binary_installer.tgz \ " do_install() { install -d -m 0755
|
By
Rudolf J Streif
· #57298
·
|
|
Force binary package install
I have been handed a binary package that I am integrating into a Yocto build. When dnf runs it complains about missing dependencies. These are standard libraries of course but the culprit is the incom
I have been handed a binary package that I am integrating into a Yocto build. When dnf runs it complains about missing dependencies. These are standard libraries of course but the culprit is the incom
|
By
Rudolf J Streif
· #57296
·
|
|
Query regarding yocto build
Hello, Topposting since the problem is in the screenshot. The issue is the naming of the shared object. Linux convention is that a shared object contains the version number e.g. log_wrapper.so.1 and l
Hello, Topposting since the problem is in the screenshot. The issue is the naming of the shared object. Linux convention is that a shared object contains the version number e.g. log_wrapper.so.1 and l
|
By
Rudolf J Streif
· #56446
·
|
|
Custom Image Type
Thanks, Khem. The image class defines IMAGE_CMD. There is not much to it for now: OTA_ROOTFS_MD5 ?= "rootfs.md5" IMAGE_CMD:ota () { build_ota="${WORKDIR}/build-ota" # rootfs md5sum ${IMAGE_ROOTFS} > $
Thanks, Khem. The image class defines IMAGE_CMD. There is not much to it for now: OTA_ROOTFS_MD5 ?= "rootfs.md5" IMAGE_CMD:ota () { build_ota="${WORKDIR}/build-ota" # rootfs md5sum ${IMAGE_ROOTFS} > $
|
By
Rudolf J Streif
· #56330
·
|
|
Custom Image Type
I ran into a problem with a custom image type class. I called the class image_types_ota.bbclass. When I try to use it I am getting these error messages for two predefined image recipes (but only for t
I ran into a problem with a custom image type class. I called the class image_types_ota.bbclass. When I try to use it I am getting these error messages for two predefined image recipes (but only for t
|
By
Rudolf J Streif
· #56327
·
|
|
linux-firmware_20211216
Thanks, Khem. I sent a patch to OE.
Thanks, Khem. I sent a patch to OE.
|
By
Rudolf J Streif
· #55986
·
|
|
linux-firmware_20211216
I got a question about the linux-firmware-bcm4373 package. The link /lib/firmware/brcm/brcmfmac4373-sdio.clm_blob -> ../cypress/cyfmac4373-sdio.clm_blob is packaged into linux-firmware and not into li
I got a question about the linux-firmware-bcm4373 package. The link /lib/firmware/brcm/brcmfmac4373-sdio.clm_blob -> ../cypress/cyfmac4373-sdio.clm_blob is packaged into linux-firmware and not into li
|
By
Rudolf J Streif
· #55982
·
|
|
Honister broken WiFi communication
Hi JH, This would typically mean that you are actually connected to a wifi network but the interface did not receive a DHCP lease for the IP address. the 169.254. is local IPv4 IP address which the in
Hi JH, This would typically mean that you are actually connected to a wifi network but the interface did not receive a DHCP lease for the IP address. the 169.254. is local IPv4 IP address which the in
|
By
Rudolf J Streif
· #55925
·
|
|
Honister broken WiFi communication
Hi JH, Yes, I have, but with Network Manager instead of connman. WiFi works just fine. There are a lot of pieces in the chain and it is not obvious from your description where it is broken. If you run
Hi JH, Yes, I have, but with Network Manager instead of connman. WiFi works just fine. There are a lot of pieces in the chain and it is not obvious from your description where it is broken. If you run
|
By
Rudolf J Streif
· #55900
·
|
|
[WIC] bootimg-partition plugin
A not so well-known feature of the WIC bootimg-partition plugin is that it can install files into different partitions. For that the variable IMAGE_BOOT_FILES has to be defined as one of the following
A not so well-known feature of the WIC bootimg-partition plugin is that it can install files into different partitions. For that the variable IMAGE_BOOT_FILES has to be defined as one of the following
|
By
Rudolf J Streif
· #54800
·
|
|
Inactive service of hello world
#yocto
What does your 'Hello World' service do? Just print 'Hello World' to the console and then exit? If so that would be the reason why it is inactive. Systemd starts it and then it exits. Typically, servi
What does your 'Hello World' service do? Just print 'Hello World' to the console and then exit? If so that would be the reason why it is inactive. Systemd starts it and then it exits. Typically, servi
|
By
Rudolf J Streif
· #54671
·
|
|
Assign IP address at boot time
Not that I know of. Why anyway?
Not that I know of. Why anyway?
|
By
Rudolf J Streif
· #52669
·
|
|
Assign IP address at boot time
Preferred method for local configuration is using /etc/systemd/network. However, the probable reason why it did not work is that the file should be eth0.network. The name of the file(s) do not matter
Preferred method for local configuration is using /etc/systemd/network. However, the probable reason why it did not work is that the file should be eth0.network. The name of the file(s) do not matter
|
By
Rudolf J Streif
· #52657
·
|
|
Assign IP address at boot time
Create the file /etc/systemd/network/eth0.conf: [Match] Name=eth0 [Network] Address=<ip> Gateway=<ip> DNS=<ip> Restart systemd-networkd # systemctl restart systemd-networkd or reboot. :rjs
Create the file /etc/systemd/network/eth0.conf: [Match] Name=eth0 [Network] Address=<ip> Gateway=<ip> DNS=<ip> Restart systemd-networkd # systemctl restart systemd-networkd or reboot. :rjs
|
By
Rudolf J Streif
· #52653
·
|
|
Assign IP address at boot time
What is your startup manager? systemd or SysVInit?
What is your startup manager? systemd or SysVInit?
|
By
Rudolf J Streif
· #52649
·
|
|
Assign IP address at boot time
Hi there, That depends on whether or not you are using a network manager and if so which one. You haven't told us much about your board and it's network interfaces and how you built your system. To st
Hi there, That depends on whether or not you are using a network manager and if so which one. You haven't told us much about your board and it's network interfaces and how you built your system. To st
|
By
Rudolf J Streif
· #52637
·
|