* problem in building console-iamge
@ 2010-01-21 14:31 saleh usman
2010-01-21 15:18 ` Andrea Adami
0 siblings, 1 reply; 3+ messages in thread
From: saleh usman @ 2010-01-21 14:31 UTC (permalink / raw)
To: Openembedded Discussion
[-- Attachment #1: Type: text/plain, Size: 1905 bytes --]
I've built console-image without adding the following lines in local.conf
file and it has been built successfully.Now when I've added these lines it is
giving error.Attached is local.conf file.
ANGSTROM_EXTRA_INSTALL = " screen oprofile ossie-fm-from-file "
BBFILES = "/oe/org.openembedded.dev/packages/*/*.bb /oe/ossie_collection/packages/*/*.bb"
BBFILE_COLLECTIONS = "upstream ossie"
BBFILE_PATTERN_upstream = "^/oe/org.openembedded.dev/packages"
BBFILE_PRIORITY_upstream = "5"
BBFILE_PATTERN_ossie = "^/oe/ossie/packages"
BBFILE_PRIORITY_ossie = "10"
Where oe is directory in which I've placed openembedded.
Terminal window is showing following error.
[saleh@localhost ~]$ bitbake console-image
NOTE: Out of date cache found, rebuilding...
NOTE: Handling BitBake files: \ (0014/0014) [100 %]
NOTE: Parsing finished. 0 cached, 14 parsed, 0 skipped, 0 masked.
ERROR: Nothing PROVIDES 'console-image'
I've set the BBPATH environment variable as following.
export BBPATH=/oe/build:/oe/openembedded:/oe/ossie_collection
where oe is directory in which I've placed openembedded and ossie_collection directory.
Actuall I've dowloaded files from
http://trac.geekisp.com/opensdr/browser/OE/ossie_collection and placed
them in a directory named ossie_collection.
How this line will be interpretted
/oe/org.openembedded.dev/packages/*/*.bb
weather it is a link from which bitbake will download files or it
is pointing to a directory which should be already existing in oe
directory
I
Plz help me in moving forward.
Saleh
_________________________________________________________________
Keep your friends updated—even when you’re not signed in.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_5:092010
[-- Attachment #2: local.conf --]
[-- Type: application/octet-stream, Size: 8196 bytes --]
#
# OpenEmbedded local configuration file (sample)
#
# Please visit the Wiki at http://openembedded.org/ for more info.
#
#
# Be SURE to read this file in its entirety and the GettingStarted page on the
# wiki before proceeding.
#
# Once you have done that, remove the line at the end of this
# file and build away.
#
# WARNING: lines starting with a space (' ') will result in parse failures.
# Remove '# ' from commented lines to activate them.
#
# NOTE: Do NOT use $HOME in your paths, BitBake does NOT expand ~ for you. If you
# must have paths relative to your homedir use ${HOME} (note the {}'s there
# you MUST have them for the variable expansion to be done by BitBake). Your
# paths should all be absolute paths (They should all start with a / after
# expansion. Stuff like starting with ${HOME} or ${TOPDIR} is ok).
# Use this to specify where BitBake should place the downloaded sources into
DL_DIR = "/oe/openembedded/sources"
# Delete the line below. Then specify which .bb files to consider for
# your build. Typically this will be something like BBFILES = "/path/to/openembedded/recipes/*/*.bb"
BBFILES = "/oe/openembedded/recipes/*/*.bb"
# Use the BBMASK below to instruct BitBake to _NOT_ consider some .bb files
# This is a regulary expression, so be sure to get your parenthesis balanced.
BBMASK = ""
# Uncomment this if you want to use a prebuilt toolchain. You will need to
# provide packages for toolchain and additional libraries yourself. You also
# have to set PATH in your environment to make sure BitBake finds additional binaries.
# ASSUME_PROVIDED += "virtual/${TARGET_PREFIX}gcc virtual/libc"
# Uncomment this if you're building for an arch that uses emulated locale
# generation under qemu (mainly arm glibc) and have an external gcc 3.x compiler
# that OE recognises. This will mean the gcc-native build is skipped, speeding
# builds up.
# ASSUME_PROVIDED += "gcc3-native"
# Uncomment this if you are building Linux 2.4 Embedix kernels.
# i.e. openzaurus-sa-2.4.18 and openzaurus-pxa-2.4.18 - and don't forget
# to rename the binaries as instructed in the Wiki.
# Most users do not need this anymore thankfully!
# ASSUME_PROVIDED += "virtual/arm-linux-gcc-2.95"
# Select between multiple alternative providers, if more than one is eligible.
PREFERRED_PROVIDERS = "virtual/qte:qte virtual/libqpe:libqpe-opie"
PREFERRED_PROVIDERS += " virtual/libsdl:libsdl-x11"
PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc-initial:gcc-cross-initial"
PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc-intermediate:gcc-cross-intermediate"
PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc:gcc-cross"
PREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}g++:gcc-cross"
# Uncomment this to specify where BitBake should create its temporary files.
# Note that a full build of everything in OpenEmbedded will take GigaBytes of hard
# disk space, so make sure to free enough space. The default TMPDIR is
# <build directory>/tmp
# Don't use symlinks in in the path to avoid problems
#TMPDIR = /oe/build
# Uncomment this to specify a machine to build for. See the conf directory
# for machines currently known to OpenEmbedded. This will automatically take care
# of TARGET_ARCH
MACHINE = "dm6446-evm"
# Use this to specify the target architecture. Note that this is only
# needed when building for a machine not known to OpenEmbedded. Better use
# the MACHINE attribute (see above)
#TARGET_ARCH = "arm"
# Use this to specify the target operating system. The default is "linux",
# for a normal linux system with glibc. Set this to "linux-uclibc" if you want
# to build a uclibc based system.
# Normally the DISTRO of your choosing will take care of this
# TARGET_OS = "linux"
# TARGET_OS = "linux-uclibc"
# Uncomment this to select a distribution policy. See the conf directory
# for distributions currently known to OpenEmbedded.
# Although it no longer contain version number in the (file-)name
# openzaurus-unstable is a so called "versioned" distro, i.e. they
# explicitely select specific versions of various packages.
# Stay away from unversioned distros unless you really know what you are doing
DISTRO = "angstrom-2008.1"
# So far, angstrom.conf sets ENABLE_BINARY_LOCALE_GENERATION
# to generate binary locale packages at build time using qemu-native and
# thereby guarantee i18n support on all devices. If your build breaks on
# qemu-native consider disabling ENABLE_BINARY_LOCALE_GENERATION (note that
# this breaks i18n on devices with less than 128MB RAM) or installing
# a working third-party qemu (e.g. provided by your distribution) and
# adding qemu-native to ASSUME_PROVIDED. Caveat emptor, since third-party
# qemus lack patches needed to work with various OE targets.
# ENABLE_BINARY_LOCALE_GENERATION = "0"
# ASSUME_PROVIDED += "qemu-native"
# If ENABLE_BINARY_LOCALE_GENERATION is set to "1", you can limit locales
# generated to the list provided by GLIBC_GENERATE_LOCALES. This is huge
# time-savior for developmental builds. Format: list of locale.encoding pairs
# with spaces as separators.
# GLIBC_GENERATE_LOCALES = "en_US.UTF-8 en_GB.UTF-8 de_DE.UTF-8"
# Uncomment this to select a particular major kernel version if the MACHINE setting
# supports more than one major kernel version. Currently this is suported by the
# following MACHINE types: poodle, tosa and simpad.
# MACHINE_KERNEL_VERSION = "2.6"
# Uncomment one of these to build packages during the build process.
# This is done automatically if you set DISTRO (see above)
# INHERIT = "package_ipk"
# INHERIT = "package_tar"
# Add the required image file system types below. Valid are
# jffs2, tar(.gz|bz2), cpio(.gz), cramfs, ext2(.gz), ext3(.gz)
# squashfs, squashfs-lzma
IMAGE_FSTYPES = "jffs2 tar"
# Uncomment this if you want to keep the temporary rootfs
# diretory, this can be useful during development.
# (Note that this rootfs is NOT usuable as NFS export.)
# IMAGE_KEEPROOTFS = "1"
# Uncomment this to disable the parse cache (not recommended).
# CACHE = ""
# Uncomment this if you want BitBake to emit debugging output
# BBDEBUG = "yes"
# Uncomment these two if you want BitBake to build images useful for debugging.
# Note that INHIBIT_PACKAGE_STRIP needs a package format to be defined.
# Also note that OE now produces -dbg packages which contain debugging symbols.
# DEBUG_BUILD = "1"
# INHIBIT_PACKAGE_STRIP = "1"
# Uncomment these to build a package such that you can use gprof to profile it.
# NOTE: This will only work with 'linux' targets, not
# 'linux-uclibc', as uClibc doesn't provide the necessary
# object files. Also, don't build glibc itself with these
# flags, or it'll fail to build.
#
# PROFILE_OPTIMIZATION = "-pg"
# SELECTED_OPTIMIZATION = "${PROFILE_OPTIMIZATION}"
# LDFLAGS =+ "-pg"
# Uncomment this to enable parallel make.
# This allows make to spawn mutliple processes to take advantage of multiple
# processors. Useful on SMP machines. This may break some packages - we're
# in the process of marking these so let us know if you find any.
# PARALLEL_MAKE = "-j 4"
# Uncomment to run multiple bitbake threads in parallel.
# Bitbake can do multiple jobs in parallel: Its a good idea make use of
# all available resources: e.g. to download sources while some other
# piece of software is compiled.
# BB_NUMBER_THREADS = "2"
# Uncomment this if you want BitBake to emit the log if a build fails.
BBINCLUDELOGS = "yes"
# Specifies a location to search for pre-generated tarballs when fetching
# a cvs:// URI. Outcomment this, if you always want to pull directly from CVS.
#CVS_TARBALL_STASH = ""
# Uncomment this if you want to install shared libraries directly under their SONAME,
# rather than installing as the full version and symlinking to the SONAME.
# PACKAGE_SNAP_LIB_SYMLINKS = "1"
# EDIT THIS FILE and then remove the line below before using!
ANGSTROM_EXTRA_INSTALL = " screen oprofile ossie-fm-from-file "
BBFILES = "/oe/org.openembedded.dev/packages/*/*.bb /oe/ossie_collection/packages/*/*.bb"
BBFILE_COLLECTIONS = "upstream ossie"
BBFILE_PATTERN_upstream = "^/oe/org.openembedded.dev/packages"
BBFILE_PRIORITY_upstream = "5"
BBFILE_PATTERN_ossie = "^/oe/ossie/packages"
BBFILE_PRIORITY_ossie = "10"
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: problem in building console-iamge
2010-01-21 14:31 problem in building console-iamge saleh usman
@ 2010-01-21 15:18 ` Andrea Adami
2010-01-21 15:41 ` Philip Balister
0 siblings, 1 reply; 3+ messages in thread
From: Andrea Adami @ 2010-01-21 15:18 UTC (permalink / raw)
To: openembedded-devel
>>BBFILES = "/oe/org.openembedded.dev/packages/*/*.bb /oe/ossie_collection/packages/*/*.bb"
This seems wrong
>>NOTE: Handling BitBake files: \ (0014/0014) [100 %]
In fact you get just 14 items...
Dunno about ossie, but in openembedded we moved from 'packages' to 'recipes'.
Regards
Andrea
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: problem in building console-iamge
2010-01-21 15:18 ` Andrea Adami
@ 2010-01-21 15:41 ` Philip Balister
0 siblings, 0 replies; 3+ messages in thread
From: Philip Balister @ 2010-01-21 15:41 UTC (permalink / raw)
To: openembedded-devel
On 01/21/2010 10:18 AM, Andrea Adami wrote:
>>> BBFILES = "/oe/org.openembedded.dev/packages/*/*.bb /oe/ossie_collection/packages/*/*.bb"
> This seems wrong
>
>>> NOTE: Handling BitBake files: \ (0014/0014) [100 %]
> In fact you get just 14 items...
>
> Dunno about ossie, but in openembedded we moved from 'packages' to 'recipes'.
Urg, good point, I need to fix that web page :)
Philip
>
> Regards
>
> Andrea
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-01-21 15:43 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-01-21 14:31 problem in building console-iamge saleh usman
2010-01-21 15:18 ` Andrea Adami
2010-01-21 15:41 ` Philip Balister
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox