Re: [yocto] linux-firmware-mt7601u-license missing - all fw installed not only selected
On Thu, Aug 24, 2023 at 06:00:06PM +0200, Konstantin Kletschke wrote:
> meta-insidem2m/recipes-kernel/linux-firmware/linux-firmware_%.bbappend
> containing this:
> FILES:${PN}-mt7662 = "${nonarch_base_libdir}/firmware/mt7662.bin
> ${nonarch_base_libdir}/firmware/mt7662_rom_patch.bin"
No!
I had to do the firmware -> firmware/mediatek move in my own bbappend
too, of course!
I did it but not for both entries so I was mislead thinking that is not
the problem. Noo!
So in my bbappend I changed to
FILES:${PN}-mt7662 = "${nonarch_base_libdir}/firmware/mediatek/mt7662.bin
${nonarch_base_libdir}/firmware/mediatek/mt7662_rom_patch.bin"
also. Problem solved!
The error message was a _bit_ misleading, though!
Regards
Konsti
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60883): https://lists.yoctoproject.org/g/yocto/message/60883
Mute This Topic: https://lists.yoctoproject.org/mt/100938076/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] linux-firmware-mt7601u-license missing - all fw installed not only selected
Today I updated my kirkstone poky (git pull) to today's version, I do
not know when the last time was, though (winter?)...
I have
IMAGE_INSTALL += " \
kernel-module-rtl8812au \
linux-firmware-ralink \
linux-firmware-rtl8168 \
linux-firmware-rtl8188 \
linux-firmware-rtl8192ce \
linux-firmware-rtl8192cu \
linux-firmware-rtl8192su \
linux-firmware-rtl8723 \
linux-firmware-rtl8821 \
linux-firmware-mt7662 \
util-linux-sfdisk \
blspec \
e2fsprogs-resize2fs e2fsprogs-mke2fs xfsprogs \
rauc barebox-utils dt-utils"
in my image config and only those firmware packages got installed.
To create linux-firmware-mt7662 I have a
meta-insidem2m/recipes-kernel/linux-firmware/linux-firmware_%.bbappend
containing this:
PACKAGES =+ "${PN}-mt7662-license ${PN}-mt7662"
LICENSE:${PN}-mt7662 = "Firmware-ralink_a_mediatek_company_firmware"
LICENSE:${PN}-mt7662-license = "Firmware-ralink_a_mediatek_company_firmware"
FILES:${PN}-mt7662-license =
"${nonarch_base_libdir}/firmware/LICENCE.ralink_a_mediatek_company_firmware"
FILES:${PN}-mt7662 = "${nonarch_base_libdir}/firmware/mt7662.bin
${nonarch_base_libdir}/firmware/mt7662_rom_patch.bin"
RDEPENDS:${PN}-mt7662 += "${PN}-mt7662-license"
Worked fine, after today's update I got:
The following packages have unmet dependencies:
linux-firmware-mt7601u : Depends: linux-firmware-mt7601u-license but it is not
installable
E: Unable to correct problems, you have held broken packages.
Why could that be?
I read there was a fix in November:
https://git.yoctoproject.org/poky/commit/meta/recipes-kernel/linux-firmware/linux-firmware_20230625.bb?id=b4b218b0699490765459995f43e945ceea6c32c1
By accident I found out if I rape my bbappend file to look so:
PACKAGES =+ "${PN}-mt7662-license ${PN}-mt7662"
LICENSE:${PN}-mt7662 = "Firmware-ralink_a_mediatek_company_firmware"
LICENSE:${PN}-mt7662-license = "Firmware-ralink_a_mediatek_company_firmware"
FILES:${PN}-mt7662-license =
"${nonarch_base_libdir}/firmware/LICENCE.ralink_a_mediatek_company_firmware"
FILES:${PN}-mt7662 = "${nonarch_base_libdir}/firmware/mt7662.bin
${nonarch_base_libdir}/firmware/mt7662_rom_patch.bin"
RDEPENDS:${PN}-mt7662 += "${PN}-mt7662-license"
LICENSE:${PN}-mt7601u = "Firmware-ralink_a_mediatek_company_firmware"
LICENSE:${PN}-mt7601u-license = "Firmware-ralink_a_mediatek_company_firmware"
FILES:${PN}-mt7601u-license =
"${nonarch_base_libdir}/firmware/LICENCE.ralink_a_mediatek_company_firmware"
FILES:${PN}-mt7601u = "${nonarch_base_libdir}/firmware/mt7662.bin
${nonarch_base_libdir}/firmware/mt7662_rom_patch.bin"
#FILES:${PN}-mt7601u = " \
# ${nonarch_base_libdir}/firmware/mediatek/mt7601u.bin \
#"
RDEPENDS:${PN}-mt7601u += "${PN}-mt7601u-license"
The image gets created successfully, but now it has ALL firmware
packages installed (900MB). The commented out FILES:${PN}-mt7601u is the
original actual recipe part.
What's going on here?
Generally the Problem looks similair to this one:
https://lore.kernel.org/all/20767.1677381945442913...@lists.openembedded.org/T/#md2177072e60f8a737f0db0ef267d75596b34cb89
Was there ever a fix? Despite of that, why is mt7601u failing?
Regards
Konstantin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60882): https://lists.yoctoproject.org/g/yocto/message/60882
Mute This Topic: https://lists.yoctoproject.org/mt/100938076/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Pick up ${PV} dynamically from environment or file or filename
On Sat, Aug 19, 2023 at 12:07:08PM +0200, Alexander Kanavin wrote: > I think the easiest would be to run a shell script prior to starting > bitbake, which would check what jar needs to be used, and write the > SRC_URI with the name and the checksum into a .inc file in the > meta-layer. Then there's a static .bb file that would include the > .inc, and do the installation/packaging. Changes to .inc would then be > under version control and thus reproducible. Thanks for this extermely helpful advice I did not think of. I made a shell script, inspecting the jar files and extracting the version with a regexp from the filename. This is injected as PV into a inc file the latter bb recipe require. This way the inc contains only PV, the bb recipe is fix. The shell script is invoked from the outer build brocess between maven and bitbake. Many thanks! Kind Regards Konstantin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60856): https://lists.yoctoproject.org/g/yocto/message/60856 Mute This Topic: https://lists.yoctoproject.org/mt/100819403/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Pick up ${PV} dynamically from environment or file or filename
On Fri, Aug 18, 2023 at 08:48:46PM +, Darcy Watkins wrote: > Then make use of the GIT AUTOREV facility to fetch from that GIT repo. Interesting idea which I will track in the future, thank you very much! Regards Konstantin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60855): https://lists.yoctoproject.org/g/yocto/message/60855 Mute This Topic: https://lists.yoctoproject.org/mt/100819403/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Pick up ${PV} dynamically from environment or file or filename
On Fri, Aug 18, 2023 at 05:30:50PM +0200, Alexander Kanavin wrote: > You probably need to explain the use case. Why do you want to do > something like that? The yocto build is happening in a gitlab runner thingy. What happens before is that inedependently from the yocto build is that my colleauges are running a maven build which provides java jar files. And I do not know on my side what version they are doing. It could happen even that it alternates between X.Y.Z and X.Y.Z-SNAPSHOT. Then my yocto comes and is picking those jars up and integrates them into the rootfs to be started there by java. They are not processed or executed or compiled, they are copied into the rootfs, symlinkd and integrated into a systemd start. Colleauges maven build: Their git tree. Yocto build: My git tree. > Generally, Yocto cares about build reproducibility, a lot. Thus, > source must be stable, and verified against a checksum of some kind. I learned to love its build reliability because of such stuff too. Konsti -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60825): https://lists.yoctoproject.org/g/yocto/message/60825 Mute This Topic: https://lists.yoctoproject.org/mt/100819403/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Pick up ${PV} dynamically from environment or file or filename
Dear community,
I need to build a recipe which does not now, which actual version the
source file(s) has.
So is it possible, to pick up a version preliminary from either
environment, the content of an existing auxiliary file or from the
structure of the source file itself?
Say, if theres is something like bla-1.23.jar I could look vor a jar
beginning with bla, suffix .jar and construct 1.23 as ${PV} to use in
the SRC_URI. Also possible is to provide a file with version info to be
read or prepare the ENV.
Kind Regards
Konstantin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60823): https://lists.yoctoproject.org/g/yocto/message/60823
Mute This Topic: https://lists.yoctoproject.org/mt/100819403/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Approach for generating two WIC files at once
Meanwhile I tested my proposed approach and it works well... On Mon, Jun 12, 2023 at 11:35:59AM +0200, Alexander Kanavin wrote: > sdcard-base.inc is better, because sdcard-base.bb is a recipe in > itself, but you don't want to build that (or others to get confused > about its purpose). ... but this is a nice hint! Thank you very much! I was bothered colleagues trying to build the base "image" indeed :-) -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60261): https://lists.yoctoproject.org/g/yocto/message/60261 Mute This Topic: https://lists.yoctoproject.org/mt/99383108/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Remove kernel image from IMAGE_BOOT_FILES for WIC boot partition
On Wed, Jun 07, 2023 at 04:58:41PM +0200, Konstantin Kletschke wrote: > Yeah... I end up in scripts/lib/wic/engine.py get_custom_config() which > I must prepare to avoid falling into the "No Kernel..." pitfall, what is > that, an u-boot extlinux config? I am trying to find out... I found out: In the wks file I have to specifiy an existing configfile like this at the bottom (--configfile part): bootloader --append="console=ttyS0,115200" --configfile="directdisk-bootloader-config.cfg" Then I can use my stripped down set of IMAGE_BOOT_FILES without kernel and dtb files. I end up with an unnecessary extlinux/extlinux.conf but this are ~550Bytes and are not avoidable so I can live with that at the moment. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60212): https://lists.yoctoproject.org/g/yocto/message/60212 Mute This Topic: https://lists.yoctoproject.org/mt/99383061/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Remove kernel image from IMAGE_BOOT_FILES for WIC boot partition
On Wed, Jun 07, 2023 at 02:25:15PM +0200, Alexander Kanavin wrote:
> [ak@fedora poky]$ grep -ir "No kernel file found" scripts/
> scripts/lib/wic/plugins/source/bootimg-partition.py:
> raise WicError('No kernel file found')
Yeah... I end up in scripts/lib/wic/engine.py get_custom_config() which
I must prepare to avoid falling into the "No Kernel..." pitfall, what is
that, an u-boot extlinux config? I am trying to find out...
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60211): https://lists.yoctoproject.org/g/yocto/message/60211
Mute This Topic: https://lists.yoctoproject.org/mt/99383061/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Approach for generating two WIC files at once
On Wed, Jun 07, 2023 at 02:15:30PM +0200, Alexander Kanavin wrote: > The easiest is probably to make two image recipes pointing to > different wic files, but sharing everything else via .inc. You mean moving my current meta-insidem2m/recipes-core/images/sdcard.bb to something like meta-insidem2m/recipes-core/images/sdcard_base.bb, creating two new ones like sdcard_d.bb and sdcard_y.bb among the sdcard_base.bb, require the sdcard_base.bb from sdcard_d.bb and sdcard_y.bb and having the latter files overwrite the variable WKS_FILE with different ones? According to preliminary tests the search path for wks files also include meta-insidem2m/recipes-core/images where the sdcard*.bb are located and could ne put right there. This way? I will test, that sounds convenient. Kind Regards Konstantin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60210): https://lists.yoctoproject.org/g/yocto/message/60210 Mute This Topic: https://lists.yoctoproject.org/mt/99383108/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Remove kernel image from IMAGE_BOOT_FILES for WIC boot partition
On Wed, Jun 07, 2023 at 02:16:34PM +0200, Alexander Kanavin wrote: > I don't have a ready solution, but you could grep for the error > message, see where it happens and what can be done to 'not make it I am still searching for this like you suggested :-D -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60206): https://lists.yoctoproject.org/g/yocto/message/60206 Mute This Topic: https://lists.yoctoproject.org/mt/99383061/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Approach for generating two WIC files at once
Can the build system be extended to generate two WIC files for on run, is that possible? I need the same rootfs once with a boot partition part /boot part / and one image only with rootfs part / so I can write sdcards with same rootfs for older systems expecting root on mmcblk0p1 (BBB debian based) and newer ones expecting it on mmcblk0p2 (BBB yocto based). Is that possible, how could one approach such a config? Kind Regards Konstantin -- 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.kletsc...@inside-m2m.de http://www.inside-m2m.de Geschäftsführung: Michael Emmert, Derek Uhlig HRB: 111204, AG Hannover -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60203): https://lists.yoctoproject.org/g/yocto/message/60203 Mute This Topic: https://lists.yoctoproject.org/mt/99383108/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Remove kernel image from IMAGE_BOOT_FILES for WIC boot partition
Hi There, I want to create a WIC image for sdcards which generally works. I use beaglebone-yocto with barebox instead of u-boot. This works with overwriting IMAGE_BOOT_FILES in my meta-insidem2m/recipes-core/images/sdcard.bb: IMAGE_BOOT_FILES="barebox/barebox.bin;barebox.bin barebox-pbl/MLO;MLO zImage am335x-bone.dtb am335x-boneblack.dtb am335x-bonegreen.dtb" I use bootloader spec booting with barebox, so I need only MLO and barbox.bin in the boot partition, so I went: IMAGE_BOOT_FILES="barebox/barebox.bin;barebox.bin barebox-pbl/MLO;MLO" bitbake -e reflects the change: bitbake -e sdcard|grep ^IMAGE_BOOT IMAGE_BOOT_FILES="barebox/barebox.bin;barebox.bin barebox-pbl/MLO;MLO" Then "bitbake sdcard" complains: | NOTE: Installed into sysroot: [] | NOTE: Skipping as already exists in sysroot: ['cross-localedef-native', 'ldconfig-native', 'cdrtools-native', 'qemuwrapper-cross', 'depmodwrapper-cross', 'update-rc.d-native', 'apt-native', 'btrfs-tools-native', 'dosfstools-native', 'dpkg-native', 'e2fsprogs-native', 'gptfdisk-native', 'makedevs-native', 'mtools-native', 'opkg-utils-native', 'pseudo-native', 'squashfs-tools-native', 'syslinux-native', 'parted-native', 'pigz-native', 'bmap-tools-native', 'openssl-native', 'debianutils-native', 'kmod-native', 'systemd-systemctl-native', 'shadow-native', 'qemu-native', 'python3-six-native', 'python3-setuptools-native', 'python3-installer-native', 'python3-native', 'python3-wheel-native', 'coreutils-native', 'zlib-native', 'perl-native', 'gnutls-native', 'lz4-native', 'xz-native', 'xxhash-native', 'db-native', 'cmake-native', 'libgcrypt-native', 'attr-native', 'lzo-native', 'zstd-native', 'libtool-native', 'texinfo-dummy-native', 'readline-native', 'util-linux-native', 'ncurses-native', 'gettext-minimal-native', 'popt-native', 'shared-mime-info-native', 'nasm-native', 'bzip2-native', 'gettext-native', 'glib-2.0-native', 'python3-flit-core-native', 'unzip-native', 'gdbm-native', 'libtirpc-native', 'util-linux-libuuid-native', 'libffi-native', 'libnsl2-native', 'sqlite3-native', 'make-native', 'nettle-native', 'libunistring-native', 'libidn2-native', 'gmp-native', 'curl-native', 'libgpg-error-native', 'libcap-native', 'libcap-ng-native', 'libpcre2-native', 'libxml2-native', 'itstool-native', 'groff-native', 'libpcre-native'] | DEBUG: Python function extend_recipe_sysroot finished | DEBUG: Executing python function set_image_size | DEBUG: 345274.80 = 265596 * 1.30 | DEBUG: 345274.80 = max(345274.80, 65536)[345274.80] + 0 | DEBUG: 345275.00 = int(345274.80) | DEBUG: 345275 = aligned(345275) | DEBUG: returning 345275 | DEBUG: Python function set_image_size finished | DEBUG: Executing shell function do_image_wic | INFO: Creating image(s)... | | ERROR: No kernel file found | | WARNING: exit code 1 from a shell command. How do I remove the requirement for a kernel image? I suppose if I manage to do that, the dtb files are missng too, then. Kind Regards Konstantin -- 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.kletsc...@inside-m2m.de http://www.inside-m2m.de Geschäftsführung: Michael Emmert, Derek Uhlig HRB: 111204, AG Hannover -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#60202): https://lists.yoctoproject.org/g/yocto/message/60202 Mute This Topic: https://lists.yoctoproject.org/mt/99383061/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Setup no IP address for eth0 - systemd
On Mon, Feb 27, 2023 at 01:54:53PM +0200, Anders Montonen wrote: > Check if you also have Networkmanager in your image. My other, rather similair mail was answered with a solution which works fine here in this use case, too: Renaming the file having an additional prefix like "10-" works like a charme. I suspect the number has to be lower than the 80 found in many files in /lib/systemd/network... Kind Regards Konstantin > > -a -- 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.kletsc...@inside-m2m.de http://www.inside-m2m.de Geschäftsführung: Michael Emmert, Derek Uhlig HRB: 111204, AG Hannover -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59309): https://lists.yoctoproject.org/g/yocto/message/59309 Mute This Topic: https://lists.yoctoproject.org/mt/97263146/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Setup a static IP address - systemd
On Mon, Feb 27, 2023 at 01:28:13PM +, Chen, Qi wrote: > I think you're having a higher priority configuration file taking effect. > Check /lib/systemd/network and /run/systemd/network. > Maybe renaming your configuration file to 00-eth0.network would solve the > problem. Yes indeed. I am searching the web for ages for this, my colleauge also found out within a couple of minutes :-| Renaming the file having an additional prefix like "10-" works like a charme. I suspect the number has to be lower than the 80 found in many files in /lib/systemd/network... Thanks for your provided solution, many thanks! Kind Regards Konstantin -- 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.kletsc...@inside-m2m.de http://www.inside-m2m.de Geschäftsführung: Michael Emmert, Derek Uhlig HRB: 111204, AG Hannover -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59308): https://lists.yoctoproject.org/g/yocto/message/59308 Mute This Topic: https://lists.yoctoproject.org/mt/97263112/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Setup no IP address for eth0 - systemd
Dear yocto, community, I have a yocto build running on a Beaglebone Black with systemd enabled. No /etc/init.d, no /etc/network/interfaces. How do I set up no IP Address at all for eth0? The system always does an udhcpc request and uses that. I have systemd-networkd.service loaded active running and tryed the following file in /etc/systemd/network: # cat unmanaged.network [Match] Name = eth0 eth1 eth2 wlan* [Link] Unmanaged = true Kind Regards Konstantin -- 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.kletsc...@inside-m2m.de http://www.inside-m2m.de Geschäftsführung: Michael Emmert, Derek Uhlig HRB: 111204, AG Hannover -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59304): https://lists.yoctoproject.org/g/yocto/message/59304 Mute This Topic: https://lists.yoctoproject.org/mt/97263146/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Setup a static IP address - systemd
Dear yocto, community, I have a yocto build running on a Beaglebone Black with systemd enabled. No /etc/init.d, no /etc/network/interfaces. How do I set up a static IP Address for eth0? The system always does an udhcpc request and uses that. I have systemd-networkd.service loaded active running and tryed the following file in /etc/systemd/network: # cat eth0.network [Match] Name=eth0 [Network] Address=10.2.3.4/24 Gateway=10.2.3.1 DNS=1.1.1.1 Kind Regards Konstantin -- 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.kletsc...@inside-m2m.de http://www.inside-m2m.de Geschäftsführung: Michael Emmert, Derek Uhlig HRB: 111204, AG Hannover -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59303): https://lists.yoctoproject.org/g/yocto/message/59303 Mute This Topic: https://lists.yoctoproject.org/mt/97263112/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Remove kernel image and modules from rootfs
Hi Quentin, On Tue, Jan 03, 2023 at 05:16:09PM +0100, Quentin Schulz wrote: > So, you needed the extra :beaglebone-yocto because the machine configuration > file is parsed after local.conf, therefore since beaglebone-yocto.conf file I was not aware of that, thaught always local.conf is master/last. > > Meanwhile I did something similair, I cloned the machine > > beaglebone-yocto into my tree with thos modifications on top and this > > works too. > Would highly recommend not doing that though, having two configruation files > with the same filename is not nice to your users, because then the order of > inclusion of the layers will decide which file gets picked. I fully agree, this felt strange from the beginning to me and I wondered why I had the luck that ot worked. Indeed my meta-insidem2m layer is ordered last. > Create your own my-beaglebone and in there have: > MACHINEOVERRIDES =. "beaglebone-yocto:" > require conf/machine/beaglebone-yocto.conf > > The first line will allow recipes to use the :beaglebone-yocto OVERRIDE to > match both the original beaglebone-yocto and your my-beaglebone machines. Thanks for this really nice and useful advice! > > CORE_IMAGE_BASE_INSTALL:remove = " packagegroup-core-boot > > packagegroup-base-extended" > > > > Be careful, :remove are final, you cannot re-add its content later on. SO if > you expect users to reuse and extend your image recipe while having :remove > in there, you'll have unhappy users :) You are right, I reread the part in the reference manual and played around with it utilizing the bitbake-getvar you showed to me. I did not really have understood this before. Additionally removeing thos packagegroups probably removes too much from the image. This is what I meanwhile realized - regarding our pretended use case. > What exactly should be different between your images per machines? If we're I have a meta-insidem2m layer which up until now contains all my stuff I need to cope with yocto and requires no modifications to upstream stuff. Additionally it contains one bblayers.conf and local.conf, which are placed in build/config but not modified. This meta-insidem2m has a distro and 3 images configured. The MACHINE is beaglebone-yocto for all the same. The images only differ in the IMAGE_INSTALL set, they are insidem2m-s insidem2m-m and insidem2m-xl. I use the -s as a NFS rootfs for our Bealgsbone Blacks and the -xl variant is the one which gets installed on them for production use. All from one tree w/o further configuration. Now I have a customer's requirement for use to live from a docker container and to utilize a self compiled rootfs in that to have full control over this regarding content and availability. So I thougt I need a insidem2m-xs variant additionally like the already existing ones (processor architecure matches regarding userspace) and now I need insidem2m-s minus kernel, bootloader and init system. And this in a way like making this right and not abusing mechanisms. I learned removing bootloader and kernel requires an additional machine set up _if_ I want to use my local.conf for all images. I have to do this smart (renaming with MACHINEOVERRIDES and require), check. Then I can call "bitabke insidem2m-[s|m|xl]" for my normal images, "MACHINE=my-bbb bitbake insidem2m-xs" for an image w/o kernel and stuff for my docker filesystem. as said, this way local.conf is fixed, everything else also. This is the smartest approach, right? > IMAGE_INSTALL:append:my-beaglebone = " some-my-beaglebone-package" I think, this will become useful also to my use case. I do not yet know, which packages in the end are required in our resulting rootfs. This will become handy... > Finally, it might make more sense to just have multiple image recipes, each > machine having its own image recipe for example. May be this is most importand for me and not covered from my understanding,yet : Can a machine[.conf] have its onw own image[.bb]? In a single meta-xyz layer? This way "bitbake image" would autoselect a proper machine. Kind Regards Konstantin -- 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.kletsc...@inside-m2m.de http://www.inside-m2m.de Geschäftsführung: Michael Emmert, Ingo Haase, Dr. Fred Könemann, Derek Uhlig HRB: 111204, AG Hannover -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#58929): https://lists.yoctoproject.org/g/yocto/message/58929 Mute This Topic: https://lists.yoctoproject.org/mt/95815345/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Remove kernel image and modules from rootfs
On Mon, Jan 02, 2023 at 05:11:35PM +0100, Quentin Schulz wrote:
> > but this is now deprecated for kirkstone and should be done this way:
> >
> > RRECOMMENDS:${KERNEL_PACKAGE_NAME}-base = ""
> >
>
> This makes sense, I'll send a patch updating the documentation to reflect
> this change. I thought we already had discussed about this and someone sent
> a patch but doesn't seem so :/
Thank you :-)
> So I believe you need to add:
> MACHINE_EXTRA_RRECOMMENDS:beaglebone-yocto = ""
> MACHINE_ESSENTIAL_EXTRA_RDEPENDS:remove:beaglebone-yocto = "kernel-image
> kernel-devicetree"
> RRECOMMENDS:${KERNEL_PACKAGE_NAME}-base = ""
> to your local.conf
Dear Quentin, this is correct. It worked this way.
I admit, I was not aware the config snippets I copied need to be
modified for the local.conf in a way the machine name has to be
appended!
> I suggest you create your own machine configuration file which requires
> beaglebone-yocto.conf where you'll be able to set:
> MACHINE_EXTRA_RRECOMMENDS = ""
> MACHINE_ESSENTIAL_EXTRA_RDEPENDS = ""
> RRECOMMENDS:${KERNEL_PACKAGE_NAME}-base = ""
Meanwhile I did something similair, I cloned the machine
beaglebone-yocto into my tree with thos modifications on top and this
works too.
Thanks for your enormous useful hint to the modification needed for
local.conf and the tip to create a machine, inherit beaglebone-yocto and
modify those three variables.
> You can check the value of a variable by running bitbake-getvar -r
> virtual/kernel MACHINE_EXTRA_RRECOMMENDS for example.
Thank you, very useful.
Meanwhile I found out, for my puspose it could be useful to do something
like
CORE_IMAGE_BASE_INSTALL:remove = " packagegroup-core-boot
packagegroup-base-extended"
in the image config, which might be even more useful for my approach to
my use case.
I now can approch my goal with local.conf, an additional machine or the
CORE_IMAGE_BASE_INSTALL modification.
One question though:
can the MACHINE variable only be modified in the local.conf (the
reference manual - glossary does not mention other places)?
If I go with the additional machine approach I am searching for a way to
build different images in my distro based on different machines. Is that
possible?
Kind Regards
Konstantin Kletschke
--
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.kletsc...@inside-m2m.de
http://www.inside-m2m.de
Geschäftsführung: Michael Emmert, Ingo Haase, Dr. Fred Könemann, Derek Uhlig
HRB: 111204, AG Hannover
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58908): https://lists.yoctoproject.org/g/yocto/message/58908
Mute This Topic: https://lists.yoctoproject.org/mt/95815345/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] Remove kernel image and modules from rootfs
Hi,
I am creating a rootfs/bootloader/kernel to run on a beaglebone black
usually and it works great.
So I have in conf/local.conf
MACHINE ?= "beaglebone-yocto"
and an own layer meta-insidem2m which defines some image settings in
recipes-core/images/insidem2m-s.bb among other recipes for packages and
package modification.
Now I wan't to create a rootfs without the kernel image and the kernel
modules to make it as small as possible to use it as a basis to run as a
docker image.
Now I wonder how to instruct bitbake to not put the kernel image (and
modules) into the rootfs.
I read this was done by
RDEPENDS_${KERNEL_PACKAGE_NAME}-base = ""
but this is now deprecated for kirkstone and should be done this way:
RRECOMMENDS:${KERNEL_PACKAGE_NAME}-base = ""
But rootfs always still is equipped with kernel and modules.
I tried all permutations of
#RDEPENDS_kernel-base = ""
#MACHINE_ESSENTIAL_EXTRA_RDEPENDS = ""
#RDEPENDS_kernel-base = ""
#PREFERRED_PROVIDER_virtual/kernel = "linux-dummy"
# Don't include kernels in standard images
##RDEPENDS:kernel-base = ""
#RRECOMMENDS:${KERNEL_PACKAGE_NAME}-base = ""
#MACHINE_EXTRA_RRECOMMENDS = ""
#RDEPENDS_${KERNEL_PACKAGE_NAME}-base = ""
in my conf/local.conf but no avail...
How is this done correctly?
Are there any variables to check I might have (being) set preventing me
to do this? Or is it necessary to split out a new MACHINE, i.e. can this
only be done in an own created machine which has to be split out?
I thought setting such at the bottom of conf/local.conf always "wins".
Kind Regards
Konstantin
--
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.kletsc...@inside-m2m.de
http://www.inside-m2m.de
Geschäftsführung: Michael Emmert, Ingo Haase, Dr. Fred Könemann, Derek Uhlig
HRB: 111204, AG Hannover
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58856): https://lists.yoctoproject.org/g/yocto/message/58856
Mute This Topic: https://lists.yoctoproject.org/mt/95815345/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Dealing with go dependencies in recipes - native docker-compose
On Tue, Oct 18, 2022 at 01:39:34PM -0400, Bruce Ashfield wrote: > root@qemux86-64-c9:~# /usr/lib/docker/cli-plugins/docker-compose version > > Docker Compose version v2.11.2 root@insidem2m:~/docker-nginx-demo# docker compose version Docker Compose version v2.11.2 I did a test run with a small docker-compose.yml for a nginx hello world demo. It worked flawlessly, downloading, installing and starting went really fine. Perfect, nice work! Kind Regards Konstantin -- 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.kletsc...@inside-m2m.de http://www.inside-m2m.de Geschäftsführung: Michael Emmert, Ingo Haase, Dr. Fred Könemann, Derek Uhlig HRB: 111204, AG Hannover -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#58364): https://lists.yoctoproject.org/g/yocto/message/58364 Mute This Topic: https://lists.yoctoproject.org/mt/94264665/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Dealing with go dependencies in recipes - native docker-compose
On Sun, Oct 16, 2022 at 10:28:18PM -0400, Bruce Ashfield wrote: > FYI: Here's the very lightly tested RFC version of the recipe: > > https://git.yoctoproject.org/meta-virtualization/commit/?h=master-next=fa24cfc08b129de5c7ba36099985359cc0228630 Thanks for the kind notification. My stuff is based upon kirkstone, I stuffed the recipe from master-next into my kirkstone build. One package of this new docker-compose is depending upon go-1.19 (kirkstone provides go-1.17) so I pulled in go-1.19 from langdale also into my kirkstone build. The compiling and building works just fine! The recipe(s) for docker-compose look impressive, I would not have expected them being so complex. But they work. Two notes: After installing the package provides /bin/docker-compose. I realized other parties provide this as /usr/lib/docker/cli-plugins/docker-compose which make something like "docker compose version" working. For me this does not harm, only as remark. May be this is intentional. Upon investigating I realized the version reported by docker-compose is "dev" instead of the expected "v2.11.2". Great work, thank you! Regards Konstantin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#58354): https://lists.yoctoproject.org/g/yocto/message/58354 Mute This Topic: https://lists.yoctoproject.org/mt/94264665/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Dealing with go dependencies in recipes - native docker-compose
On Tue, Oct 11, 2022 at 11:23:31PM -0300, Bruce Ashfield wrote: > Adding the missing setuptools does get things working. Oh my, I was still looking for python3-distutils (deprecated, not available) and did not realize I now need setuptools. Thanks for clarifying, however, I investigated the gao approach then... > I actually have a prototype recipe for this that I was working on before > ELCe, but I didn't get it into meta-virtualization yet, as it had a few > rough edges. I suppose, those go recipes look extremly difficult to do. > If you give me a few days, I can post it to the meta-virtualization list, > but I'm on the road right now and don't have access to all my build > machines. Of course I have patience and I am very curious to test this out! Currently I have no urge but in future it will be extremely handy to have the native docker compose approach available. It is a bit smaller then the python approach (if python is only used by this docker-compose, a third disk space is used by native approach). > I also did a presentation at the yocto summit about "modern languages". Opps, interesting. No need to summarize here, I agree. I will dig this up in the internet. Interesting... > You can see the approach that I take for this in the k3s and nerdctl recipes > in meta-virtualization. My new docker-compose recipe is of similar format. As I vaguely mentioned above, those recipes look far more complex than I would have imagined when starting to dig into the go world... astonishing! > If we just bypass the fetcher, offline builds, some of licensing and SBOM > and reproducible builds .. you can have a simple recipe like that as well :) Yea, and I already learned to lovae this reproducibility approach. -- 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.kletsc...@inside-m2m.de http://www.inside-m2m.de Geschäftsführung: Michael Emmert, Ingo Haase, Dr. Fred Könemann, Derek Uhlig HRB: 111204, AG Hannover -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#58332): https://lists.yoctoproject.org/g/yocto/message/58332 Mute This Topic: https://lists.yoctoproject.org/mt/94264665/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Dealing with go dependencies in recipes - native docker-compose
Today I realized, that the docker-compose in the meta-virtualization
layer is the old python3 based one and a native solution is available. I
tried to make a recipe for it to get rid of python3 (no other packages
uses it in our setup) and the current python3-docker-compose is broken:
https://lore.kernel.org/yocto-meta-virtualization/49660ea1-cd22-40db-98c7-c43f38a72...@ieee.org/
I tried to build the native solution proposed in
https://github.com/docker/compose/tree/v2.11.2.
So my current recipe docker-compose_2.11.2.bb looks like this:
LICENSE = "Apache-2.0"
inherit go
inherit go-mod
GO_IMPORT = "github.com/docker/compose"
SRC_URI = "git://${GO_IMPORT};protocol=https;branch=v2"
# v2.11.2
SRCREV = "616777eb4ad4d1101622d6727d9b7adaeb7943bb"
# S = "${WORKDIR}/git"
DEPENDS = "docker-ce"
RDEPENDS:${PN} = "docker-ce-cli"
With this I run into the issue, that go want's to download stuff while
compiling. Which is forbidden and breaks the reliable build proposal.
Totally understandable. Looks similair to this:
dial tcp: lookup proxy.golang.org: Temporary failure in name resolution
I read about a proposal allowing this by adding do_compile[network] =
"1" to meta/classes/go.bb:
https://lore.kernel.org/all/20220228235433.3948994-1-and...@gherzan.com/
Of course, if this works, the reliable build thingy is gone, but while
trying I discovered go loads external stuff, compiles it too.
In my case (I have kirkstone with go-1.17) I run into modules demanding
a go more recent:
ASH[build k8s.io/client-go/applyconfigurations/autoscaling/v2beta2]: "file
containerresourcemetricsource.go Mas4-HIX5lGBEQNTIo58\n"
# github.com/docker/compose/v2/pkg/utils
pkg/utils/slices.go:23:6: missing function body
pkg/utils/slices.go:23:14: syntax error: unexpected [, expecting (
note: module requires Go 1.19
HASH[build k8s.io/client-go/applyconfigurations/certificates/v1beta1]
HASH[build k8s.io/client-go/applyconfigurations/certificates/v1beta1]:
"go1.17.13"
which could be worked around by moving to landsdale release. Which
bothers me, because I too want to keep my build reliable. And I do not
want to mess around outside our meta layer in the distribution!
How do I do this properly?
I see people pulling in each dependency by individual golang.org-x.bb
recipes, how could such a recipe look like?
I read
https://lore.kernel.org/all/8132db85-5881-636e-c091-d84c47efe...@gmail.com/T/
where Mike is not happy with this appraoch either and comes up with a
working recipe I don't get why this could work at all.
What am I missing here where is the missing link I did not get yet?
Also, I am jealous about the buildroot guys sometimes, how do they do
this in a 22 lines makefile including comments:
https://git.busybox.net/buildroot/tree/package/docker-compose/docker-compose.mk
Regards
Konstantin
--
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.kletsc...@inside-m2m.de
http://www.inside-m2m.de
Geschäftsführung: Michael Emmert, Ingo Haase, Dr. Fred Könemann, Derek Uhlig
HRB: 111204, AG Hannover
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58323): https://lists.yoctoproject.org/g/yocto/message/58323
Mute This Topic: https://lists.yoctoproject.org/mt/94264665/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] installed and not shipped files. [installed-vs-shipped]
On Sat, Apr 02, 2022 at 12:13:26PM +0200, Quentin Schulz wrote:
> FILES variables is compatible with glob from Python so that should work but
> that's really the first time I see this, usually it's just the directory or
> dir/*. Learned something new today :)
:-)
> Are you on honister (or master/soon kirkstone) release? If so, it's
> FILES:${PN} and not FILES_${PN}.
That's it!
I wasn't aware of this change, could have searched for another couple of
days!
Thank.
you.
very.
much.
Kind 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.kletsc...@inside-m2m.de
http://www.inside-m2m.de
Geschäftsführung: Michael Emmert, Ingo Haase, Dr. Fred Könemann, Derek Uhlig
HRB: 111204, AG Hannover
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56646): https://lists.yoctoproject.org/g/yocto/message/56646
Mute This Topic: https://lists.yoctoproject.org/mt/90177703/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] installed and not shipped files. [installed-vs-shipped]
I am currently trying to extend the meta-java framework with an
openjdk-18 recipe.
I encounter a problem with the [installed-vs-shipped] QA check which I
can't cope with, I admit.
The autotolls and crosscompile seems to work fine, the install is
overridden with this:
do_install() {
rm -rf ${D}/${JAVA_HOME}
mkdir -p ${D}/${JAVA_HOME}
echo "THIS IS D: "${D} > ${D}/${JAVA_HOME}/THE_D
if [[ "${PN}" = openjre* ]]; then
# cp -rp ${B}/images/jre/* ${D}/${JAVA_HOME}
cp -rp ${B}/jdk/* ${D}${JAVA_HOME}
else
# cp -rp ${B}/images/jdk/* ${D}/${JAVA_HOME}
cp -rp ${B}/jdk/* ${D}${JAVA_HOME}
fi
chown -R root:root ${D}${JAVA_HOME}
#install -m644 ${WORKDIR}/jvm.cfg ${D}${JAVA_HOME}/jre/lib/${JDK_ARCH}/
find ${D}/${JAVA_HOME} -name "*.debuginfo" -exec rm {} \;
}
To verify ${D} there is this "echo [...] THE_D" part in the install step
to look, what's happening.
After this stage I have the following file
/home/konsti/yocto/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/openjdk-18/18+37+gitAUTOINC+0f2113cee7-r0/image/usr/lib/jvm/openjdk-18/THE_D
with contents
THIS IS D:
/home/konsti/yocto/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/openjdk-18/18+37+gitAUTOINC+0f2113cee7-r0/image
What I suppose is ${D} looks like this:
~/yocto/build honister ?1 ❯ ls -la
/home/konsti/yocto/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/openjdk-18/18+37+gitAUTOINC+0f2113cee7-r0/image
total 12
drwxr-xr-x 3 konsti konsti 4096 Apr 1 14:24 .
drwxr-xr-x 17 konsti konsti 4096 Apr 1 14:24 ..
drwxr-xr-x 3 konsti konsti 4096 Apr 1 14:24 usr
${JAVA_HOME} expands to /usr/lib/jvm/openjdk-18:
~/yocto/build honister ?1 ❯ ls -la
/home/konsti/yocto/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/openjdk-18/18+37+gitAUTOINC+0f2113cee7-r0/image/usr/lib/jvm/openjdk-18/
total 36
drwxr-xr-x 7 konsti konsti 4096 Apr 1 14:24 .
drwxr-xr-x 3 konsti konsti 4096 Apr 1 14:24 ..
-rw-r--r-- 3 konsti konsti 128 Apr 1 14:24 THE_D
drwxr-xr-x 2 konsti konsti 4096 Apr 1 14:24 bin
drwxr-xr-x 5 konsti konsti 4096 Apr 1 14:22 conf
drwxr-xr-x 3 konsti konsti 4096 Apr 1 14:22 include
drwxr-xr-x 5 konsti konsti 4096 Apr 1 14:24 lib
drwxr-xr-x 69 konsti konsti 4096 Apr 1 14:23 modules
-rw-r--r-- 3 konsti konsti 129 Apr 1 14:22 release
So accordingly the recipe continues with extending the FILES to do
packaging this way:
FILES_${PN} += "\
${JAVA_HOME}/bin/[a-z]* \
${JAVA_HOME}/lib/[a-z]* \
${JAVA_HOME}/modules \
${JAVA_HOME}/release \
${JAVA_HOME}/conf \
${JAVA_HOME}/include \
${JAVA_HOME}/THE_D \
"
When I do "bitbake -e openjdk-18 |grep FILES_openjdk-18=" I get this:
FILES_openjdk-18=" /usr/lib/jvm/openjdk-18/bin/[a-z]*
/usr/lib/jvm/openjdk-18/lib/[a-z]* /usr/lib/jvm/openjdk-18/modules
/usr/lib/jvm/openjdk-18/release /usr/lib/jvm/openjdk-18/conf
/usr/lib/jvm/openjdk-18/include /usr/lib/jvm/openjdk-18/THE_D "
When bitbake tries to package, I get this error:
ERROR: openjdk-18-18+37+gitAUTOINC+0f2113cee7-r0 do_package: QA Issue:
openjdk-18: Files/directories were installed but not shipped in any package:
/usr/lib/jvm/openjdk-18/release
/usr/lib/jvm/openjdk-18/THE_D
/usr/lib/jvm/openjdk-18/conf
/usr/lib/jvm/openjdk-18/include
/usr/lib/jvm/openjdk-18/lib/libj2gss.so
[...]
/usr/lib/jvm/openjdk-18/modules/jdk.internal.le/jdk/internal/org/jline/keymap/BindingReader.class
/usr/lib/jvm/openjdk-18/modules/jdk.internal.le/jdk/internal/org/jline/keymap/KeyMap.class
Please set FILES such that these items are packaged. Alternatively if they are
unneeded, avoid installing them or delete them within do_install.
openjdk-18: 28751 installed and not shipped files. [installed-vs-shipped]
ERROR: openjdk-18-18+37+gitAUTOINC+0f2113cee7-r0 do_package: Fatal QA errors
found, failing task.
ERROR: Logfile of failure stored in:
/home/konsti/yocto/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/openjdk-18/18+37+gitAUTOINC+0f2113cee7-r0/temp/log.do_package.3424506
ERROR: Task
(/home/konsti/yocto/meta-insidem2m/recipes-core/openjdk/openjdk-18_18+37.bb:do_package)
failed with exit code '1'
Well, I am pretty shure the FILES_${PN} refers relative to ${D}, where
is my stupid misunderstanding?
Side-Quest: In do install the destination is referred as
${D}${JAVA_HOME}. Why does this not need to be ${D}/${JAVA_HOME}?
Kind Regards
Konstantin Kletschke
--
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.kletsc...@inside-m2m.de
http://www.inside-m2m.de
Geschäftsführung: Michael Emmert, Ingo Haase, Dr. Fred Könemann, Derek Uhlig
HRB: 111204, AG Hannover
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56612): https://lists.yoctoproject.
[yocto] Pass environment to kernel make
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.kletsc...@inside-m2m.de http://www.inside-m2m.de Geschäftsführung: Michael Emmert, Ingo Haase, Dr. Fred Könemann, Derek Uhlig HRB: 111204, AG Hannover -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56166): https://lists.yoctoproject.org/g/yocto/message/56166 Mute This Topic: https://lists.yoctoproject.org/mt/89090024/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Not all config fragments applied
I added a custom layer and under recipes-kernel I try to apply kernel config
fragments:
└[ *~* ]> cat poky/meta-insidem2m/recipes-kernel/linux/linux-yocto_5.10.bbappend
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI += "\
file://wext.cfg \
file://at24.cfg \
file://leds.cfg \
file://usb.cfg \
file://keyspan.cfg \
file://00-leds.patch \
"
Works fine. So far.
Today i added wext.cfg and the file itself is found among the other in
poky/build/tmp/work/beaglebone_yocto-poky-linux-gnueabi/linux-yocto/5.10.12+gitAUTOINC+67e74d52f2_cdca787784-r0
but its content is not applied to the .config.
wext.cfg has this content:
└[ *~* ]> cat poky/meta-insidem2m/recipes-kernel/linux/linux-yocto/wext.cfg
CONFIG_WIRELESS_EXT=y
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
I don't see a dependency missing,
if I test the so far .config in two fresh linux trees, do make menuconfig in
both and do this again in one tree and add then CONFIG_WIRELESS_EXT in one tree
with make menucinfug I get the following diff:
└[ *~* ]> diff -Nur a/.config b/.config
*--- a/.config 2021-04-26 15:16:24.425877434 +0200*
*+++ b/.config 2021-04-26 15:15:42.797926593 +0200*
@@ -1222,7 +1222,9 @@
# CONFIG_AF_KCM is not set
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
-# CONFIG_WIRELESS_EXT is not set
+CONFIG_WIRELESS_EXT=y
+CONFIG_WEXT_CORE=y
+CONFIG_WEXT_PROC=y
# CONFIG_WEXT_SPY is not set
# CONFIG_WEXT_PRIV is not set
CONFIG_CFG80211=y
Does somebody have a hint what's going on here? As said the other fragments are
properly applied...
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53266): https://lists.yoctoproject.org/g/yocto/message/53266
Mute This Topic: https://lists.yoctoproject.org/mt/82377531/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] BeagleBone Black wig image does not boot
Hi all, I successfully compile/create a target image and binaries for a BeagleBone Black: MACHINE ?= "beaglebone-yocto" The resulting wic image does not boot, when I write it to a sdcard nor when I write it directly into the internal /dev/mmcblk0. There is no console output despite of some capital "C" sometimes (the internal boot loader-loader failing to find u-boot?). The image looks rather healthy, though: fdisk p output: Disk core-image-base-beaglebone-yocto-20210331083925.rootfs.wic: 1 GiB, 1098599424 bytes, 2145702 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xa63a46ea Device Boot Start End SectorsSize Id Type core-image-base-beaglebone-yocto-20210331083925.rootfs.wic1 *8 49065 49058 24M c W95 FAT32 (LBA) core-image-base-beaglebone-yocto-20210331083925.rootfs.wic2 49072 2145701 2096630 1023.8M 83 Linux ls -la of the mounted first boot partition: insidem2m@konsti ~/Y $ ls -la /mnt total 8648 drwxr-xr-x 3 root root 16384 Jan 1 1970 . drwxr-xr-x 17 root root4096 Mar 4 12:06 .. -rwxr-xr-x 1 root root 107940 Apr 6 2011 MLO -rwxr-xr-x 1 root root 59303 Apr 6 2011 am335x-bone.dtb -rwxr-xr-x 1 root root 62629 Apr 6 2011 am335x-boneblack.dtb -rwxr-xr-x 1 root root 59567 Apr 6 2011 am335x-bonegreen.dtb drwxr-xr-x 2 root root2048 Apr 6 2011 extlinux -rwxr-xr-x 1 root root 892736 Apr 6 2011 u-boot.img -rwxr-xr-x 1 root root 7645608 Apr 6 2011 zImage The strange thing is, when I prepare a sdcard (or the internal flash!) with partitions manually, format manually and copy the same kernel and u-boot binaries into the first and the rootfs into the second partition, the system works fine! Since the complete Image layout looks fine to me, what could be the culprit of that? Kind Regards Konsti -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52993): https://lists.yoctoproject.org/g/yocto/message/52993 Mute This Topic: https://lists.yoctoproject.org/mt/81771131/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
