Problem building MIPS image (core-image-minimal)

* Problem building MIPS image (core-image-minimal)
@ 2012-03-29 20:51 Zhouheng Zhuang
  2012-03-30  6:22 ` Khem Raj
  0 siblings, 1 reply; 4+ messages in thread
From: Zhouheng Zhuang @ 2012-03-29 20:51 UTC (permalink / raw)
  To: poky

[-- Attachment #1.1: Type: text/plain, Size: 1473 bytes --]

Hi all,
I am a student, and I just started using Yocto Project, and tried to build
a MIPS image (core-image-minimal) myself, but failed. Can anyone help me on
this issue?

I downloaded Yocto 1.1. After
% source oe-init-build-env
I set configurations in ./build/conf/local.conf with (the file is attached)
------
BB_NUMBER_THREADS = "4"
PARALLEL_MAKE = "-j 3"
MACHINE ??= "qemumips"
DISTRO ?= "poky"
PACKAGE_CLASSES = "package_deb"
EXTRA_IMAGE_FEATURES = "debug-tweaks"
USER_CLASSES ?= "image-mklibs image-prelink"
PATCHRESOLVE = "noop"
CONF_VERSION = "1"
INHERIT += rm_work
------

Then, I ran
% bitbake -k core-image-minimal
and got errors:
------
Errors were encountered while processing:
 /home/zhouheng/poky/build/tmp/deploy/deb/mips/./base-passwd_3.5.22-r9_mips.deb
W: Ignoring Provides line with DepCompareOp for package rtld
W: You may want to run apt-get update to correct these problems
E: Sub-process dpkg returned an error code (1)
ERROR: Function 'do_rootfs' failed (see
/home/zhouheng/poky/build/tmp/work/qemumips-poky-linux/core-image-minimal-1.0-r0/temp/log.do_rootfs.2097
for further information)
-------
I have attached the errorlog with the email, too.
I have tried searching the error, but I haven't figured out why it happens.
Can anyone answer my questions?
I would appreciate it very much if anyone can share their configuration to
successfully build the image.
Thank you very much!

Zhouheng (Philip) Zhuang

[-- Attachment #1.2: Type: text/html, Size: 2020 bytes --]

[-- Attachment #2: local.conf --]
[-- Type: application/octet-stream, Size: 9676 bytes --]

#
# 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 don'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 = "4"
# 
# The second option controls how many processes make should run in parallel when
# running compile tasks:
#
PARALLEL_MAKE = "-j 3"
#
# For a quadcore, 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
# 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 ?= "mpc8315e-rdb"
#MACHINE ?= "routerstationpro"
#
# This sets the default machine to be qemux86 if no other machine is selected:
MACHINE ??= "qemumips"

#
# Where to place downloads
#
# During a first build the system will download many differernt 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 through 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 chages 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 complation 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 exable of a subclass there is a "bleeding" egde policy configuration 
# where many versions are set to the absolute latest code from the upstream 
# source control systems. This is just mentioned here an 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_deb"

#
# 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)
#  "tools-sdk"      - add development tools (gcc, make, pkgconfig etc.)
#  "tools-debug"    - add debugging tools (gdb, strace)
#  "tools-profile"  - add profiling tools (oprofile, exmap, lttng valgrind (x86 only))
#  "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
#  "debug-tweaks"   - make an image for suitable of development
#                     e.g. ssh root access has a blank password
# There are other application targets that can be uses here too, see 
# meta/classes/core-image.bbclass and meta/recipes-core/tasks/task-core.bb 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:
#   - '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 ?= "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, oot test case under sanity suite and 
# toolchain tests
#TEST_SCEN = "sanity bat sanity:boot toolchain"
#
# Because of the QEMU booting slowness issue(see bug #646 and #618), autobuilder
# may suffer a timeout issue when running sanity test. We introduce variable
# TEST_SERIALIZE here to reduce the time on sanity test. It is by default set 
# to 1. This will start image and run cases in the same image without reboot 
# or kill. 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 to use xterm.
#
# Examples of the occasions this may happen are when resolving patches which cannot
# be applied, to use the devshell or the kernel menuconfig
#
# If you do not use (or have installed) xterm you will need to
# uncomment these variables and set them to the terminal you wish to use
# 
# Supported shell prefixes for *_TERMCMD and *_TERMCMDRUN are:
# GNOME, SCREEN, XTERM and KONSOLE
# Note: currently, Konsole support only works for KDE 3.x due to the way
# newer Konsole versions behave
#TERMCMD = "${XTERM_TERMCMD}"
#TERMCMDRUN = "${XTERM_TERMCMDRUN}"
# By default disable interactive patch resolution (tasks will just fail instead):
PATCHRESOLVE = "noop"

#
# 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.
#SSTATE_MIRRORS ?= "\
#file://.* http://someserver.tld/share/sstate/ \n \
#file://.* file:///some/local/dir/sstate/"

# 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"

INHERIT += rm_work

[-- Attachment #3: log.do_rootfs.2097 --]
[-- Type: application/octet-stream, Size: 9425 bytes --]

dpkg-scanpackages: info: Wrote 7 entries to output Packages file.
dpkg-scanpackages: info: Wrote 1270 entries to output Packages file.
dpkg-scanpackages: info: Wrote 313 entries to output Packages file.
dpkg-scanpackages: info: Wrote 7 entries to output Packages file.
Ign file: ./ Release.gpg
Ign file: ./ Release.gpg
Ign file: ./ Release.gpg
Get:1 file: ./ Release [16B]
Get:2 file: ./ Release [12B]
Get:3 file: ./ Release [11B]
Reading package lists...
W: Ignoring Provides line with DepCompareOp for package rtld
W: You may want to run apt-get update to correct these problems
Reading package lists...
Building dependency tree...
The following extra packages will be installed:
  base-files base-passwd busybox busybox-syslog busybox-udhcpc initscripts
  libacl1 libattr1 libc6 libglib-2.0-0 libusb-1.0-0 libusb-compat libz1
  modutils-initscripts netbase pciutils-ids sysvinit sysvinit-inittab
  sysvinit-pidof tinylogin udev udev-cache udev-extraconf
  update-alternatives-cworth update-rc.d usbutils-ids
The following NEW packages will be installed:
  base-files base-passwd busybox busybox-syslog busybox-udhcpc initscripts
  libacl1 libattr1 libc6 libglib-2.0-0 libusb-1.0-0 libusb-compat libz1
  modutils-initscripts netbase pciutils-ids sysvinit sysvinit-inittab
  sysvinit-pidof task-core-boot tinylogin udev udev-cache udev-extraconf
  update-alternatives-cworth update-rc.d usbutils-ids
0 upgraded, 27 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/3702kB of archives.
After this operation, 0B of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  base-files base-passwd update-rc.d libc6 busybox busybox-syslog
  busybox-udhcpc initscripts libattr1 libacl1 libz1 libglib-2.0-0 libusb-1.0-0
  libusb-compat modutils-initscripts netbase pciutils-ids sysvinit-pidof
  sysvinit-inittab sysvinit tinylogin update-alternatives-cworth udev
  task-core-boot udev-cache udev-extraconf usbutils-ids
Authentication warning overridden.
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package base-files.
(Reading database ... \r(Reading database ... 100%\r(Reading database ... 0 files and directories currently installed.)
Unpacking base-files (from .../base-files_3.0.14-r69_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package base-passwd.
Unpacking base-passwd (from .../base-passwd_3.5.22-r9_mips.deb) ...
dpkg (subprocess): unable to execute new pre-installation script (/var/lib/dpkg/tmp.ci/preinst): No such file or directory
dpkg: error processing /home/zhouheng/poky/build/tmp/deploy/deb/mips/./base-passwd_3.5.22-r9_mips.deb (--unpack):
 subprocess new pre-installation script returned error exit status 2
Selecting previously deselected package update-rc.d.
Unpacking update-rc.d (from ..././update-rc.d_0.7-r4_all.deb) ...
warning, in file '/home/zhouheng/poky/build/tmp/work/qemumips-poky-linux/core-image-minimal-1.0-r0/rootfs/var/lib/dpkg/tmp.ci/control' near line 15 package 'libc6':
 `Provides' field, reference to `rtld':
 implicit exact match on version number, suggest using `=' instead
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package libc6.
Unpacking libc6 (from .../libc6_2.13-r15+svnr14157_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package busybox.
Unpacking busybox (from ..././busybox_1.18.5-r2_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package busybox-syslog.
Unpacking busybox-syslog (from .../busybox-syslog_1.18.5-r2_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package busybox-udhcpc.
Unpacking busybox-udhcpc (from .../busybox-udhcpc_1.18.5-r2_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package initscripts.
Unpacking initscripts (from .../initscripts_1.0-r127_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package libattr1.
Unpacking libattr1 (from ..././libattr1_2.4.46-r2_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package libacl1.
Unpacking libacl1 (from ..././libacl1_2.2.51-r2_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package libz1.
Unpacking libz1 (from .../mips/./libz1_1.2.5-r1_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package libglib-2.0-0.
Unpacking libglib-2.0-0 (from .../libglib-2.0-0_2.28.8-r5_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package libusb-1.0-0.
Unpacking libusb-1.0-0 (from .../libusb-1.0-0_1.0.8-r0_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package libusb-compat.
Unpacking libusb-compat (from .../libusb-compat_0.1.3-r0_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package modutils-initscripts.
Unpacking modutils-initscripts (from .../modutils-initscripts_1.0-r6_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package netbase.
Unpacking netbase (from ..././netbase_4.45-r1_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package pciutils-ids.
Unpacking pciutils-ids (from .../pciutils-ids_3.1.7-r2_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package sysvinit-pidof.
Unpacking sysvinit-pidof (from .../sysvinit-pidof_2.88dsf-r5_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package sysvinit-inittab.
Unpacking sysvinit-inittab (from .../sysvinit-inittab_2.88dsf-r6_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package sysvinit.
Unpacking sysvinit (from ..././sysvinit_2.88dsf-r5_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package tinylogin.
Unpacking tinylogin (from ..././tinylogin_1.4-r7_mips.deb) ...
Selecting previously deselected package update-alternatives-cworth.
Unpacking update-alternatives-cworth (from .../update-alternatives-cworth_0.1.8+svnr633-r5_all.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package udev.
Unpacking udev (from .../mips/./udev_164-r6_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package task-core-boot.
Unpacking task-core-boot (from .../task-core-boot_1.0-r8_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package udev-cache.
Unpacking udev-cache (from ..././udev-cache_164-r6_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package udev-extraconf.
Unpacking udev-extraconf (from .../udev-extraconf_0.0-r2_mips.deb) ...
dpkg: warning: overriding problem because --force enabled:
 package architecture (mips) does not match system (amd64)
Selecting previously deselected package usbutils-ids.
Unpacking usbutils-ids (from .../usbutils-ids_0.91-r3_mips.deb) ...
Errors were encountered while processing:
 /home/zhouheng/poky/build/tmp/deploy/deb/mips/./base-passwd_3.5.22-r9_mips.deb
W: Ignoring Provides line with DepCompareOp for package rtld
W: You may want to run apt-get update to correct these problems
E: Sub-process dpkg returned an error code (1)
ERROR: Function 'do_rootfs' failed (see /home/zhouheng/poky/build/tmp/work/qemumips-poky-linux/core-image-minimal-1.0-r0/temp/log.do_rootfs.2097 for further information)

^ permalink raw reply	[flat|nested] 4+ messages in thread