Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- $ bitbake core-image-minimal
- Parsing recipes: 100% |#########################################| ETA: 00:00:00
- Parsing of 927 .bb files complete (0 cached, 927 parsed). 1236 targets, 74 skipped, 7 masked, 0 errors.
- Build Configuration:
- BB_VERSION = "1.18.0"
- BUILD_SYS = "x86_64-linux"
- NATIVELSBSTRING = "Ubuntu-12.04"
- TARGET_SYS = "arm-poky-linux-gnueabi"
- MACHINE = "beaglebone"
- DISTRO = "poky"
- DISTRO_VERSION = "1.4.2"
- TUNE_FEATURES = "armv7a vfp neon"
- TARGET_FPU = "vfp-neon"
- meta
- meta-yocto = "dylan:d734ab491a30078d43dee5440c03acce2d251425"
- meta-ti = "dylan:ee570b6331bab0bb741193c43723d0da5a5ead34"
- meta-yocto-bsp = "dylan:d734ab491a30078d43dee5440c03acce2d251425"
- meta-qt5 = "dylan:047908c2c5bc62283d12f137b3df7a569fb84c68"
- meta-epic = "dylan:d734ab491a30078d43dee5440c03acce2d251425"
- NOTE: Resolving any missing task queue dependencies
- NOTE: Preparing runqueue
- NOTE: Executing SetScene Tasks
- NOTE: Executing RunQueue Tasks
- WARNING: Failed to fetch URL http://www.zlib.net/zlib-1.2.7.tar.bz2, attempting MIRRORS if available
- WARNING: Failed to fetch URL ftp://ftp.ossp.org/pkg/lib/uuid/uuid-1.6.2.tar.gz, attempting MIRRORS if available
- WARNING: Failed to fetch URL http://www.apache.org/dist/apr/apr-util-1.5.1.tar.gz, attempting MIRRORS if available
- WARNING: Failed to fetch URL http://www.apache.org/dist/subversion/subversion-1.7.8.tar.bz2, attempting MIRRORS if available
- WARNING: Failed to fetch URL http://downloads.sourceforge.net/project/libpng/libpng16/1.6.0/libpng-1.6.0.tar.xz, attempting MIRRORS if available
- WARNING: am33x-cm3: No generic license file exists for: TI-BSD in any provider
- ERROR: Function failed: do_rootfs (see /media/toshiba-usb3/work/poky/build/tmp/work/beaglebone-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.3354 for further information)
- ERROR: Logfile of failure stored in: /media/toshiba-usb3/work/poky/build/tmp/work/beaglebone-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.3354
- Log data follows:
- | DEBUG: Executing shell function do_rootfs
- | Previous repo file missing: /media/toshiba-usb3/work/poky/build/tmp/deploy/rpm/all/repodata/primary.xml.gz
- | Previous repo file missing: /media/toshiba-usb3/work/poky/build/tmp/deploy/rpm/armv7a_vfp_neon/repodata/primary.xml.gz
- | Previous repo file missing: /media/toshiba-usb3/work/poky/build/tmp/deploy/rpm/beaglebone/repodata/primary.xml.gz
- | Note: configuring RPM platform settings
- | Note: configuring RPM system provides
- | Note: configuring RPM DB settings
- | Note: configuring Smart settings
- |
- |
- |
- |
- |
- |
- | Note: adding Smart channel beaglebone (80)
- |
- |
- | Note: adding Smart channel armv7a_vfp_neon (75)
- |
- |
- | Note: adding Smart channel all (10)
- |
- |
- | Note: configuring RPM cross-install scriptlet_wrapper
- |
- | Updating cache... ######################################## [100%]
- |
- | Saving cache...
- |
- | Error: qtbase-native not found in the base feeds (beaglebone armv7a-vfp-neon armv7a-vfp armv7a armv6-vfp armv6 armv5e-vfp armv5e armv5-vfp armv5 armv4 arm noarch any all).
- | ERROR: Function failed: do_rootfs (see /media/toshiba-usb3/work/poky/build/tmp/work/beaglebone-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.3354 for further information)
- ERROR: Task 7 (/media/toshiba-usb3/work/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs) failed with exit code '1'
- NOTE: Tasks Summary: Attempted 2165 tasks of which 333 didn't need to be rerun and 1 failed.
- No currently running tasks (2165 of 2166)
- Summary: 1 task failed:
- /media/toshiba-usb3/work/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs
- Summary: There were 6 WARNING messages shown.
- Summary: There was 1 ERROR message shown, returning a non-zero exit code.
- ~~~~~~~~~~~~~~~~~~~~~~~
- CONFIGURATION FILES
- ~~~~~~~~~~~~~~~~~~~~~~~
- # bblayers.conf
- # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
- # changes incompatibly
- LCONF_VERSION = "6"
- BBPATH = "${TOPDIR}"
- BBFILES ?= ""
- BBLAYERS ?= " \
- /media/toshiba-usb3/work/poky/meta \
- /media/toshiba-usb3/work/poky/meta-yocto \
- /media/toshiba-usb3/work/poky/meta-ti \
- /media/toshiba-usb3/work/poky/meta-yocto-bsp \
- /media/toshiba-usb3/work/poky/meta-qt5 \
- /media/toshiba-usb3/work/poky/meta-epic \
- "
- BBLAYERS_NON_REMOVABLE ?= " \
- /media/toshiba-usb3/work/poky/meta \
- /media/toshiba-usb3/work/poky/meta-yocto \
- "
- # local.conf
- #
- # This file is your local configuration file and is where all local user settings
- # are placed. The comments in this file give some guide to the options a new user
- # to the system might want to change but pretty much any configuration option can
- # be set in this file. More adventurous users can look at local.conf.extended
- # which contains other examples of configuration which can be placed in this file
- # but new users likely won't need any of them initially.
- #
- # Lines starting with the '#' character are commented out and in some cases the
- # default values are provided as comments to show people example syntax. Enabling
- # the option is a question of removing the # character and making any change to the
- # variable as required.
- #
- # Parallelism Options
- #
- # These two options control how much parallelism BitBake should use. The first
- # option determines how many tasks bitbake should run in parallel:
- #
- BB_NUMBER_THREADS = "8"
- #
- # The second option controls how many processes make should run in parallel when
- # running compile tasks:
- #
- PARALLEL_MAKE = "-j 8"
- #
- # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
- # be appropriate for example.
- #
- # Machine Selection
- #
- # You need to select a specific machine to target the build with. There are a selection
- # of emulated machines available which can boot and run in the QEMU emulator:
- #
- #MACHINE ?= "qemuarm"
- #MACHINE ?= "qemumips"
- #MACHINE ?= "qemuppc"
- #MACHINE ?= "qemux86"
- #MACHINE ?= "qemux86-64"
- #
- # There are also the following hardware board target machines included for
- # demonstration purposes:
- #
- #MACHINE ?= "atom-pc"
- #MACHINE ?= "beagleboard"
- MACHINE ?= "beaglebone"
- #MACHINE ?= "mpc8315e-rdb"
- #MACHINE ?= "routerstationpro"
- #
- # This sets the default machine to be qemux86 if no other machine is selected:
- MACHINE ??= "qemux86"
- #
- # Where to place downloads
- #
- # During a first build the system will download many different source code tarballs
- # from various upstream projects. This can take a while, particularly if your network
- # connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
- # can preserve this directory to speed up this part of subsequent builds. This directory
- # is safe to share between multiple builds on the same machine too.
- #
- # The default is a downloads directory under TOPDIR which is the build directory.
- #
- #DL_DIR ?= "${TOPDIR}/downloads"
- #
- # Where to place shared-state files
- #
- # BitBake has the capability to accelerate builds based on previously built output.
- # This is done using "shared state" files which can be thought of as cache objects
- # and this option determines where those files are placed.
- #
- # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
- # from these files if no changes were made to the configuration. If changes were made
- # to the configuration, only shared state files where the state was still valid would
- # be used (done using checksums).
- #
- # The default is a sstate-cache directory under TOPDIR.
- #
- #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
- #
- # Where to place the build output
- #
- # This option specifies where the bulk of the building work should be done and
- # where BitBake should place its temporary files and output. Keep in mind that
- # this includes the extraction and compilation of many applications and the toolchain
- # which can use Gigabytes of hard disk space.
- #
- # The default is a tmp directory under TOPDIR.
- #
- #TMPDIR = "${TOPDIR}/tmp"
- #
- # Default policy config
- #
- # The distribution setting controls which policy settings are used as defaults.
- # The default value is fine for general Yocto project use, at least initially.
- # Ultimately when creating custom policy, people will likely end up subclassing
- # these defaults.
- #
- DISTRO ?= "poky"
- # As an example of a subclass there is a "bleeding" edge policy configuration
- # where many versions are set to the absolute latest code from the upstream
- # source control systems. This is just mentioned here as an example, its not
- # useful to most new users.
- # DISTRO ?= "poky-bleeding"
- #
- # Package Management configuration
- #
- # This variable lists which packaging formats to enable. Multiple package backends
- # can be enabled at once and the first item listed in the variable will be used
- # to generate the root filesystems.
- # Options are:
- # - 'package_deb' for debian style deb files
- # - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
- # - 'package_rpm' for rpm style packages
- # E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
- # We default to rpm:
- PACKAGE_CLASSES ?= "package_rpm"
- #
- # SDK/ADT target architecture
- #
- # This variable specified the architecture to build SDK/ADT items for and means
- # you can build the SDK packages for architectures other than the machine you are
- # running the build on (i.e. building i686 packages on an x86_64 host._
- # Supported values are i686 and x86_64
- #SDKMACHINE ?= "i686"
- #
- # Extra image configuration defaults
- #
- # The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
- # images. Some of these options are added to certain image types automatically. The
- # variable can contain the following options:
- # "dbg-pkgs" - add -dbg packages for all installed packages
- # (adds symbol information for debugging/profiling)
- # "dev-pkgs" - add -dev packages for all installed packages
- # (useful if you want to develop against libs in the image)
- # "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
- # (useful if you want to run the package test suites)
- # "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
- # "tools-debug" - add debugging tools (gdb, strace)
- # "eclipse-debug" - add Eclipse remote debugging support
- # "tools-profile" - add profiling tools (oprofile, exmap, lttng, valgrind)
- # "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
- # "debug-tweaks" - make an image suitable for development
- # e.g. ssh root access has a blank password
- # There are other application targets that can be used here too, see
- # meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
- # We default to enabling the debugging tweaks.
- EXTRA_IMAGE_FEATURES = "debug-tweaks"
- #
- # Additional image features
- #
- # The following is a list of additional classes to use when building images which
- # enable extra features. Some available options which can be included in this variable
- # are:
- # - 'buildstats' collect build statistics
- # - 'image-mklibs' to reduce shared library files size for an image
- # - 'image-prelink' in order to prelink the filesystem image
- # - 'image-swab' to perform host system intrusion detection
- # NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
- # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
- USER_CLASSES ?= "buildstats image-mklibs image-prelink"
- #
- # Runtime testing of images
- #
- # The build system can test booting virtual machine images under qemu (an emulator)
- # after any root filesystems are created and run tests against those images. To
- # enable this uncomment this line
- #IMAGETEST = "qemu"
- #
- # This variable controls which tests are run against virtual images if enabled
- # above. The following would enable bat, boot the test case under the sanity suite
- # and perform toolchain tests
- #TEST_SCEN = "sanity bat sanity:boot toolchain"
- #
- # Because of the QEMU booting slowness issue (see bug #646 and #618), the
- # autobuilder may suffer a timeout issue when running sanity tests. We introduce
- # the variable TEST_SERIALIZE here to reduce the time taken by the sanity tests.
- # It is set to 1 by default, which will boot the image and run cases in the same
- # image without rebooting or killing the machine instance. If it is set to 0, the
- # image will be copied and tested for each case, which will take longer but be
- # more precise.
- #TEST_SERIALIZE = "1"
- #
- # Interactive shell configuration
- #
- # Under certain circumstances the system may need input from you and to do this it
- # can launch an interactive shell. It needs to do this since the build is
- # multithreaded and needs to be able to handle the case where more than one parallel
- # process may require the user's attention. The default is iterate over the available
- # terminal types to find one that works.
- #
- # Examples of the occasions this may happen are when resolving patches which cannot
- # be applied, to use the devshell or the kernel menuconfig
- #
- # Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
- # Note: currently, Konsole support only works for KDE 3.x due to the way
- # newer Konsole versions behave
- #OE_TERMINAL = "auto"
- # By default disable interactive patch resolution (tasks will just fail instead):
- PATCHRESOLVE = "noop"
- #
- # Disk Space Monitoring during the build
- #
- # Monitor the disk space during the build. If there is less that 1GB of space or less
- # than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
- # shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
- # of the build. The reason for this is that running completely out of space can corrupt
- # files and damages the build in ways which may not be easily recoverable.
- BB_DISKMON_DIRS = "\
- STOPTASKS,${TMPDIR},1G,100K \
- STOPTASKS,${DL_DIR},1G,100K \
- STOPTASKS,${SSTATE_DIR},1G,100K \
- ABORT,${TMPDIR},100M,1K \
- ABORT,${DL_DIR},100M,1K \
- ABORT,${SSTATE_DIR},100M,1K"
- #
- # Shared-state files from other locations
- #
- # As mentioned above, shared state files are prebuilt cache data objects which can
- # used to accelerate build time. This variable can be used to configure the system
- # to search other mirror locations for these objects before it builds the data itself.
- #
- # This can be a filesystem directory, or a remote url such as http or ftp. These
- # would contain the sstate-cache results from previous builds (possibly from other
- # machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
- # cache locations to check for the shared objects.
- # NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
- # at the end as shown in the examples below. This will be substituted with the
- # correct path within the directory structure.
- #SSTATE_MIRRORS ?= "\
- #file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
- #file://.* file:///some/local/dir/sstate/PATH"
- # CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
- # track the version of this file when it was generated. This can safely be ignored if
- # this doesn't mean anything to you.
- CONF_VERSION = "1"
- #IMAGE_INSTALL_append += "hello"
- IMAGE_INSTALL_append += " libphidget"
- IMAGE_INSTALL_append += " qtbase qtbase-native"
- #Required for meta-ti
- BBMASK = "meta-ti/recipes-misc"
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement