This change clearly breaks builds since subsequent patches
depend on changes this patch removes. Not sure what's going
on here but this change isn't correct.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Thu, 9 Jun 2011 16:30:17 +0000 (17:30 +0100)]
bitbake/event/ast: Add RecipePreFinalise event
One of the implications is we need to register the event handlers before
executing the anonymous python functions. I can't find any issue with making
that change in any existing metadata use cases.
This patch changes the behaviour such that at the time bitbake expands the DEPENDS_z
override, it removes "DEPENDS_z" from the data store. In the above example this would
mean that it wouldn't matter how often you call d.update_data(), you'd always get
"a c" back.
See the bitbake-devel mailing list for further discussion and analysis of the
potential impact of this change.
Mark Hatle [Thu, 9 Jun 2011 17:06:44 +0000 (12:06 -0500)]
pseudo: Fix problem related to realpath
When pseudo is disabled, certain programs that call realpath may not
work properly. This was discovered when using the Qt MOC tool when
certain qmake project features are used.
Paul Eggleton [Wed, 1 Jun 2011 14:37:07 +0000 (15:37 +0100)]
track skipped packages
Add skiplist to cooker that allows access to the list of packages skipped
via SkipPackage (this includes COMPATIBLE_MACHINE, INCOMPATIBLE_LICENSE,
etc.) This can be used to enhance error reporting.
The default list of EXTRA_IMAGE_FEATURES adds alot to the generic non-dev and non-sdk image
so ensure that the sato-sdk and lsb-sdk includes this list by default.
Phil Blundell [Thu, 9 Jun 2011 11:58:43 +0000 (12:58 +0100)]
kexec-tools: don't depend on virtual/kernel
There doesn't appear to be any terribly good reason for kexec-tools to
depend on the kernel. (I verified that kexec-tools is buildable in a
clean TMPDIR without having previously built virtual/kernel.)
Having this dependency in place is a nuisance because it makes it
awkward to put kexec into an initramfs. So, it seems like we would be
better off without.
Paul Eggleton [Wed, 8 Jun 2011 13:20:25 +0000 (14:20 +0100)]
iproute2: update to 2.6.38
Fixes "ip route get" not producing any output (a regression in 2.6.35).
See http://marc.info/?l=linux-netdev&m=129442470405398&w=2 and
http://marc.info/?l=linux-netdev&m=130038222321440&w=2 for a list of
other changes since 2.6.35.
Mark Hatle [Thu, 2 Jun 2011 22:15:26 +0000 (17:15 -0500)]
pseudo: Update pseudo to 1.1.1 version
Update both the core and pseudo_git packages to the latest 1.1.1 verison.
This fixes an issues where the call system() was not wrapped. This could
lead to issues where certain spawned commands broke out of a pseudo-chroot
and created files in the wrong place.
Also the update the 1.0 -> 1.1.1 adds additional capabilities such as
beginning support for MacOS X.
Tom Zanussi [Wed, 8 Jun 2011 13:48:11 +0000 (08:48 -0500)]
initramfs-live-install: comment out allarch inherit to resolve no provider
initramfs-live-install is only compatible with i.86|x86_64 so
shouldn't inherit 'allarch'. This comments it out.
More specifically, commit 52295fa3deef3b0374b99829626d524cefae6001
(Improve handling of 'all' architecture recipes and their interaction
with sstate) sets TARGET_ARCH which due to the COMPATIBLE_HOST setting
in the recipe causes it to be skipped and gives the following error
for any -live build:
NOTE: Resolving any missing task queue dependencies
NOTE: Runtime target 'initramfs-live-install' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['initramfs-live-install']
ERROR: Required build target 'core-image-sato-live' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-sato-live', 'core-ima\
ge-minimal-initramfs', 'initramfs-live-install']
ERROR: Nothing RPROVIDES 'initramfs-live-install'
Chris Larson [Tue, 8 Feb 2011 20:41:36 +0000 (13:41 -0700)]
Shift traceback pre-formatting into LogHandler
It's cleaner to leave it behaving as usual, passing the exception data in the
exc_info attribute of the LogRecord where it normally lies, and then let
LogHandler make it pickleable so it can be sent to the UI.
Chris Larson [Thu, 24 Feb 2011 20:16:43 +0000 (13:16 -0700)]
cooker: use BBHandler.inherit for INHERIT
Ideally we'd avoid direct BBHandler usage, but honestly, to say the whole
bb.parse abstraction is incredibly leaky is an understatement. If we try to
make handle() not reparse classes, things get ugly fairly quickly, as
inherit() calls handle() itself after adding the class to the inherit cache.
This change fixes it so we no longer risk reparsing a class if:
- it's listed in INHERIT multiple times
- it's listed in INHERIT and is 'inherit'ed from a class in INHERIT
Chris Larson [Fri, 6 May 2011 00:43:38 +0000 (17:43 -0700)]
Shift exception formatting into the UI
Now we use bb.exceptions to pass pickleable traceback entries to the UI, and
the UI is free to do whatever it wants to do with this information. By
default, the log formatter for the UIs formats it with bb.exceptions. This
also means that all exceptions should now show 3 lines of context and limit to
5 entries.
Chris Larson [Thu, 5 May 2011 23:55:33 +0000 (16:55 -0700)]
cooker: pass traceback back from parsing thread
Uses bb.exceptions to get a traceback back from the parsing thread to the main
thread, where it is then formatted. Also enables 3 lines of context for the
formatted traceback, and limits the number of entries displayed to 5.
Chris Larson [Sat, 14 May 2011 00:35:37 +0000 (17:35 -0700)]
bb.exceptions: don't show a repr of 'self'
Rather than treating self like an ordinary argument, showing a repr of its
value in the function spec when formatting the traceback entry, now we show
the class name for the method as a part of the function name. Example:
Old: bar(self=<some repr of Fooclass>, f=5)
New: Fooclass.bar(f=5)
Chris Larson [Thu, 5 May 2011 23:53:52 +0000 (16:53 -0700)]
bb.exceptions: add code to create pickleable traceback entries
This lets you get as much useful information as possible from traceback
entries while staying pickleable.
In addition, it has improved traceback formatting. It shows the values of the
arguments for the functions, lines of context from the file for the code, and
has an optional formatter to do things like syntax highlighting for the code
lines.
Richard Purdie [Wed, 8 Jun 2011 08:34:12 +0000 (09:34 +0100)]
bitbake: Cleanup bitbake server init process to be clearer to follow
Create a standard format server class instance with method calls
for each step in the server setup. There should be enough hooks
for each of the different server types.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Liping Ke [Fri, 3 Jun 2011 00:22:40 +0000 (08:22 +0800)]
cache: Implement multiple extra cache fields request support
This patch is to support extra cache. If user needs to request
extra cache fields besides CoreRecipeInfo fields, just add a new
XXXRecipeInfo class definition as Hob Does.
Currently supported Extra RecipeInfo name is an array. We can
support multiple extra cache fields at the same time besides
CoreRecipeInfo which is needed by all clients.
Liping Ke [Fri, 3 Jun 2011 00:21:44 +0000 (08:21 +0800)]
Introduce new param caches_array into Cache impl.
When using hob ui interface, we need extra cache fields.
We will save ui required extra cache fields into a separate
cache file. This patch introduce this caches_array parameter.
It will be used in the extra cache implementation (following patch).
Caches_array at least contains CoreRecipeInfo. If users need extra
cache fields support, such as 'hob', caches_array will contain
more relevant elements such as HobRecipeInfo.
Liping Ke [Fri, 3 Jun 2011 00:20:15 +0000 (08:20 +0800)]
Introduce extra cache class for image creator
Extra RecipeInfo will be all defined in this file. Currently,
Only Hob (Image Creator) Requests some extra fields. So
HobRecipeInfo is defined. It's named HobRecipeInfo because it
is introduced by 'hob'. Users could also introduce other
RecipeInfo or simply use those already defined RecipeInfo.
In the following patch, this newly defined new extra RecipeInfo
will be dynamically loaded and used for loading/saving the extra
cache fields.
Liping Ke [Fri, 3 Jun 2011 00:17:23 +0000 (08:17 +0800)]
cache.py: Refactory Current Cache implementation
This patch is for refactorying current cache implementation, the
main reason is for introducing extra cache fields requests for
image creator as well as other users. The refactory parts include:
Move cache data retrieve methods out of Cache Data Fields
Definition. Since this retrieve methods will be shared for
both CoreRecipeInfo as well as the new introduced extra RecipeInfo
in the following patches.
Chris Larson [Thu, 2 Jun 2011 21:46:13 +0000 (14:46 -0700)]
siggen: don't choke with traceback when data is None
Given we use bb.error, not bb.fatal, here, it seems this was intended to be
non-fatal, yet we'd end up trying to concatenate None. Fix this by setting an
empty task to the empty string, for the purposes of hashing. Also str() the
value we get from the datastore, just in case something other than a string
was stored there.
Bruce Ashfield [Mon, 6 Jun 2011 16:11:36 +0000 (12:11 -0400)]
linux-yocto/meta-yocto: make e1000e structure common [commit: bec3f1e8c]
During work on 1.1 BSPs, some driver options changed. The
result was that the upstream fix b1d670f10e8078485884f0cf7e384d890909aeaa
needs to be available for all BSPs.
These SRCREV updates are the result of making that commit common.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Bruce Ashfield [Mon, 6 Jun 2011 15:30:31 +0000 (11:30 -0400)]
linux-yocto: make e1000e structure common [commit: bec3f1e8c]
During work on 1.1 BSPs, some driver options changed. The
result was that the upstream fix b1d670f10e8078485884f0cf7e384d890909aeaa
needs to be available for all BSPs.
These SRCREV updates are the result of making that commit common.
Bruce Ashfield [Fri, 3 Jun 2011 05:05:30 +0000 (01:05 -0400)]
linux-yocto: update target/meta SRCREVs
This SRCREV update picks up the following changes from the
2.6.37 kernel tree:
- fishriver: create and use a dedicated BSP branch
- fishriver: usbnet fixes, but common to all boards
- standard: update omap baseline match the 2.6.34
upstream merge content
projects / thirdparty / openembedded / openembedded-core-contrib.git / log
