Take Valentin's recipes because he's not working on the
project anymore.
(From meta-yocto rev: de6064a222e59df32e8052e7f11eebc106bba862)
Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If a configuration fragment was missing, the previous error output
was not clear about the error:
| [INFO] doing kernel configme
| [INFO] Configuring target/machine combo: "standard/atom-pc"
| [INFO] collecting configs in ./meta/meta-series
| ERROR: could not sanitize configuration fragments
| errors are logged in ... linux/meta/cfg/standard/atom-pc/config.log
but we know the name of the missing fragment and can improve the error
message to be this:
| [ERROR] kernel configuration fragment fragment 'virto.cfg' cannot be found
| ERROR. A meta series could not be created for branch yocto/standard/common-pc/atom-pc
| ERROR. Could not locate meta series for atom-pc
| ERROR. Could not apply patches for atom-pc.
| Patch failures can be resolved in the devshell (bitbake -c devshell linux-yocto)
[YOCTO #3473]
(From OE-Core rev: 46cc0d0a2f1486bf541c1a1b11075de3da396cc2)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Having a meta branch is not strictly required by the tools (and
recipes like linux-yocto-custom do not have meta branches), but the
comments in the kernel-yocto.bbclass could lead someone to think that
it was required.
This commit clearifies the comment to the following:
# We can fix up the kernel repository even if it wasn't a bare clone.
# If KMETA is defined, the branch must exist, but a machine branch
# can be missing since it may be created later by the tools.
[YOCTO #3422]
(From OE-Core rev: 421a2e2523a8f2c461479a1c0d44908cc1eaca6b)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bumping the meta SRCREV to import the following fix:
[
uprobes: reinstate config options for 'uprobe' feature
commit 17ec51adfff (meta: cleanup invalid/obselete 3.4 CONFIG options)
removed the uprobes config options, this restores them.
]
(From OE-Core rev: 8c637986e063fcb087babecfc0192f96d3981515)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The recent tools updates in master exposed a typo that has existed
in the 3.0 kernel meta data and that breaks the build for boards still
using the 3.0 kernel.
Bumping the meta SRCREV to pickup the following fix:
[
commit fa9b8c24e84bb9d75d08d197c84c50ce4f99c424
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Wed Nov 21 09:24:46 2012 -0500
meta: fix typo in virtio.scc
virtio.scc was referring to an invalid/incorrect virto.cfg. Fixing
this typo fixes the build for boards still using the 3.0 kernel.
]
(From OE-Core rev: b16d72a749ac73a2bd0434f36102c00f6c476bc1)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
At runtime virtual/ providers make *no* sense at all. They also break debian
packaging since the "/" character is not allowed in debian package names.
This patch removes this runtime provider selection code since it is not
workable and breaks builds.
(From OE-Core rev: 887059e9c0082cb4e7fa8b5d7c9646207acd62a6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This driver has been superceeded by a dri omap driver. This driver
no longer builds against current versions of the xserver. If someone
wants to do the work to resurect it, that is fine but until that happens
there is no point in keeping broken code in the tree which won't even
compile. It can be easily brought back from git history.
(From OE-Core rev: 75858ad8cb19ee24f2c418515cb9d2b649a4de46)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream uses AC_CHECK_FILE to find dri.h, but that errors out when
cross-compiling. Until oe-core 1b0d9cb1801a8eb68c82dfcda5a1da420ac8dd83 this
wasn't a problem because we patched AC_CHECK_FILE to always pass, which was a
nasty hack.
Patch configure.ac to use pkg-config like it should, and not AC_CHECK_FILE.
(From OE-Core rev: a7fe0d17c50d9b38ce33fe39e677da349d1d358c)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are a lot of improvements in Hob
and a critical fix to bitbake affecting
Build Appliance, so the poky revision
is upped to include these changes.
(From OE-Core rev: 654d5816f8ff696d42d72cfb881d5e51330a79b6)
Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Build Appliance needs to have for the builder
user a password set. However, the useradd.bbclass
requires the last parameter to be the user's group
name. Previously, the password was the last
parameter to useradd command.
Fixed using the right order for parameters.
(From OE-Core rev: 29f2ae0305b9a3db9632a8fe078fedc88f89a9ad)
Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This reverts commit d6e5ceafcaef06b8a3f9acc2aa826a40a016f913 since
the value is clearly still being used in local file urls that are
only hit at do_unpack time.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In a small number of cases we need to have ${PN} in FILESPATH rather
than ${BPN}. Rather than hurt readability for all other recipes,
set FILESPATH in these recipes so we can prune the default.
(From OE-Core rev: d61ef6ce86abe5b484a2a2602982f4ded54b3f9a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was needed when do_package for target recipes was target specific
however since it now isn't we can remove these stale references.
(From OE-Core rev: 1c54d8c3639659bc8cf8fa2786a1aa9ed785b723)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Calling split on the same expression, once per loop iteration is
inefficent and pointless, particularly in a function called by
every recipe during parsing.
(From OE-Core rev: 566c0e874fc1610f3f97737b5601ef22026c918a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
FILESPATH is the preferred way of finding files now. Having a value
for FILESDIR which defaults to paths which will have already been
searched is pointless at best. This is the final step in letting
us drop FILESDIR support entirely from bitbake at some future date.
(From OE-Core rev: d6e5ceafcaef06b8a3f9acc2aa826a40a016f913)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This provides a slightly neater way of ensuring fetch/unpack get
executed (image.bbclass marks them as noexec) since I found the
current approach harder to understand at first glance.
(From OE-Core rev: 84021fd694d0a7bb1e4f49c0f7c46a0fbd178924)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* there is warning about update-alternatives-cworth ipk being
overwritten in "all" feed when opkg is built for more architectures
* see https://bugzilla.yoctoproject.org/show_bug.cgi?id=3390 for details
(From OE-Core rev: 969d10d0aa5537a119ed9be9e8321dbd73d160fe)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Licensing files changes from 1 COPYING to be split.
The Code is marked LGPLv3 or GPLv2 or both in parallel
(From OE-Core rev: 96a29f346f89641eaccdb740e4d21cc4f732768d)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
LICENSE file updated Copyright year to 2012, no other change
(From OE-Core rev: 41f3104d1993f374e9e289ac74f821261808f833)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This change fixes the following QA Warning
WARNING: QA Issue: libproxy: Files/directories were installed but not shipped
/usr/libexec
/usr/libexec/pxgsettings
/usr/libexec/.debug
/usr/libexec/.debug/pxgsettings
(From OE-Core rev: b11874ef0b80f8d5150681fc2d6a0ca7a2c8fa06)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With this recently introduced exclusion, <multilib>-meta-toolchain-sdk
throws errors about missing DEPENDS that don't exist since it needs the
PROVIDES/DEPENDS remapping. This patch tweaks the class tests to fix
the errors.
(From OE-Core rev: 9cc18fe12bd8d1c73df291b4057aab6167ef6b16)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The new version of libcheck needs gawk and we need to ensure the paths are
not taken from the build system.
(From OE-Core rev: 120bea8043d3a05174ed034e20d9094784402824)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In normal usage, we never hit the timeout issue. If we do, it becomes obvious
that the current error handling is not good enough. The request may have made it
to the server and the answer will get queued. This means the next command may get
the return value from the previous command with suitably puzzling results.
Without rewriting large sections of code, its not possible to avoid this problem.
It is better to increase the timeout to several seconds giving the server a chance
to respond and if it does timeout, hard exit since recovery is not possible with the
code base today.
I'd be happy to see the structure of this code improved but this quick fix at least
stops corrupted builds from happening which has to be a good thing.
(Bitbake rev: 410c11dd10736873f2dc587fbe9119c38831e693)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With the change to WORKDIR layout, splutting PN and PV into two directories,
the debugsrc splutting code layout became suboptimal. This changes things to
include the information as it was before. Ideally this code would be written
to more generically support other layouts buts it not clear that the tools
would even support that right now so this is the best immediate fix.
(From OE-Core rev: 432cfbb403f0e864d1fad383c2bbb6f9bdb80770)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The -dev packages were RPROVIDEing the non-dev names, which is clearly wrong.
(From OE-Core rev: 8d224244a016adc889be132d9994d7c517f7eae3)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This bbappend is forcibly enabling OpenGL on atom-pc and mpc8315e-rdb, but as
Poky enables the OpenGL distro feature this option is on for all machines
anyway.
(From meta-yocto rev: cdfa38051f9f39730e612f39227bdee3ea06bf25)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There were some changes in the xserver-xorg upstream project that need
to be reflected here too:
* extmod module was removed completely as it became empty;
* DRI1, DRI2, DBE (among others) were made built-in;
(From meta-yocto rev: ed681441a2cf06dc55e71035ecbfc637ff83640d)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add bold color output to log level name and standard color output to log msg
when bitbake is run from an iteractive console. Color output is only
enabled
if the terminal supports color.
Used Jason Wessel's recommendation for transparency on verbose, note and
plain.
(Bitbake rev: 2734240da2cc150f811129a6adf6eb4b2161b204)
Signed-off-by: Seth Bollinger <seth.boll@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Constantin Musca
Bruce Ashfield
Richard Purdie
Ross Burton
Cristian Iorga
Martin Jansa
Stefan Herbrechtsmeier
Saul Wold
Laurentiu Palcu
Seth Bollinger