[oe] [meta-initramfs][PATCH 0/6 v2] Run dracut from rootfs

[Khem Raj]

On Tue, Feb 19, 2019 at 10:46 AM Böszörményi Zoltán <zboszor at pr.hu> wrote:
>
> 2019. 02. 19. 17:51 keltezéssel, Khem Raj írta:
> > On Tue, Feb 19, 2019 at 12:43 AM Böszörményi Zoltán <zboszor at pr.hu> wrote:
> >>
> >> 2019. 02. 19. 8:14 keltezéssel, Khem Raj írta:
> >>> more here
> >>>
> >>> NOTE: Started PRServer with DBfile: /mnt/a/yoe/cache/prserv.sqlite3,
> >>> IP: 127.0.0.1, PORT: 45089, PID: 43331
> >>> Parsing recipes...done.
> >>> Parsing of 3233 .bb files complete (0 cached, 3233 parsed). 4441
> >>> targets, 574 skipped, 0 masked, 0 errors.
> >>> NOTE: Resolving any missing task queue dependencies
> >>> ERROR: Nothing RPROVIDES 'plymouth-initrd' (but
> >>> /mnt/a/yoe/sources/meta-openembedded/meta-initramfs/recipes-devtools/dracut/dracut_git.bb
> >>> RDEPENDS on or otherwise requires it)
> >>> NOTE: Runtime target 'plymouth-initrd' is unbuildable, removing...
> >>
> >> Questions:
> >>
> >> 1. What removes "initrd" from the plymouth PACKAGECONFIG for this setup?
> >>
> >
> >
> >
> >> 2. Can a PACKAGECONFIG string of one recipe queried from another recipe?
> >>      E.g. would bb.utils.contains("PACKAGECONFIG_pn-plymouth", ...) work
> >>      from the dracut recipe if the variable does not exit at a layer level
> >>      but only in a plymouth bbappend?
> >
> > I dont think so, but you can tie it into a DISTRO_CONFIG
>
> You mean, instead of checking for PACKAGECONFIG, plymouth and dracut
> should both test for "dracut" in DISTRO_FEATURES, right?
>
> Or should they check for the other one?
>
> Or both should check for both strings?
>
> Which one is preferred?

just a DISTRO_FEATURE should be enough.

>
> >
> >>
> >> 3. Would moving plymouth-initrd from RDEPENDS to RRECOMMENDS in the dracut
> >>      recipe solve this problem? If not, why? intel-microcode is also in
> >>      RRECOMMENDS, but it's mentioned in the errors below. Why?
> >
> > recommendations still have to be built, for feeds.
>
> Okay, so I need a function to check for an x86(_64) target
> and conditionally include intel-microcode.

I guess that would work, you might use overrides to add conditional
dependency based on architecture.

>
> >
> >>
> >>> Missing or unbuildable dependency chain was: ['plymouth-initrd']
> >>> NOTE: Runtime target 'dracut' is unbuildable, removing...
> >>> Missing or unbuildable dependency chain was: ['dracut', 'plymouth-initrd']
> >>> NOTE: Runtime target 'dracut-dev' is unbuildable, removing...
> >>> Missing or unbuildable dependency chain was: ['dracut-dev', 'plymouth-initrd']
> >>> ERROR: Nothing RPROVIDES 'intel-microcode' (but
> >>> /mnt/a/yoe/sources/meta-openembedded/meta-initramfs/recipes-devtools/dracut/dracut_git.bb
> >>> RDEPENDS on or otherwise requires it)
> >>> NOTE: Runtime target 'intel-microcode' is unbuildable, removing...
> >>> Missing or unbuildable dependency chain was: ['intel-microcode']
> >>>
> >>> Build Configuration:
> >>> BB_VERSION           = "1.40.0"
> >>> BUILD_SYS            = "x86_64-linux"
> >>> NATIVELSBSTRING      = "arch"
> >>> TARGET_SYS           = "arm-yoe-linux-musleabi"
> >>> MACHINE              = "sama5d27-som1-ek-sd"
> >>> DISTRO               = "yoe-musl-sysvinit-wayland"
> >>> DISTRO_VERSION       = "2.6"
> >>> TUNE_FEATURES        = "arm vfp cortexa5 neon vfpv4 thumb callconvention-hard"
> >>> TARGET_FPU           = "hard"
> >>> meta-yoe             = "yoe/mut:f14a20d6c6b23391aa0b8636d0b20752e074830a"
> >>> meta-96boards        = "HEAD:6e8a11ea878698742e83832ef06df2c11604c338"
> >>> meta-atmel           = "HEAD:ac803d348433d7755803f5429c7c40f4883a5ae4"
> >>> meta-freescale       = "HEAD:2e83203ebd8439a45bc7a931ace6871e6b238658"
> >>> meta-freescale-3rdparty = "HEAD:8b38f230d4d7cd6c283d75c17eddfbe51eca90a5"
> >>> meta-odroid
> >>> meta-odroid-extras   = "yoe/mut:688ff9c5f549f072af204ee64d5ad3ee18b9e47f"
> >>> meta-qcom            = "yoe/mut:f708a3a9b6a61cd4d83a32dec4532453a127b54a"
> >>> meta-raspberrypi     = "HEAD:6305aa7b693fb3423bd40921144666dadd7185b8"
> >>> meta-riscv           = "yoe/mut:2ec848f8f37ea3c0d3538f32a59133294a9234cc"
> >>> meta-ti              = "yoe/mut:04c4fef39d62396ea855b5f086a969269d740562"
> >>> meta-browser         = "yoe/mut:974e22e9ffcba92a1d7e7aab90a6cb88b9c3e77f"
> >>> meta-qt5             = "HEAD:fb71293f257c6fd02ccc06765a96dbf11d4569a0"
> >>> meta-rust            = "HEAD:f4517aaba8026b44576c6407adf0175663d5a7b4"
> >>> meta-filesystems
> >>> meta-gnome
> >>> meta-initramfs
> >>> meta-multimedia
> >>> meta-networking
> >>> meta-oe
> >>> meta-perl
> >>> meta-python
> >>> meta-webserver
> >>> meta-xfce            = "yoe/mut:6adca5007190518de21ff406a141944c9d601588"
> >>> meta                 = "yoe/mut:36242003ab8ff7e5dd93206ff672d92f9dbbd6e4"
> >>> meta-clang           = "master:e96a34778c238692769c488fbe0d7781f0b929ce"
> >>> workspace            = "kraj/master:8a94ccf193a33feb1546455fd190ac880ff66fb2"
> >>>
> >>> On Mon, Feb 18, 2019 at 11:01 PM Khem Raj <raj.khem at gmail.com> wrote:
> >>>>
> >>>> https://errors.yoctoproject.org/Errors/Details/228793/
> >>>>
> >>>> On Mon, Feb 18, 2019 at 2:47 AM Böszörményi Zoltán <zboszor at pr.hu> wrote:
> >>>>>
> >>>>> This patchset adds the necessary pieces to create the initramfs
> >>>>> with dracut during do_rootfs.
> >>>>>
> >>>>> The 6th patch references a GitHub branch for which a pull request
> >>>>> was made against dracut. See https://github.com/dracutdevs/dracut/pull/535
> >>>>>
> >>>>> Best regards,
> >>>>> Zoltán Böszörményi
> >>>>>
> >>>>>
> >>>
> >>
> >
>