Pastebin launched a little side project called VERYVIRAL.com, check it out ;-) Want more features on Pastebin? Sign Up, it's FREE!
Guest

Untitled

By: a guest on Aug 21st, 2013  |  syntax: None  |  size: 15.42 KB  |  views: 148  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. $ bitbake core-image-minimal
  2. Parsing recipes: 100% |#########################################| ETA:  00:00:00
  3. Parsing of 927 .bb files complete (0 cached, 927 parsed). 1236 targets, 74 skipped, 7 masked, 0 errors.
  4.  
  5. Build Configuration:
  6. BB_VERSION        = "1.18.0"
  7. BUILD_SYS         = "x86_64-linux"
  8. NATIVELSBSTRING   = "Ubuntu-12.04"
  9. TARGET_SYS        = "arm-poky-linux-gnueabi"
  10. MACHINE           = "beaglebone"
  11. DISTRO            = "poky"
  12. DISTRO_VERSION    = "1.4.2"
  13. TUNE_FEATURES     = "armv7a vfp neon"
  14. TARGET_FPU        = "vfp-neon"
  15. meta              
  16. meta-yocto        = "dylan:d734ab491a30078d43dee5440c03acce2d251425"
  17. meta-ti           = "dylan:ee570b6331bab0bb741193c43723d0da5a5ead34"
  18. meta-yocto-bsp    = "dylan:d734ab491a30078d43dee5440c03acce2d251425"
  19. meta-qt5          = "dylan:047908c2c5bc62283d12f137b3df7a569fb84c68"
  20. meta-epic         = "dylan:d734ab491a30078d43dee5440c03acce2d251425"
  21.  
  22. NOTE: Resolving any missing task queue dependencies
  23. NOTE: Preparing runqueue
  24. NOTE: Executing SetScene Tasks
  25. NOTE: Executing RunQueue Tasks
  26. WARNING: Failed to fetch URL http://www.zlib.net/zlib-1.2.7.tar.bz2, attempting MIRRORS if available
  27. WARNING: Failed to fetch URL ftp://ftp.ossp.org/pkg/lib/uuid/uuid-1.6.2.tar.gz, attempting MIRRORS if available
  28. WARNING: Failed to fetch URL http://www.apache.org/dist/apr/apr-util-1.5.1.tar.gz, attempting MIRRORS if available
  29. WARNING: Failed to fetch URL http://www.apache.org/dist/subversion/subversion-1.7.8.tar.bz2, attempting MIRRORS if available
  30. 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
  31. WARNING: am33x-cm3: No generic license file exists for: TI-BSD in any provider
  32. 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)
  33. 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
  34. Log data follows:
  35. | DEBUG: Executing shell function do_rootfs
  36. | Previous repo file missing: /media/toshiba-usb3/work/poky/build/tmp/deploy/rpm/all/repodata/primary.xml.gz
  37. | Previous repo file missing: /media/toshiba-usb3/work/poky/build/tmp/deploy/rpm/armv7a_vfp_neon/repodata/primary.xml.gz
  38. | Previous repo file missing: /media/toshiba-usb3/work/poky/build/tmp/deploy/rpm/beaglebone/repodata/primary.xml.gz
  39. | Note: configuring RPM platform settings
  40. | Note: configuring RPM system provides
  41. | Note: configuring RPM DB settings
  42. | Note: configuring Smart settings
  43. |
  44. |
  45. |
  46. |
  47. |
  48. |
  49. | Note: adding Smart channel beaglebone (80)
  50. |
  51. |
  52. | Note: adding Smart channel armv7a_vfp_neon (75)
  53. |
  54. |
  55. | Note: adding Smart channel all (10)
  56. |
  57. |
  58. | Note: configuring RPM cross-install scriptlet_wrapper
  59. |
  60. | Updating cache...               ######################################## [100%]
  61. |
  62. | Saving cache...
  63. |
  64. | 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).
  65. | 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)
  66. ERROR: Task 7 (/media/toshiba-usb3/work/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs) failed with exit code '1'
  67. NOTE: Tasks Summary: Attempted 2165 tasks of which 333 didn't need to be rerun and 1 failed.
  68. No currently running tasks (2165 of 2166)
  69.  
  70. Summary: 1 task failed:
  71.   /media/toshiba-usb3/work/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs
  72. Summary: There were 6 WARNING messages shown.
  73. Summary: There was 1 ERROR message shown, returning a non-zero exit code.
  74.  
  75. ~~~~~~~~~~~~~~~~~~~~~~~
  76.   CONFIGURATION FILES
  77. ~~~~~~~~~~~~~~~~~~~~~~~
  78.  
  79. # bblayers.conf
  80.  
  81. # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
  82. # changes incompatibly
  83. LCONF_VERSION = "6"
  84.  
  85. BBPATH = "${TOPDIR}"
  86. BBFILES ?= ""
  87.  
  88. BBLAYERS ?= " \
  89.   /media/toshiba-usb3/work/poky/meta \
  90.   /media/toshiba-usb3/work/poky/meta-yocto \
  91.   /media/toshiba-usb3/work/poky/meta-ti \
  92.   /media/toshiba-usb3/work/poky/meta-yocto-bsp \
  93.   /media/toshiba-usb3/work/poky/meta-qt5 \
  94.   /media/toshiba-usb3/work/poky/meta-epic \
  95.   "
  96. BBLAYERS_NON_REMOVABLE ?= " \
  97.   /media/toshiba-usb3/work/poky/meta \
  98.   /media/toshiba-usb3/work/poky/meta-yocto \
  99.   "
  100.  
  101. # local.conf
  102.  
  103. #
  104. # This file is your local configuration file and is where all local user settings
  105. # are placed. The comments in this file give some guide to the options a new user
  106. # to the system might want to change but pretty much any configuration option can
  107. # be set in this file. More adventurous users can look at local.conf.extended
  108. # which contains other examples of configuration which can be placed in this file
  109. # but new users likely won't need any of them initially.
  110. #
  111. # Lines starting with the '#' character are commented out and in some cases the
  112. # default values are provided as comments to show people example syntax. Enabling
  113. # the option is a question of removing the # character and making any change to the
  114. # variable as required.
  115.  
  116. #
  117. # Parallelism Options
  118. #
  119. # These two options control how much parallelism BitBake should use. The first
  120. # option determines how many tasks bitbake should run in parallel:
  121. #
  122. BB_NUMBER_THREADS = "8"
  123. #
  124. # The second option controls how many processes make should run in parallel when
  125. # running compile tasks:
  126. #
  127. PARALLEL_MAKE = "-j 8"
  128. #
  129. # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
  130. # be appropriate for example.
  131.  
  132. #
  133. # Machine Selection
  134. #
  135. # You need to select a specific machine to target the build with. There are a selection
  136. # of emulated machines available which can boot and run in the QEMU emulator:
  137. #
  138. #MACHINE ?= "qemuarm"
  139. #MACHINE ?= "qemumips"
  140. #MACHINE ?= "qemuppc"
  141. #MACHINE ?= "qemux86"
  142. #MACHINE ?= "qemux86-64"
  143. #
  144. # There are also the following hardware board target machines included for
  145. # demonstration purposes:
  146. #
  147. #MACHINE ?= "atom-pc"
  148. #MACHINE ?= "beagleboard"
  149. MACHINE ?= "beaglebone"
  150. #MACHINE ?= "mpc8315e-rdb"
  151. #MACHINE ?= "routerstationpro"
  152. #
  153. # This sets the default machine to be qemux86 if no other machine is selected:
  154. MACHINE ??= "qemux86"
  155.  
  156. #
  157. # Where to place downloads
  158. #
  159. # During a first build the system will download many different source code tarballs
  160. # from various upstream projects. This can take a while, particularly if your network
  161. # connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
  162. # can preserve this directory to speed up this part of subsequent builds. This directory
  163. # is safe to share between multiple builds on the same machine too.
  164. #
  165. # The default is a downloads directory under TOPDIR which is the build directory.
  166. #
  167. #DL_DIR ?= "${TOPDIR}/downloads"
  168.  
  169. #
  170. # Where to place shared-state files
  171. #
  172. # BitBake has the capability to accelerate builds based on previously built output.
  173. # This is done using "shared state" files which can be thought of as cache objects
  174. # and this option determines where those files are placed.
  175. #
  176. # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
  177. # from these files if no changes were made to the configuration. If changes were made
  178. # to the configuration, only shared state files where the state was still valid would
  179. # be used (done using checksums).
  180. #
  181. # The default is a sstate-cache directory under TOPDIR.
  182. #
  183. #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
  184.  
  185. #
  186. # Where to place the build output
  187. #
  188. # This option specifies where the bulk of the building work should be done and
  189. # where BitBake should place its temporary files and output. Keep in mind that
  190. # this includes the extraction and compilation of many applications and the toolchain
  191. # which can use Gigabytes of hard disk space.
  192. #
  193. # The default is a tmp directory under TOPDIR.
  194. #
  195. #TMPDIR = "${TOPDIR}/tmp"
  196.  
  197. #
  198. # Default policy config
  199. #
  200. # The distribution setting controls which policy settings are used as defaults.
  201. # The default value is fine for general Yocto project use, at least initially.
  202. # Ultimately when creating custom policy, people will likely end up subclassing
  203. # these defaults.
  204. #
  205. DISTRO ?= "poky"
  206. # As an example of a subclass there is a "bleeding" edge policy configuration
  207. # where many versions are set to the absolute latest code from the upstream
  208. # source control systems. This is just mentioned here as an example, its not
  209. # useful to most new users.
  210. # DISTRO ?= "poky-bleeding"
  211.  
  212. #
  213. # Package Management configuration
  214. #
  215. # This variable lists which packaging formats to enable. Multiple package backends
  216. # can be enabled at once and the first item listed in the variable will be used
  217. # to generate the root filesystems.
  218. # Options are:
  219. #  - 'package_deb' for debian style deb files
  220. #  - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
  221. #  - 'package_rpm' for rpm style packages
  222. # E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
  223. # We default to rpm:
  224. PACKAGE_CLASSES ?= "package_rpm"
  225.  
  226. #
  227. # SDK/ADT target architecture
  228. #
  229. # This variable specified the architecture to build SDK/ADT items for and means
  230. # you can build the SDK packages for architectures other than the machine you are
  231. # running the build on (i.e. building i686 packages on an x86_64 host._
  232. # Supported values are i686 and x86_64
  233. #SDKMACHINE ?= "i686"
  234.  
  235. #
  236. # Extra image configuration defaults
  237. #
  238. # The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
  239. # images. Some of these options are added to certain image types automatically. The
  240. # variable can contain the following options:
  241. #  "dbg-pkgs"       - add -dbg packages for all installed packages
  242. #                     (adds symbol information for debugging/profiling)
  243. #  "dev-pkgs"       - add -dev packages for all installed packages
  244. #                     (useful if you want to develop against libs in the image)
  245. #  "ptest-pkgs"     - add -ptest packages for all ptest-enabled packages
  246. #                     (useful if you want to run the package test suites)
  247. #  "tools-sdk"      - add development tools (gcc, make, pkgconfig etc.)
  248. #  "tools-debug"    - add debugging tools (gdb, strace)
  249. #  "eclipse-debug"  - add Eclipse remote debugging support
  250. #  "tools-profile"  - add profiling tools (oprofile, exmap, lttng, valgrind)
  251. #  "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
  252. #  "debug-tweaks"   - make an image suitable for development
  253. #                     e.g. ssh root access has a blank password
  254. # There are other application targets that can be used here too, see
  255. # meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
  256. # We default to enabling the debugging tweaks.
  257. EXTRA_IMAGE_FEATURES = "debug-tweaks"
  258.  
  259. #
  260. # Additional image features
  261. #
  262. # The following is a list of additional classes to use when building images which
  263. # enable extra features. Some available options which can be included in this variable
  264. # are:
  265. #   - 'buildstats' collect build statistics
  266. #   - 'image-mklibs' to reduce shared library files size for an image
  267. #   - 'image-prelink' in order to prelink the filesystem image
  268. #   - 'image-swab' to perform host system intrusion detection
  269. # NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
  270. # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
  271. USER_CLASSES ?= "buildstats image-mklibs image-prelink"
  272.  
  273. #
  274. # Runtime testing of images
  275. #
  276. # The build system can test booting virtual machine images under qemu (an emulator)
  277. # after any root filesystems are created and run tests against those images. To
  278. # enable this uncomment this line
  279. #IMAGETEST = "qemu"
  280. #
  281. # This variable controls which tests are run against virtual images if enabled
  282. # above. The following would enable bat, boot the test case under the sanity suite
  283. # and perform toolchain tests
  284. #TEST_SCEN = "sanity bat sanity:boot toolchain"
  285. #
  286. # Because of the QEMU booting slowness issue (see bug #646 and #618), the
  287. # autobuilder may suffer a timeout issue when running sanity tests. We introduce
  288. # the variable TEST_SERIALIZE here to reduce the time taken by the sanity tests.
  289. # It is set to 1 by default, which will boot the image and run cases in the same
  290. # image without rebooting or killing the machine instance. If it is set to 0, the
  291. # image will be copied and tested for each case, which will take longer but be
  292. # more precise.
  293. #TEST_SERIALIZE = "1"
  294.  
  295. #
  296. # Interactive shell configuration
  297. #
  298. # Under certain circumstances the system may need input from you and to do this it
  299. # can launch an interactive shell. It needs to do this since the build is
  300. # multithreaded and needs to be able to handle the case where more than one parallel
  301. # process may require the user's attention. The default is iterate over the available
  302. # terminal types to find one that works.
  303. #
  304. # Examples of the occasions this may happen are when resolving patches which cannot
  305. # be applied, to use the devshell or the kernel menuconfig
  306. #
  307. # Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
  308. # Note: currently, Konsole support only works for KDE 3.x due to the way
  309. # newer Konsole versions behave
  310. #OE_TERMINAL = "auto"
  311. # By default disable interactive patch resolution (tasks will just fail instead):
  312. PATCHRESOLVE = "noop"
  313.  
  314. #
  315. # Disk Space Monitoring during the build
  316. #
  317. # Monitor the disk space during the build. If there is less that 1GB of space or less
  318. # than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
  319. # shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
  320. # of the build. The reason for this is that running completely out of space can corrupt
  321. # files and damages the build in ways which may not be easily recoverable.
  322. BB_DISKMON_DIRS = "\
  323.     STOPTASKS,${TMPDIR},1G,100K \
  324.     STOPTASKS,${DL_DIR},1G,100K \
  325.     STOPTASKS,${SSTATE_DIR},1G,100K \
  326.     ABORT,${TMPDIR},100M,1K \
  327.     ABORT,${DL_DIR},100M,1K \
  328.     ABORT,${SSTATE_DIR},100M,1K"
  329.  
  330. #
  331. # Shared-state files from other locations
  332. #
  333. # As mentioned above, shared state files are prebuilt cache data objects which can
  334. # used to accelerate build time. This variable can be used to configure the system
  335. # to search other mirror locations for these objects before it builds the data itself.
  336. #
  337. # This can be a filesystem directory, or a remote url such as http or ftp. These
  338. # would contain the sstate-cache results from previous builds (possibly from other
  339. # machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
  340. # cache locations to check for the shared objects.
  341. # NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
  342. # at the end as shown in the examples below. This will be substituted with the
  343. # correct path within the directory structure.
  344. #SSTATE_MIRRORS ?= "\
  345. #file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
  346. #file://.* file:///some/local/dir/sstate/PATH"
  347.  
  348. # CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
  349. # track the version of this file when it was generated. This can safely be ignored if
  350. # this doesn't mean anything to you.
  351. CONF_VERSION = "1"
  352. #IMAGE_INSTALL_append += "hello"
  353. IMAGE_INSTALL_append += " libphidget"
  354. IMAGE_INSTALL_append += " qtbase qtbase-native"
  355. #Required for meta-ti
  356. BBMASK = "meta-ti/recipes-misc"