angstrom-distribution / meta-angstrom Goto Github PK

ERROR: No recipes available for:
.../meta-angstrom/recipes-core/update-rc.d/update-rc.d_0.7.bbappend

update-rc.d version in thud branch of openembedded-core is 0.8. Please update!

After doing "bitbake meta-toolchain-qt5", then starting again fresh except with a different MACHINE when running setup_environment, "bitbake meta-toolchain-qt5" will fail with stuff like

ERROR: meta-toolchain-qt5-1.0-r0 do_populate_sdk: The recipe meta-toolchain-qt5 is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/windriver/usr1/halfdome/fluke-cda-setup/angstrom-v2017.06-yocto2.3-manifest-fluke-cda/deploy/glibc/sdk/angstrom-glibc-x86_64-armv7at2hf-neon-v2017.06-toolchain.target.manifest
(matched in manifest-fluke-cda-vanquishx86_64-meta-toolchain-qt5.populate_sdk)
/windriver/usr1/halfdome/fluke-cda-setup/angstrom-v2017.06-yocto2.3-manifest-fluke-cda/deploy/glibc/sdk/angstrom-glibc-x86_64-armv7at2hf-neon-v2017.06-toolchain.testdata.json

I suspect this is due to there being no machine specific subdirs under deploy/glibc/sdk/ unlike for example deploy/glibc/images/ which has a subdirectory for each machine. I guess this is due to the setting of SDK_DEPLOY in openembedded-core/meta/classes/populate_sdk_base.bbclass which doesn't include SDKMACHINE in its path.

Breaks due to change in default gcc optimizations, see

u-boot/u-boot@704f3ac

also linux can no longer boot due to being unable to find init in our ubifs root filesystem (we don't know why this happens yet, but it started happening after the update to gcc 6.4).

Can Yocto dunfell branch be prepared?

Sometime in the past few days, libdrm has starting failing to patch (I'm using the sumo branch):

ERROR: libdrm-2.4.96-r0 do_patch: Command Error: 'quilt --quiltrc /home/fmhess/git/fluke-cda-setup/angstrom-v2018.06-sumo-fluke-cda-manifest/build/tmp-angstrom-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/libdrm/2.4.96-r0/recipe-sysroot-native/etc/quiltrc push' exited with 0 Output:
Applying patch installtests.patch
patching file tests/Makefile.am
Hunk #1 FAILED at 45.
1 out of 1 hunk FAILED -- rejects in file tests/Makefile.am
Patch installtests.patch does not apply (enforce with -f)
ERROR: libdrm-2.4.96-r0 do_patch: Function failed: patch_do_patch
ERROR: Logfile of failure stored in: /home/fmhess/git/fluke-cda-setup/angstrom-v2018.06-sumo-fluke-cda-manifest/build/tmp-angstrom-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/libdrm/2.4.96-r0/temp/log.do_patch.9857
ERROR: Task (/home/fmhess/git/fluke-cda-setup/angstrom-v2018.06-sumo-fluke-cda-manifest/layers/meta-angstrom/recipes-tweaks/drm/libdrm_2.4.96.bb:do_patch) failed with exit code '1'

This tweak here forces openssh to use PAM auth for cleartext passwords, and this tweak here causes PAM to allow null passwords through the pam_unix.so auth module.

Unfortunately, out of the box, the Angstrom root user does not have a null password, he has NO password, a subtle difference and the user gets a password authentication issue when trying to log in through ssh with a null password.

This stackexchange question here provides an answer to the problem. (See the update at the bottom of the first answer).

/etc/shadow needs to have the encrypted value for null password saved for the root user. For example:

root:U6aMy0wojraho:13721:0:99999:7:::

When I add this to my /etc/shadow file, I can log in with no problem now through ssh.

For 2014.06 branch PACKAGE_CLASSES is set to " "
and because of this we can not use bitbake package-index to update index of ipk.
In package_manager.py generate_index_files function
we check this variable and because variable is not set we do not call
opkg-make-index.
Also we can not set PACKAGE_CLASSES in local.conf.

WARNING: Layer angstrom-layer should set LAYERSERIES_COMPAT_angstrom-layer in its conf/layer.conf file to list the core layer names it is compatible with.

Is there any reason not to set this variable in the layer.conf?

If not this should be set at least in the Yocto release related branches to avoid these warnings!

Hi,

zstd fetch failed because revision 90ae502 is not in the master branch.

bitbake -c fetch zstd results in

WARNING: zstd-1.3.5+gitAUTOINC+90ae50224d-r0 do_fetch: Failed to fetch URL git://github.com/facebook/zstd.git;protocol=https;branch=master, attempting MIRRORS if available
ERROR: zstd-1.3.5+gitAUTOINC+90ae50224d-r0 do_fetch: Fetcher failure: Unable to find revision 90ae50224d15e8dbcb9fa26b9be096366733db8e in branch master even from upstream
ERROR: zstd-1.3.5+gitAUTOINC+90ae50224d-r0 do_fetch: Fetcher failure for URL: 'git://github.com/facebook/zstd.git;protocol=https;branch=master'. Unable to fetch URL from any source.
ERROR: zstd-1.3.5+gitAUTOINC+90ae50224d-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: ..../build/tmp-angstrom-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/zstd/1.3.5+gitAUTOINC+90ae50224d-r0/temp/log.do_fetch.14680
ERROR: Task (.../layers/meta-angstrom/recipes-tweaks/btrfs-tools/zstd_git.bb:do_fetch) failed with exit code '1'

git -c core.fsyncobjectfiles=0 branch --contains 90ae50224d15e8dbcb9fa26b9be096366733db8e -- list master shows nothing (in the repo https://github.com/facebook/zstd.git) which causes the git fetcher to fail.

Hi,

I am trying to upgrade a layer to support angstrom warrior, but getting the following error:

do_rootfs: No manifest generated from: angstrom-libc-fixup-hack in ....../conf/../layers/meta-angstrom/recipes-angstrom/angstrom/angstrom-libc-fixup-hack.bb

Is there something which needs to be considered regarding this angstrom-libc-fixup-hack?

I am on the github/angstrom-v2019.06-warrior branch for meta-angstrom.

I'm trying to build an image based of console-base-image.bb with a few extra packages that shouldn't interfere and it fails with the following error:

WARNING: headless-1.0-r0 do_rootfs: wpa-supplicant.postinst returned 2, marking as unpacked only, configuration required on target.
WARNING: headless-1.0-r0 do_rootfs: apmd.postinst returned 2, marking as unpacked only, configuration required on target.
ERROR: headless-1.0-r0 do_rootfs: Postinstall scriptlets of ['wpa-supplicant', 'apmd'] have failed. If the intention is to defer them to first boot,
then please place them into pkg_postinst_ontarget_${PN} ().
Deferring to first boot via 'exit 1' is no longer supported.

In addition I've added virtualization to the distro_features.

I can confirm that this image builds successfuly on commit f225c2c.

bitbake of xfce images are failing:
bitbake development-xfce-image ==> ERROR: Nothing RPROVIDES 'gtk-engine-clearlooks'
bitbake xfce-nm-image ==> ERROR: Nothing RPROVIDES 'gdm'

Removing those packages from each image recipe results in further "Nothing RPROVIDES" errors.

Are these recipes still being maintained?
I can build a simple console image but I need a graphical desktop image.

Is it possible to change systemd-qt5-image.bb in the way that it won't require populate_sdk_qt5 class?
The reason is that this causes the bitbake to fail if the QT5 layer is not present even though I don't plan to build a QT5 image. I would like to avoid bringing in a layer if it isn't strictly necessary.

I have created an angstrom-v2020.12-gatesgarth branch with the appropriate modifications.
https://github.com/marioecht/meta-angstrom/tree/angstrom-v2020.12-gatesgarth

Can you create an angstrom-v2020.12-gatesgarth branch based on the angstrom-v2020.06-dunfell branch?

Hello, I have some old Beaglebone Blacks with an old Angstrom distribution (Angstrom v2012.12 Kernel 3.8.13). Although is still the most recent Angstrom image that Beaglebone Black provides on their website.

We are having issues where I2C bus is getting hung, and I have read that there is a recovery mechanism built into Kernels v 3.10+ ), so I am trying to upgrade to a later kernel. If I upgrade to V 3.X, should I be able to drop a replacement into the /boot/ folder? If so, I would want to just upgrade to 3.10+

I've been able to compile a the latest kernel using the yocto-docker docker image, but it is 4.X kernel but I'm assuming I need a 3.X kernel to avoid rebuilding everything else on the system.
I got some strange errors trying to build the 'angstrom-v2013.12-yocto1.5' branch, but mabey that has the 3.X kernel I want.

Any general ideas on the best way to proceed?

when building an image with sumo, during

meta-angstrom/recipes-tweaks/mesa/mesa_18.1.3.bb:do_compile

I get:

make[4]: *** No rule to make target '/usr/share/wayland-protocols/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml', needed by 'drivers/dri2/linux-dmabuf-unstable-v1-client-protocol.h'. Stop.

any suggestions on how to work around?