This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/BEAGLEBK: Beaglebone Black Yocto build warning

Part Number: BEAGLEBK

Tool/software: Linux

Hi,

I had a warning when building images for BBB using am335x-evm machine on Yocto build system:

$bitbake core-image-minimal

...

WARNING: core-image-minimal-1.0-r0 do_rootfs: [log_check] core-image-minimal: found 1 warning message in the logfile:
[log_check] warning: %post(sysvinit-inittab-2.88dsf-r10.am335x_evm) scriptlet failed, exit status 1
...

NOTE: Tasks Summary: Attempted 2297 tasks of which 2250 didn't need to be rerun and all succeeded.

Summary: There was 1 WARNING message shown.

Although this does not really affect my build results. I wonder if anyone has seen the same warning. Question: What this is and if there is a way to get rid of the warning?

Thank you.

  • Hello Matt,

    This warning is caused by your custom service. Please, check your custom service files for typos and discrepancies.

    Best regards,
    Kemal
  • Hi Kemal,

    Sorry about the late reply, I am not sure if I understand you correctly... Do you mean the warning is caused by one of my scripts /etc/init.d? Or you mean other files? Please explain.

    In this case, I built core-image-minimal using the recipes from Poky and meta-ti. My customized Yocto layers and other scripts are not added. So I just want to be sure what are the exact files I should look.

    Thank you.
  • Yes, I mean your scripts in /etc/init.d/. Can you share your exact configs for Poky and meta-ti? I cannot reproduce this warning with the Processor SDK OE layer configs.

  • Hi Kemal,

    Here are my configs. Please let me know if you need other information. Thank you!

    Poky:     git://git.yoctoproject.org/poky tag "rocko-18.0.3"
    meta-ti: git://git.yoctoproject.org/meta-ti tag "ti2018.03"

    $ bitbake -k core-image-minimal
    Loading cache: 100% |######################################################################################| Time: 0:00:00
    Loaded 1499 entries from dependency cache.
    NOTE: Resolving any missing task queue dependencies

    Build Configuration:
    BB_VERSION           = "1.36.0"
    BUILD_SYS            = "x86_64-linux"
    NATIVELSBSTRING      = "universal"
    TARGET_SYS           = "arm-poky-linux-gnueabi"
    MACHINE              = "am335x-evm"
    DISTRO               = "poky"
    DISTRO_VERSION       = "2.4.3"
    TUNE_FEATURES        = "arm armv7a vfp thumb neon callconvention-hard"
    TARGET_FPU           = "hard"
    meta                 
    meta-poky            = "rocko:7e7ee662f5dea4d090293045f7498093322802cc"
    meta-ti              = "rocko:bd9fc96232042ae8d830056dfe7a8811d658a7a4"

    Initialising tasks: 100% |#################################################################################| Time: 0:00:03
    NOTE: Executing SetScene Tasks
    NOTE: Executing RunQueue Tasks
    WARNING: core-image-minimal-1.0-r0 do_rootfs: [log_check] core-image-minimal: found 1 warning message in the logfile:
    [log_check] warning: %post(sysvinit-inittab-2.88dsf-r10.am335x_evm) scriptlet failed, exit status 1

    NOTE: Tasks Summary: Attempted 2493 tasks of which 2276 didn't need to be rerun and all succeeded.

    Summary: There was 1 WARNING message shown.

     

  • Hello Matt,

    Please, try to build from scratch or on another host computer. I've just built with the exact configurations as yours and no such warning appeared.

    Best regards,
    Kemal
  • Hi Kemal,

    Thank you for the message.

    I built from scratch and also tried a different build machine (CentOS rather than Ubuntu). They both have the same warning. However, after digging a bit more, it looks like the warning is caused by the pkg_postinst_${PN} of sysvinit-inittab-2.88dsf.bb. This seems to be addressed in Yocto 2.5: www.yoctoproject.org/.../ref-manual.html
    4.13.6. Miscellaneous Changes
    ...
    "* Using exit 1 to explicitly defer a postinstall script until first boot is now deprecated..."

    So I will just treat it as a warning that can be ignore. Please let me know if you have insights about this.

    Thank you for you help!
  • I found this article which also says that this warnings can be ignored.

  • Yes, thank you for the help!