Hi Vijay,

Note that the yocto-builds list is for automated tests and reports.
The usual list is:
   yocto@lists.yoctoproject.org

See below for my reply once I address the email list confusion.

Michael,
Can you help here or should I contact someone else?
Since this isn't the first time someone thinks that their
build problem emails should be sent to the yocto-builds email
list, could you add a WARNING, say:
   Automated feed for autobuilder results.
   WARNING, ONLY FOR: Automated feed for autobuilder results.
on:
https://www.yoctoproject.org/community/mailing-lists/


Vijay, would have helped you find the right list?
Maybe we need to change:

  • Yocto Project Discussions (yocto): Discussion with Yocto Project developers – start here with general questions.
  • Yocto Project Discussions (yocto): Discussion with Yocto Project developers and users – start here with general questions.

    • On 2/9/20 7:28 AM, ansurivijay.r@hcl.com wrote:
    Hi,

    I have added below lines in local.conf of yocto 2.6.3
    VIRTUAL-RUNTIME_init_manager = " systemd"
    DISTRO_FEATURES_append = " systemd"
    DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
     
    When I building sdk using "bitbake core-image-sato-sdk -c populate_sdk"
    You likely need all of:

    # Select the default init manager
    # use systemd as the default init manager
    DISTRO_FEATURES_append = " systemd"
    DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
    VIRTUAL-RUNTIME_init_manager = "systemd"
    VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"
    KERNEL_FEATURES_append = " cfg/systemd.scc"

    As shown in the WR Linux sample local.conf:

    https://github.com/WindRiver-Labs/wrlinux-x/blob/WRLINUX_10_19_BASE/data/samples/local.conf.sample#L302

    and documented for Yocto distros in geneal here:

    https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#selecting-an-initialization-manager

    ../Randy

     
    I'm facing " file /sbin/telinit conflicts between attempted installs of systemd-1.239-r0.armv7vet2hf_neon and sysvinit-2.88dsf-r14.armv7vet2hf_neon
     
    Can anyone help me fix this?
     
    Thanks &Regards, 
    Vijay

    
    
    
    

    
    
    
    
    -- 
# Randy MacLeod
# Wind River Linux