Am 10.03.2014 14:00, schrieb Markus Eich:


Am Montag, 10. März 2014 12:04:21 UTC+1 schrieb Stefan Herbrechtsmeier:

    Am 10.03.2014 11:20, schrieb Markus Eich:
    > I have a problem baking my ros image with dora. The build process
    > looks good, until the install process starts. The last output was
    >
    >  164:Installing roslaunch
    ######################################## [100%]
    > |                         python-xmlrpc
    > |   libgpg-error0                          rosclean
    > |   libkmod2                               rosconsole
    > |   liblog4cxx10                           roscpp
    > |   liblzma5 roscpp-serialization
    > |   libmount1                              rosgraph
    > |   libmpc3                                rosgraph-msgs
    > |   libmpfr4                               roslaunch
    > |   libncursesw5                           roslib
    > |   libpam                                 rosmaster
    > |   libpam-runtime                         rosout
    > |   libpython2.7-1.0                       rospack
    > |   libreadline6                           rosparam
    > |   libssl1.0.0                            rospy
    > |   libstdc++6                             rostime
    > |   libsystemd-daemon0                     run-postinsts
    > |   libsystemd-id128-0                     shadow
    > |   libsystemd-journal0  shadow-securetty
    > |   libtasn1-6                             std-msgs
    > |   libtinfo5                              systemd
    > |   libtinyxml2.6.2                        systemd-binfmt
    > |   libudev1 systemd-compat-units
    > |   libuuid1 systemd-serialgetty
    > |   libwrap0                               udev
    > |   libx11-6                               udev-hwdb
    > |   libxau6                                udev-utils
    > |   libxcb1 update-alternatives-cworth
    > |   libxdmcp6                              update-rc.d
    > |   libz1  util-linux-agetty
    > |   make util-linux-fsck
    > |   ncurses-terminfo-base  util-linux-mount
    > |   netbase                                xmlrpcpp
    > |
    > | 46.0MB of package files are needed. 119.9MB will be used.
    > |
    > |
    > | Saving cache...
    >
    >
    >
    >  Running intercept scripts:
    > | WARNING: The license listed MIT was not in the licenses collected
    > for packagegroup-core-boot
    > | log_check: Using
    >
    
/home/eich/yocto/gumstix_ros_build/tmp/work/overo-poky-linux-gnueabi/core-image-ros-roscore/1.0-r0/temp/log.do_rootfs.26010

    > as logfile
    > | Logfile is clean
    > | error: package update-rc.d is not installed
    > | WARNING: exit code 1 from a shell command.
    > | ERROR: Function failed: do_rootfs (log file is located at
    >
    
/home/eich/yocto/gumstix_ros_build/tmp/work/overo-poky-linux-gnueabi/core-image-ros-roscore/1.0-r0/temp/log.do_rootfs.26010)

    > ERROR: Task 7
    >
    
(/home/eich/yocto/poky/meta-ros/recipes-core/images/core-image-ros-roscore.bb
    <http://core-image-ros-roscore.bb>,
    > do_rootfs) failed with exit code '1'
    > NOTE: Tasks Summary: Attempted 3030 tasks of which 3027 didn't
    need to
    > be rerun and 1 failed.
    > No currently running tasks (3029 of 3031)
    >
    >
    > It seems that update-rc,d is not installed.
    Please search the log for more details regarding the update-rc.d
    package.

    Have you cherry-pick some patches from the meta master and have
    you try
    a clean build?


Yes. It is a clean build.
Have you manually remove the tmp and sstate directory?


I printed the last log below.
Have you check the detail log: /home/eich/yocto/gumstix_ros_build/tmp/work/overo-poky-linux-gnueabi/core-image-ros-roscore/1.0-r0/temp/log.do_rootfs.26010

I used the repositories given at https://github.com/gumstix/Gumstix-YoctoProject-Repo/blob/dev/default.xml
The meta-ros repository is only tested with the master branch.

I only added meta-ros to the build and added it to the recipies. Tried also bitbake -c clean update-rc.d. after calling again bitbake core-image-ros-roscore the build fails. but the package update-rc.d-0.7-r5.all.rpm is generated.
Have you apply any patches or manually change something?

Reply via email to