Re: Adding systemd to yocto


Scott Murray
 

On Tue, 3 May 2022, Edgar Mobile wrote:

Apparently, this is not enough:

bitbake core-image-weston
/usr/lib/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
return f(*args, **kwds)
Loading cache: 100% |############################################| Time: 0:00:00
Loaded 1472 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'pam' (but /media/user/SSD1TB/yoctoqemu/poky/meta/recipes-graphics/images/core-image-weston.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'pam' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['pam']
ERROR: Required build target 'core-image-weston' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-weston', 'pam']

These are my current additions to local.conf:

INIT_MANAGER="systemd"
CORE_IMAGE_EXTRA_INSTALL += " mesa-demos gdb"
IMAGE_INSTALL:append += " pam"
^ This line what is causing your error, remove it. With pam in
DISTRO_FEATURES the required packages will get pulled in via dependencies.

DISTRO_FEATURES:append = " systemd wayland pam x11"
If you specify INIT_MANAGER = "systemd", then you do not need to add
systemd here.

VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""
Similarly, with INIT_MANAGER = "systemd" these 3 lines are not required.
If you look at meta/conf/distro/include/init-manager-systemd.inc you can
see what INIT_MANAGER = "systemd" tweaks.

IMAGE_ROOTFS_EXTRA_SPACE = "38048576"
[snip]

Scott

Join yocto@lists.yoctoproject.org to automatically receive all group messages.