| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
enabled
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
| |
Don't specificy dependant clutter version in inc file, this enables the inc
file to be re-used accross Clutter versions.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
|
|
|
|
|
|
| |
the inc file already specifies the gtk+ dependancy
Signed-off-by: Joshua Lock <josh@linux.intel.com>
|
|
|
|
|
|
|
| |
The inc file should be usable across clutter versions, plus this is already
set in the clutter-box2d-1.4_git.bb recipe
Signed-off-by: Joshua Lock <josh@linux.intel.com>
|
|
|
|
| |
Signed-off-by: Joshua Lock <josh@linux.intel.com>
|
|
|
|
|
|
| |
I removed this YP acroynm since we never use it.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
files
The point we need to take the lock is when the rpm files are written into the
deploy rpm directory. Since sstate makes the actual installation of the files,
that is the point we need to take the lock. This also stops the deploy/rpm
directory being accessed for a lock before it exists.
[YOCTO #797]
[YOCTO #925]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
| |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
| |
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
| |
and updated-rc.d explicitly
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
| |
happens before a build completes
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
| |
prelink and other issues are resolved
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
| |
The SRCREV that was pushed to meta isn't even a commit Id
on the meta branch. As a result, the recovery code for bad
SRCREV can't trigger and fix things up due to conflicting
files between the branches.
Updating to the right SRCEV fixes the problem.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
tarball
I added a note in the "Installing the ADT" section (2.1) saying that
if you need to build the ADT tarball you can use
'bitbake adt-installer'. I also changed the location of the
toolchain from '...yocto-0.9' to '...yocto-1.0'. Finally,
I changed the host sub-directory in the toolchain directory
from 'i586' to i686'.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
|
|
|
|
|
|
|
|
| |
Fedora 14 bitbake native note
[BUGID# 931] - I have removed the Note indicating that the user must run
'bitbake make-native' if running Fedora 14.
This is no longer a requirement for YP Release 1.0
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
courtesy Colin Walters
In the Quick Start there is a note indicating that you should run
'bitbake make-native' followed by 'bitbake poky-image-sato' if you
are running Fedora 14 or another distribution that ships with GNU.
Colin Walters submitted a patch that offerred an URL for further
explanation on a Make Bug. The URL is
http://www.mail-archive.com/bug-make@gnu.org/msg06220.html. Rather
than submit Colin's patch verbatim I updated the note to include the
reference with a little different wording.
This extra information submitted by Colin will be very helpful.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
|
|
|
|
|
|
|
| |
* Add Freescale MPC8315E-RDB instructions (based on Wind River README passed
on by Bruce Ashfield)
* Add short info paragraph for RouterStation Pro (to match BeagleBoard)
* Add example for connecting to RouterStation Pro serial console with picocom
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
|
|
|
|
|
|
|
|
| |
* ppc-hack patch is dropped.
* Other patches which were direct backports
or has been merged upstream in 0.14.0 are
also dropped
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
| |
This is needed for the native recipes in meta-efl
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The 2.6.37.5 -stable update is available, so it now becomes
the new base for linux-yocto.
All qemu targets have been built and booted.
Changelog is available via:
git log --pretty=oneline --abbrev-commit v2.6.37.3..v2.6.37.5
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
|
|
|
|
| |
EXTRA_IMAGECMD
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Image generation code in .conf files is hard to read as it needs to be
single line. By moving this to a separate class, multiline functions
can be used instead improving readability. It also declutters
bitbake.conf.
There is no real functional change with this patch but it highlights
the need for improvements in places such as the IMAGE_EXTRA_OPTION
ext* specific variable which makes no sense.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
| |
The base-files version is horribly outdated too.
[YOCTO #924]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
| |
Image type specific size overrides for IMAGE_ROOTFS were being ignored.
Moving the size calculation to after the overide expansion point addresses
this problem.
[YOCTO #928]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
| |
The quoting in get_imagecmds() is hard to read. We can simplify the constuction
a little to make this easier to parse and reduce complexity slightly.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* otherwise strange error like this:
ERROR: Logfile of failure stored in: /OE/shr-core/tmp/work/armv7a-oe-linux-gnueabi/libtool-cross-2.4-r1/temp/log.do_package_write_ipk.25551
Log data follows:
| ERROR: Package already staged (/OE/shr-core/tmp/sstate-control/manifest-nokia900-libtool-cross.deploy-ipk)?!
| ERROR: Function 'sstate_task_postfunc' failed
NOTE: package libtool-cross-2.4-r1: task do_package_write_ipk: Failed
ERROR: Task 11 (/OE/shr-core/openembedded-core/meta/recipes-devtools/libtool/libtool-cross_2.4.bb, do_package_write_ipk) failed with exit code '1'
is shown in this case with package_ipk twice in INHERIT
* Thanks to Richard for fix
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
| |
When 'kernel-misc' is empty do_rootfs will fail when including 'kernel-modules'
The proper fix would be to have a whitelist for the 'kernel-modules' meta-pkg
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Tested-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
|
| |
GCC 4.5 ends up in an ICE when compiling libstdc++ pre compiled header
so we eliminate -feliminate-dwarf2-dups for gcc-runtime
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
| |
* Since bitbake.conf has got rid of -fomit-frame-pointer this
is no longer required
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-fexpensive-optimizations is enabled by default at -O2
-fomit-frame-pointer is enabled at -O2 selectively by gcc depending upon
architecture if debug info is not hurt
-frename-registers - This might have some performance advantage on top
of O2 on architectures which have more registers and registers are left
after scheduling but it affects debuggability quite a bit so as a i
tradeoff we do not use it.
-feliminate-dwarf2-dups - We use this option to reduce the size of debug
information by removing duplicates this is only valid for dwarf2+ and we
use dwarf2 by default
-pipe uses buffers instead of temporary files internally it can speed
up compilation it has has issues with other assemblers but not
with GNU assembler and we use gas.
Separate out debug information related flags into a separate variable
DEBUG_FLAGS so distros can use/notuse them as they like
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
| |
Coreutils can optionally build with libgmp support and for our uses
it's fine to just not build it rather than add the dependency.
Signed-off-by: Tom Rini <tom_rini@mentor.com>
|
|
|
|
| |
Signed-off-by: Tom Rini <tom_rini@mentor.com>
|
|
|
|
| |
Signed-off-by: Tom Rini <tom_rini@mentor.com>
|
|
|
|
|
|
|
|
| |
In mirrors.bbclass we point into /pub but we don't in bitbake.conf.
All uses of KERNELORG_MIRROR look into /pub anyhow, so lets make
use of that.
Signed-off-by: Tom Rini <tom_rini@mentor.com>
|
|
|
|
| |
Signed-off-by: Tom Rini <tom_rini@mentor.com>
|
|
|
|
| |
Signed-off-by: Tom Rini <tom_rini@mentor.com>
|
|
|
|
| |
Signed-off-by: Tom Rini <tom_rini@mentor.com>
|
|
|
|
| |
Signed-off-by: Tom Rini <tom_rini@mentor.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ubuntu has moved eglibc to /usr/lib/${arch}-linux-gnu and
/lib/${arch}-linux-gnu so we need that to be added to glibpth in
Configure.
Currently we set LD=ld in environment for recipes inheriting native
class. This overrides the LD settings in the Makefiles of perl and
it tries to link by calling ld which does not work since its using
-l<x> on commandline and ubuntu linker seems not to look into
the new location for these libraries. Its better to use gcc for linking
here anyway
[With tweak from Tom Rini to use CCLD, not LD]
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
| |
Without using rw the ext3 images boot the kernel but do not spawn the
console at the end
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
There is a nasty bug in qemu 0.14.0 where it over writes device memory
if the default sizes was not specified on commandline. It can be
worked around by this patch.
I also simplified the memory size calculation logic a bit so we append
'M' to QEMU_MEMORY at the very end instead of sed'ing it afterwards
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
| |
bb.mkdirhier should be bb.utils.mkdirhier
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
|
|
| |
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
|
|
| |
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
|
|
|
|
|
| |
While the metadata can and should rely on bb always being available, this
needn't necessarily be the case for imported python modules.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
|
|
|
|
|
|
|
|
|
| |
This attempts to separate the bits we *require* to run bitbake with oe-core
via the wrapper script, and which are independent of the build environment
(PSEUDO_DISABLED, PSEUDO_BUILD, BBFETCH2) from those which are more particular
to poky-init-build-env's way of setting things up (e.g. adding MACHINE to
BB_ENV_EXTRAWHITE, relying on OEROOT, etc). This should make it easier to use
scripts/bitbake with non-standard workflows.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
|
|
| |
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
|
|
|
|
|
|
|
| |
Without this, as a specific example, one has both gtk+-native and gtk+ runtime
providing gdk-pixbuf-loader-*, and you can get bitbake preference conflicts as
a result if you have preferences specified for both gtk+ and gtk+-native for
other things.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
|
|
| |
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|