• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 836 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

OMAP-L138: Yocto apache2 build

sharmila d
Prodigy 240 points
Part Number: OMAP-L138
Other Parts Discussed in Thread: OMAPL138

Hi,

I am trying to enable httpd package into my yocto build, steps I followed is as below

1. Added below layer in bblayer.conf file

sources/meta-openembedded/meta-webserver

2. Added below line in local.conf file

IMAGE_INSTALL_append = "apache2"

The yocto build using bitbake core-image-minimal gives below error

WARNING: core-image-minimal-1.0-r0 do_rootfs: busybox.postinst returned 1, marking as unpacked only, configuration required on target.
ERROR: core-image-minimal-1.0-r0 do_rootfs: Postinstall scriptlets of ['busybox'] 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.
Details of the failure are in /home/h440246/Projects/rfid/BSP/tisdk/build/arago-tmp-glibc/work/omapl138_lcdk-oe-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.
ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/h440246/Projects/rfid/BSP/tisdk/build/arago-tmp-glibc/work/omapl138_lcdk-oe-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.2937
ERROR: Task (/home/h440246/Projects/rfid/BSP/tisdk/sources/oe-core/meta/recipes-core/images/core-image-minimal.bb:do_rootfs) failed with exit code '1'

Please provide the solution for the same

With Best Regards,

Sharmila D

  • 0
    TI__Mastermind 30276 points

    Hi,

    We have a video series that you might find helpful here.

    We can't really support customizing the filesystem in this way given the vast array of possibilities. You might find better support in the Yocto community itself.

    In this case, I believe the error warning itself is providing a possible solution (move the package to pkg_postinst_ontarget_${PN} () ) and starting there might be a good path forward.

    I hope this is helpful. Thanks.