summaryrefslogtreecommitdiff
path: root/meta
AgeCommit message (Collapse)AuthorFiles
2013-04-11systemd: Fix path to systemd-analyze so it end up in the right package.Erik Botö1
Since the upgrade to version 199 the location for systemd-analyze has change this caused the systemd-analyze package to be empty and the binary was shipped with the systemd package instead. Signed-off-by: Erik Botö <erik.boto@pelagicore.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-11pulseaudio: remove spurious cd in do_compile_prependRoss Burton1
This prepend was cding to ${S}, which then breaks base_do_compile as it assumes it's in ${B}. The cd is pointless as all of the operations use absolute paths, so remove it. The result of this was that base_do_compile was failing to find the makefiles, so the compilation happened in do_install. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-11dpkg, opkg, rpm-postinst: fix overwriting the run-postinstall scriptLaurentiu Palcu3
If multiple package managers are installed in the image, they will overwrite each other's run-postinsts script, resulting in postinstalls not beeing run at all at first boot. What this patch does: * checks whether opkg/dpks/rpm is actually used to install the packages and, only after, creates the run-postinsts script; * brings dpkg recipe in sync with opkg: moves the script creation from do_install to postinstall; * move creation of run-postinsts script (rpm-postinsts recipe) to the postinstall scriptlet in order to better control the creation of the script according to the package manager used; [YOCTO #4231] [YOCTO #4179] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-11ptest bug fixesBjörn Stenberg3
Move ${PN}-ptest to start of PACKAGES to ensure all ptest files are packaged in the -ptest package. Add QA exclusions to insane.bbclass to ensure -ptest packages can contain any files they need. Disable ptest for native packages. Don't emit errors on missing _ptest functions. Signed-off-by: Björn Stenberg <bjst@enea.com> Signed-off-by: Anders Roxell <anders.roxell@enea.com> Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-11kernel.bbclass: do_strip: allow recipes to strip the kernelMichel Thebeau1
Allow recipes to specify sections to be stripped from the kernel output using KERNEL_IMAGE_STRIP_EXTRA_SECTIONS. For example: KERNEL_IMAGE_STRIP_EXTRA_SECTIONS = ".comment .unwanted" The kernel output is stripped in place. Since the toolchain does not give indication when the specified sections are absent, we read the sections first and make this report by issuing a warning to the developer. The toolchain by default strips the image with the -s option (even when -s is not specified): -s --strip-all Remove all symbol and relocation information For example, these sections are always removed: .debug_aranges .debug_info .debug_abbrev .debug_line .debug_frame .debug_str .debug_loc .debug_ranges .symtab .strtab In addition to these, the sections listed in KERNEL_IMAGE_STRIP_EXTRA_SECTIONS will also be removed. Only stripping of vmlinux (elf) is supported at this time. A warning will be given if the image type is not vmlinux. Stripping the image could also be done in the kernel, but that would only work for linux-yocto based kernels, so it's not the route we decided to go. [YOCTO 3515] Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-11kern-tools: fix conditional configuration itemsBruce Ashfield1
Variables defined in .scc files have two purposes: - Documentation in the meta-series - Variables that can be tested in sub sections and other features The second part of this functionality was broken when fixing configuration for tiny/small systems. As a result, arch tests were failing and configs were dropped. This restores the existing functionality. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-11linux-yocto/3.8: qemumips boot fixes and netfilter kernel featuresBruce Ashfield3
Updating the linux-yocto-3.8 recipes to fix two issues: 1) qemumips boot This is fixed by: Revert "Input: i8042-io - fix up region handling on MIPS" And by disabling ftrace for qemumips boards 2) netfilter options being dropped When KERNEL_EXTRA_FEATURES was introduced, and allowed to be inhibited, the variable was only applied to qemux86 machines. It should be applied ot all machine types (unless inhibited), so we restore that functionality. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10linux-yocto/3.8: qemumips graphical bootBruce Ashfield3
Updating the meta SRCREV to fix and illegal instruction that is seen when launching X with USB pointing devices. meta/qemumips: build USB_UHCI_HCD into the kernel When booting qemumips and USB_UHCI_HCD built as a module, the following trace is seen, and then prevents X from starting: qemumips user.warn kernel: Call Trace: qemumips user.warn kernel: [<c0028000>] uhci_check_bandwidth+0x0/0x160 [uhci_hcd] qemumips user.warn kernel: [<c002e08c>] uhci_urb_enqueue+0xba4/0xc48 [uhci_hcd] qemumips user.warn kernel: [<8058092c>] usb_hcd_submit_urb+0xdc/0x848 qemumips user.warn kernel: [<805b8fbc>] wacom_open+0x44/0x8c qemumips user.warn kernel: [<805a1990>] input_open_device+0xac/0xec qemumips user.warn kernel: [<805a8cec>] evdev_open+0x188/0x1bc qemumips user.warn kernel: [<802331d8>] chrdev_open+0xc8/0x1c4 qemumips user.warn kernel: [<8022b338>] do_dentry_open+0x248/0x2e4 qemumips user.warn kernel: [<8022b418>] finish_open+0x44/0x68 qemumips user.warn kernel: [<8023e51c>] do_last.isra.29+0x2c0/0xcbc qemumips user.warn kernel: [<8023efd8>] path_openat+0xc0/0x52c qemumips user.warn kernel: [<8023f840>] do_filp_open+0x4c/0xbc qemumips user.warn kernel: [<8022cc3c>] do_sys_open+0x128/0x20c qemumips user.warn kernel: [<8010c07c>] stack_done+0x20/0x44 qemumips user.warn kernel: Code: (Bad address in epc) qemumips user.warn kernel: ---[ end trace 8a48c6046870f8c2 ]--- Building the module into the kernel fixes the problem, but the root cause is still under investigation. The pipelines around jumps to module addresses seem to be triggering invalid instructions. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10linux-yocto/3.8: aufs, config processing, tiny, mips boot fixesBruce Ashfield3
Updating the SRCREVs to fix a number of bugs, boot issues and ktype support additions. standard/*: Aufs support was misplaced on the move from the -dev to release kernel, this commit restores the support. This is not active unless the aufs configuration items are enabled via the aufs-enable.scc feature. 11998bd aufs: core support f2ea9f4 aufs: standalone support bf529b6 aufs: aufs proc_map b6f0a04 aufs: aufs base support 55b0bc2 aufs: kbuild patch meta: The meta branch has updates for aufs enablement, tiny BSP configs, preempt-rt fixes and a wifi config audit fix. 4c567e0 meta/aufs: add -enable feature and patches 059fe88 meta/aufs: create aufs configuration fragment 7d672cd0 meta: add fri2 tiny BSP config. mti-malta32: This fixes the graphical boot of qemumips, the offending commit is breaking dynamic patching of ftrace on the simulation, so we revert the commit for now. 18c71ab Revert "ftrace/x86: Have x86 ftrace use the ftrace_modify_all_code()" mti-malta64: This enables the boot of qemumips64 by reverting the broken ftrace support for mips64 and by stubbing out inavlid oprofile register writes. 0ec615c Revert "ftrace/x86: Have x86 ftrace use the ftrace_modify_all_code()" bbefde3 oprofile/mips: do not set perf_irq for qemu mips 64 eb6cb79 Revert "MIPS: Function tracer: Fix broken function tracing" [YOCTO #4052] [YOCTO #4129] [YOCTO #2410] Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10kern-tools: fix excluded configuration processingBruce Ashfield1
One of the features introduced early on in the 1.4 release cycle was the ability to include a kernel feature, but only get its patches and not configs (and vice versa). As it turns out, this only was exercised recently and once a single include with dropped configs was started, ALL configuration values following the commit were dropped. To fix the problem, the processing of kernel features has been split into two. Where the features are preprocessed and the assembled/complete file is used to generate the meta-series (which is later applied to the tree). The logic of the tools is the same, but the two phases of processing allows configuration values to be excluded properly and simply, while keeping the logic for modifying the tree in a separate step. All changes are invisible to the user, and are done within the existing scripts and build system bindings. Output series and manipulations to the tree are the same as they were before this change. Updating the kern-tools SRCREV to pickup the kern-tools changes for this. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10linux-yocto/3.8: atom-pc: Update atom-pc-preempt-rt.scc to reuse config from ↵Bruce Ashfield2
common-pc Updating the meta branch SRCREV to pick up the following change: The atom-pc preempt-rt BSP was omitting the config from common-pc, resulting in very few drivers being built, including USB_STORAGE, preventing preliminary boot testing. Remove the "standard features" as those are covered by the common-pc scc files. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10linux-yocto/3.8: fix atom-pc config audit warningsBruce Ashfield2
The atom-pc was referencing some invalid and unecessary config options that are causing kernel config audit warnings. With this SRCREV update, the configuration is clean against the 3.8 kernel. [YOCTO #3490] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10linux/yocto: update AUTOFS configurationBruce Ashfield2
When systemd is enabled, qemumips failed to boot with the following trace: Reserved instruction in kernel code[#1]: Cpu 0 $ 0 : 00000000 80232500 c0011000 80000000 $ 4 : c0017440 00000000 87032400 8704b000 $ 8 : 00000000 00000000 00000010 003fffff $12 : 00000000 7fafbab4 00000000 87d6fbb0 $16 : 87f98780 c0017440 c0017440 00000000 $20 : 8704a000 00000000 8704a000 00000000 $24 : 00000010 80480630 $28 : 87c22000 87c23e28 7fafbc00 80232408 Hi : 00000000 Lo : 00000000 epc : c0011000 autofs_mount+0x0/0x30 [autofs4] Not tainted ra : 80232408 mount_fs+0x68/0x200 Status: 1000a403 KERNEL EXL IE Cause : d0808028 PrId : 00019300 (MIPS 24Kc) Modules linked in: autofs4 Process systemd (pid: 1, threadinfo=87c22000, task=87c28000, tls=77787490) Stack : 809b3e28 802512bc 00000000 808b0da4 87f3d310 87936c38 87032400 8704b000 87f98780 c0017440 00000020 8704b000 87032400 87032480 00000000 80251a2c 00000006 8022f7fc 87032480 802507f0 00000000 87032400 8704b000 7fafba94 00000000 c0017440 8088275c 80253f40 7fafb9d0 00000016 38513fac 0051b2a8 8704b000 801df604 00000000 0000000a 87f5c000 801f5968 87f3d310 87936c38 ... Call Trace: [<c0011000>] autofs_mount+0x0/0x30 [autofs4] [<80232408>] mount_fs+0x68/0x200 [<80251a2c>] vfs_kern_mount+0x68/0x114 [<80253f40>] do_mount+0x218/0x9d0 [<8025479c>] sys_mount+0xa4/0xec [<8010c07c>] stack_done+0x20/0x44 The policy of building AUTOFS as a module is something that can be changed, since boot processes that use automounting can take advantage of the built in support to reduce complexity. The size increase of the base policy is small with this change, and users of the linux-yocto kernel can still override this value, which is exactly what the poky-tiny kernel does. Keeping the configuration consistent for all boards, and not adding and exception for qemumips makes sense in this case. [YOCTO #4129] Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10initscripts: fix read-only-rootfs-hook.sh to start earlierPaul Eggleton2
Mount /var/volatile ourselves so that we can set up the writable area first. This fixes the urandom service not starting properly when read-only-rootfs is enabled. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10initscripts: fix read-only-rootfs-hook.sh to avoid using unionfsPaul Eggleton1
Unionfs isn't available everywhere, and we can get similar results (if not quite as neatly) by using bind mounts + tmpfs and copying the data over. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10rpm-postinsts: avoid errors during boot with read-only-rootfs enabledPaul Eggleton1
* If /etc/rpm-postinsts doesn't exist, don't error * If deleting the script errors, don't bother printing it (this will always happen if the root filesystem is read-only) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10rpm-postinsts: don't create broken postinst scriptPaul Eggleton1
Not only was the variable reference in this line broken, but it wasn't going to work anyway - we install the script directly into /etc/rcS.d and not into /etc/init.d, so the code in update-rc.d.bbclass couldn't find anything there. This resulted in a postinstall script for rpm-postinsts being created in /etc/rpm-postinsts which can't work when the root filesystem is read-only. To simplify things just remove the use of update-rc.d.bbclass since we don't really need the added complexity here. Fixes [YOCTO #4222]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10tinylogin: Fix mix of tabs and spaces for SRC_URI indentationMartin Jansa1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10systemd: use update-alternatives.bbclassRadu Moisan1
switch from using plain update-alternatives command to update-alternatives.bbclass style Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10busybox: fail on no mediaSaul Wold2
The current behaviour of busybox is to try all fstype when automounting even when no media exists. The util-linux mount command bails when no media exists, so change the behaviour of busybox to do the same. It could also be argued that the KERN_INFO message from btrfs could be removed, but that would be harder to accomplish. Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10postinst-intercepts, qemu.bbclass: fix segfaults in postinstallsLaurentiu Palcu4
Postinstalls that use qemu are throwing a segmentation fault when building for qemux86-64 on a 64bit host (it might also happen for qemux86 if building on a 32bit host but I didn't test). It looks like qemu looks for ld.so.cache which is not found because it is generated after rootfs_(rpm|ipk|deb)_do_rootfs is called and then it tries to load libraries from the default paths (which are the host's). In order to avoid this, pass the LD_LIBRARY_PATH explicitly to the target's dynamic loader. Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10update-rc.d: correctly look up the initscript params with overridesRoss Burton1
The creation of a clone of d with extra OVERRIDES was removed in 72c1fd72d3b479c728e249eaa763116d352e945b but some of the lookups are essential so that variables such as ${INITSCRIPT_PARAMS} get overriden and resolved correctly on a per-package basis. [ YOCTO #3960 ] Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10initrdscripts: Add udev sbin based libexec pathRichard Purdie2
For better or worse we need to use base_sbindir for udev's libexec dir. This updates the initrdscripts to also cover the new location. I'd prevously assumed that it was already covered but its not. udev internal binaries shouldn't be in PATH so we have to do this to deal with the issue. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10classes/license: remove outdated commentPaul Eggleton1
Package listing was implemented in the deb backend some time ago. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10meta-*/conf/layer.conf: tweak BBFILES commentPaul Eggleton1
"packages" was the old name (pre-2010) under which the recipe files were stored. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10meta/recipes.txt: add recipes-lsb4Paul Eggleton1
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-09udev: fix init script for the location of udevdSaul Wold3
Ensure we can update the script base don the location of the udevd installation Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-09systemd.bbclass: restart service in postinst, not startRoss Burton1
When upgrading packages it's possible that the service is already running because opkg doesn't actually execute the prerm hooks on upgrades, which is where the service should be stopped. Handle this case by restarting in postinst instead of starting. If the service isn't already running then this doesn't make a difference, but if it is running then the service will be restarted. [ YOCTO #4213 ] Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-09udev: Move udevd back to /sbinRadu Moisan2
Along with v182 upgrade udevd was moved to ${base_libdir} making scripts like init-live.sh to fail in finding udevd. We have some problems here since the placing binaries into either libdir breaks the way our multilib handling works. That code and its associated sanity tests assume that libdir contains binaries of a particular architecture and that these are not allowed to overlap. This is in contrast to the bindirs where conflicts are expected and handled appropriately. So whilst upstream may desire this directory layout, it won't work for OE's usage of it and we need to configure udev differently. The scripts already have fallback code to handle udev in the two locations so there is no issue is going back to our previous layout. [Yocto #4046] Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-09base.bbclass: Fix matching of MACHINEOVERRIDES in COMPATIBLE_MACHINEOtavio Salvador1
The use of SOC_FAMILY here is old code and SOC_FAMILY is now implemented by MACHINEOVERRIDES behind the scenes. It therefore makes more sense to use the replacement value in this code. Just like SOC_FAMILY, this is a ":" delimited variable so we should iterate over the components, not use the value directly. Finally, MACHINEOVERRIDES contains MACHINE so we don't need to check that directly. This makes the functionality match what most users would expect it to do and is also compatible with the way things previously worked. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-09libpng12: remove prefer version and add it to lsb packagegroupKang Kai2
Because rename libpng_1.2.50 to libpng, remove the perfer verion from default-versions.inc and add libpng12 to lsb packagegroup. Signed-off-by: Kang Kai <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-09libpng12: rename libpng_1.2.50 to libpng12Kang Kai1
As Mark's suggestion, rename libpng_1.2.50 to libpng12 that multi-versions libpng could coexist. We want to make sure we have both the old and new versions to meet LSB compliance (for people who have that enabled) as well as the new version for newer applications. And drop link files that conflict with higher version. [YOCTO #4221] Signed-off-by: Kang Kai <kai.kang@windriver.com> CC: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-09openssl: Upgrade to v1.0.1eRadu Moisan20
Dropped obolete patches and pulled updates for debian patches. Addresses CVEs: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-2686 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0166 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0169 [YOCTO #3965] Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-09classes/buildhistory: fix interaction with rm_workPaul Eggleton1
Change do_write_srcrevs to a postfunc of do_fetch, avoiding a dependency being created that causes large numbers of setscene tasks being executed on every build with both buildhistory and rm_work being enabled. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-09rpm: fix RDEPENDSLaurentiu Palcu1
The rpm-postinsts runtime dependency was overwritten. Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-09qemu: Add backported patch to address random segfaultsRichard Purdie2
We've been seeing random sefgaults on a variety of architectures which appear to be from an issue in qemu. The attached backport from upstream appears to fix these. [YOCTO #4216] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-08alsa-tools: Fix sys/io.h patchSaul Wold1
I blew my #if expression! Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-08kernel.bbclass: do_sizecheck: update path to build image and do not deleteMichel Thebeau1
do_sizecheck has a few issues especially with vmlinux image type. It breaks because KERNEL_OUTPUT is a path relative to ${B}. When do_sizecheck runs it does not find the file (because the working directory is elsewhere) and does not fail. Also, the image file referenced by KERNEL_OUTPUT may be a link. Finally, when do_sizecheck deletes the oversized kernel image it leaves the previously run do_compile task with inaccurate status. So, do the following: - specify that the working directory should be ${B} - use ls -L to reference to the real file, and ensure that the link file is created - keep the oversized image file so the status of do_compile is valid [YOCTO #3514] Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-08layer.conf: add systemd-serialgetty to SIGGEN_EXCLUDERECIPES_ABISAFEMartin Jansa1
* it was imported from meta-systemd without SIGGEN_EXCLUDERECIPES_ABISAFE change Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-08bluez4: add readline dependencyAlexandru DAMIAN1
bluez4 uses readline to be build, but the dependency is not listed This is listed in the configuration log. So we add it. Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-08systemd: Set the default firmware path to enable firmware loading in udevHolger Hans Peter Freyther2
After some breakage in udev the kernel gained direct firmware loading. For older kernels (e.g. 3.2 in my case) udev still needs to load the firmware. Firmware loading is enabled once a default firmware path is set. Apply a compile fix from the upstream project. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-08tcf-agent: Use kill instead of killproc to stop agentIoana Grigoropol2
When shutting down a core-image-lsb-sdk image, there is a lot of time spend stopping tcf-agent, which slows down the whole process. The reason for this slowdown is the fact that it tries in a loop to kill tcf-agent service by using killproc with the path of the executable and killproc does not seem to available in lsb images. This patch fixes the issue by using "kill" instead of "killproc". [Yocto #3928] Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com> Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-08smart: disable CHANNELSDIRBogdan Marinescu2
Make CHANNELSDIR in smart empty, since this causes host contamination issues on some RPM-based hosts on which smart is already installed. [YOCTO #3881] Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-08gtk-update-icon-cache-native: create wrapper scriptLaurentiu Palcu1
When using the sstate from another build machine, the path to the pixbuf loader's cache points to a path on the remote machine. Hence, the update of the icon cache fails on host. Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-08image.bbclass: fix postinstall intercepts fallbackLaurentiu Palcu1
The wrong type of paranthesis was used so 'continue' did nothing (was in another context) and the packages were marked as installed. Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-08gst-ffmpeg: fix --disable-yasmTom Zanussi1
The gst-ffmpeg build shows the following warning: configure: WARNING: unrecognized options: --disable-yasm which means that the following test in configure always fails and --disable-yasm never gets passed to the embedded ffmpeg build: 'if test "x$disable_yasm" = "xyes"; then' embffmpeg_configure_args="$embffmpeg_configure_args --disable-yasm" commit 4d309730 ['gst-ffmpeg: configure-fix patch used wrong test'] actually fixed the obviously backwards syntax by reversing the test - prior to that, --disable-yasm would always unconditionally be passed into the embedded ffmpeg config. This fixes things so that the variable actually exists and makes the test meaningful. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-08insane.bbclass: Updated MicroBlaze machine definitionsNathan Rossi1
* Removed existing definition with machine 47787, this definition is outdated, a sanity error should occur if an ELF uses this value. * Added new definition with machine 189. This value replaces the existing value since August 2009. See binutils thread for more information. (http://sourceware.org/ml/binutils/2009-08/msg00127.html) Signed-off-by: Nathan Rossi <nathan.rossi@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-05curl: backport patch to fix segfaultsMartin Jansa2
* e.g. ecore, efreet segfault a lot without this patch Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-05linux-yocto-tiny: Add 3.8.4 recipeDarren Hart1
Bring linux-yocto-tiny up to the latest linux-yocto 3.8.4 version. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-05local.conf.sample: Add info about -ptest package groupMaxin B. John1
Add information about ptest package testing in local.conf.sample file. Signed-off-by: Maxin B. John <maxin.john@enea.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>