aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2016-12-28ppp: Add patch to fix build with musl and 4.9 headersjku/ppp-fix-for-mutJussi Kukkonen
Removing unused includes fixes the build. Fixes [YOCTO #10853]. Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
2016-12-28ppp: Partly remove patch that doesn't make sense any moreJussi Kukkonen
ppp no longer provides the duplicate if_pppox.h header so no need to patch that out of the Makefile. Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
2016-12-22cairo: set license for cairo-docRoss Burton
2016-12-22WIP linux-firmware: remove alternatives for brcmfmac-stdio.binRoss Burton
Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22kernel: introduce linux-yocto v4.9 recipesBruce Ashfield
Introducing the 4.9 kernel recipes. 4.9 will be a LTSI kernel, so we introduce these recipes with the intent that they'll replace 4.1 as the LTSI kernel, and other older kernels (i.e 4.4/4.8) once 4.9 shown to be stable. linux-yocto-tiny and linux-yocto-rt are also part of this commit, but are placeholders while we wait for their content to be available. They will build, but provide nothing above the standard kernel at the moment. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22linux-libc-headers: introduce 4.9 headersBruce Ashfield
Bumping the linux-libc-headers to the 4.9 kernel variant. Since 4.9 will be a LTSI kernel, and there will be an associated linux-yocto it is worth moving to these headers sooner rather than later. This commit also drops the 4.8 headers and sets 4.9 to be the default. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22opkg-utils: Do not use --ignore-fail-on-non-empty with rmdirKhem Raj
--ignore-fail-on-non-empty is coreutils specific, and you are not always going to have coreutils on target systems especially small ones. They will use the busybox applet which does not support --ignore-fail-on-non-empty, use pipe and true to ignore the errorcode from rmdir instead Fixes upgrade errors on target e.g. rmdir: unrecognized option '--ignore-fail-on-non-empty' BusyBox v1.24.1 (2016-12-20 10:41:39 PST) multi-call binary. Usage: rmdir [OPTIONS] DIRECTORY... To remove package debris, try `opkg remove update-alternatives-opkg`. To re-attempt the install, try `opkg install update-alternatives-opkg`. Collected errors: * pkg_run_script: package "update-alternatives-opkg" postrm script returned status 1. * postrm_upgrade_old_pkg: postrm script for package "update-alternatives-opkg" failed Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22linux-dtb: strip DTB extension properly in postinst/postrmDenys Dmytriyenko
The use of awk -F "." in do_install/do_deploy to strip filename extension was deprecated long time ago in 72980d5bb465f0640ed451d1ebb9c5d2a210ad0c. Make a similar change in postinst/postrm to properly use basename command. Otherwise DTB files that contain dots in the name result in broken symlinks that point to non-existent truncated files. Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22externalsrc: Add optional srcdir arg to srctree_hash_filesOla x Nilsson
Make it easier to reuse the function for other dirs than EXTERNALSRC. Signed-off-by: Ola x Nilsson <ola.x.nilsson@axis.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22Revert "hdparm: 9.48 -> 9.50"Ross Burton
V2 incoming hopefully This reverts commit a199d36b90b2e88a92a05c8929a2a4b0053b4905.
2016-12-22externalsrc: Set STAMPCLEAN to match STAMPOla x Nilsson
Only the last stamp file should be kept, but unless STAMPCLEAN matches files generated using STAMP old stamp files may linger. This may cause false positives for skipping tasks. Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22oe-selftest: devtool: Reverting a change should trigger rebuildOla x Nilsson
Add code to verify that not only does a change trigger a build, but so does reverting that change. Reverting a change in a devtool managed git repo may cause the current checksum to match the checksum of a previous build, which will cause bitbake to skip builds that are needed. Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22lib/oe.sstatesig: make locked sig file consistentJianxun Zhang
Sort keys of dict 'types' prior to dumping, in order to have identical output every time. This could make it a little easier to diff these human-readable dumps. Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22ncurses: 6.0+20160625 -> 6.0+20161126Huang Qiyu
Upgrade ncurses from 6.0+20160625 to 6.0+20161126. Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22meta: use require instead of include when file should existPaul Eggleton
If the file is expected to exist, then we should always be using require so that if it doesn't we get an error rather than some other more obscure failure later on. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22useradd-example: exclude from worldKai Kang
Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22classes/buildstats: don't expand variable pointing to SystemStatsPaul Eggleton
We're placing an object into the datastore - it's very definitely not something we want to be expanding. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22oe-selftest: fix behaviour if oe-selftest.log is a dangling symlinkPaul Eggleton
If you delete the log file that the oe-selftest.log symlink points to but not the symlink itself, because we were using os.path.exists() here the code assumed that the symlink didn't exist when in fact it still did. Use os.path.lexists() instead. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22classes/sstate: fix file conflict messagePaul Eggleton
* Fix not decoding output from grep ("Matched in b'manifest...') * Fix showing "Matched in b''" if no match (show "not matched to any task" instead) * Drop the filtering out of .populate-sysroot from matched manifest names - it should have been .populate_sysroot so it doesn't work, and in any case the value of removing the task name is questionable given that we aren't removing it for any other task, and that the rest of the filename isn't only the task name, we might as well have the whole thing. At least then you can do a find on that exact name without wildcards and find it. * Fix indenting of file list entries and indent "matched in" further underneath * Minor punctuation fixes Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22classes/sstate: handle filenames containing square bracketsPaul Eggleton
If a recipe installs a file or directory whose name contains square brackets [ ] that form a valid glob expression and that file then they won't be correctly removed from the sysroot, because we pass each path in the sstate manifest to our oe.path.remove() function which calls glob.glob() on the path passed into it and the expression won't actually match the original filename. Since we don't expect to put any wildcarded expressions in the sstate manifests, and we already have a try...except around this, we can actually use os.remove() here instead. Similarly, when we pass existing file paths to "grep" looking through the manifests, we don't want those paths to be treated as regexes - so use grep's -F command line switch. Fixes [YOCTO #10836]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22lib/oe/path: add warning comment about oe.path.remove() with wildcarded ↵Paul Eggleton
filenames Add a warning in the doc comment for oe.path.remove() about using that function on paths that may contain wildcards in the actual file/directory names. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22classes/package_rpm: handle square brackets in filenamesPaul Eggleton
When constructing a spec file we list files and directory paths in the %files section. If ] or [ characters are in a file or directory name, rpm treats them as wildcards which will mean it won't properly match the filename. Instead, transform these into an ? wildcard so they don't cause a problem. (This fixes packaging the npm package "file-set" and anything that happens to depend upon it, since it includes tests with files that contain unusual characters including ] and [). Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22wic: Remove gummiboot testAlejandro Hernandez
Weve now migrated to systemd-boot, the gummiboot test on wic is no longer necessary Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22gummiboot: Remove gummiboot testsAlejandro Hernandez
Since we replaced gummiboot with systemd-boot along with its tests, the gummiboot tests are no longer necessary. [YOCTO #10332] Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22gummiboot: Remove old gummiboot recipe, related class and wks fileAlejandro Hernandez
Since the gummiboot project is no longer being maintained and we are using systemd-boot as a replacement instead, we can now clean up all remaining gummiboot files. [YOCTO #10332] Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22gummiboot: Remove/change gummiboot references with systemd-bootAlejandro Hernandez
After systemd-boot was introduced, its been tested for a while with no major issues being found until now, this patch completely replaces all gummiboot instances with systemd-boot ones, taking the next step into cleaning up systemd-boot/gummiboot. [YOCTO #10332] Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-22runqemu: let command line parameters override defaultsPatrick Ohly
It may be necessary to override the parameters gathered for the qemu invocation. For example, the qemux86 machine configuration sets "-vga vmware", but when using OVMF as BIOS, only "-vga std" is supported. By putting the parameters derived from custom runqemu parameters like "qemuparams" after the parameters derived from the machine configuration the user gets the possibility to override those. (From OE-Core rev: dd44b2eedc3befd9c8d272eb6cb2af5f419d03aa) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22module.bbclass: allow to override location of Module.symversAndré Draszik
Requiring all build systems for external kernel modules to place Module.symvers directly into ${B}/. is quite an artificial assumption/requirement. It doesn't have to end up there, but could easily end up somewhere below ${B}. Allow to override the location below ${B} Note that we still don't make use of multiple Module.symvers in case there are any generated by one single kernel module build, but this is no change in behaviour from before and could be added if there really is a demand for that. Reported-by: Denys Dmytriyenko <denis@denix.org> (From OE-Core rev: 1b5d6ea8b0680eacbd54cf1273d41cfc6592c617) Signed-off-by: André Draszik <adraszik@tycoint.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22ifupdown: upgrade to 0.8.16Maxin B. John
Refreshed the following patch: * inet-6-.defn-fix-inverted-checks-for-loopback.patch (From OE-Core rev: b5712b3c4f16ad75d8edcc445b89629ff6f65d4b) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22sqlite3: upgrade to 3.15.2Maxin B. John
(From OE-Core rev: 498a65efb92b6f3d15b4eaacddff84e6697b29f4) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22opkg-utils: warn if update-alternatives finds priority conflictChen Qi
If multiple providers for a utility have the same alternatives priority, which one would be chosen is determined by which one is installed later. Our alternatives system should be able to detect such problem and warn users so that potential problems could be avoided. Modify update-alternatives to warn users when detecting multiple providers with the same priority. [YOCTO #8314] (From OE-Core rev: ad463d531e3bc30fda1fe3bc2751de312427344c) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22file: 5.28 -> 5.29Huang Qiyu
Upgrade file from 5.28 to 5.29. (From OE-Core rev: ea773d21a3c6e329471fb40f5ee2e1d965736050) Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22kexec-tools: Update to 2.0.14He Zhe
Remove kexec-aarch64.patch since it has been merged upstream Remove kexec-x32.patch since it has been reverted upstream Backport patches for kdump arm64 from: https://git.linaro.org/people/takahiro.akashi/kexec-tools.git (From OE-Core rev: 8a3d08fb37cf6ce490885cea3ef58495f993b7db) Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22gstreamer: Upgrade to 1.10.2Khem Raj
(From OE-Core rev: 0bd49d78bc3acf427d3c97404be1344496cb67e2) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22hdparm: 9.48 -> 9.50Robert Yang
Add 0001-Makefile-use-weak-assignment-for-LDFALGS.patch to fix issues like: ERROR: hdparm-9.50-r0 do_package: QA Issue: File '/sbin/hdparm.hdparm' from hdparm was already stripped, this will prevent future debugging! [already-stripped] ERROR: hdparm-9.50-r0 do_package: Fatal QA errors found, failing task. (From OE-Core rev: e4f315ff1621603c69af70827685a206decfe69b) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22guile: 2.0.12 -> 2.0.13Robert Yang
Remove 0002-Recognize-nios2-as-compilation-target.patch which is already in the source. (From OE-Core rev: a2b7f442d8872afe8edec062c60264b31e860218) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22quilt: 0.64 -> 0.65Robert Yang
* Removed install.patch since it is already in the patch. * Fix indent for file://test.sh (From OE-Core rev: bd8b1d79b50819486e5882db05abb6b358b7392a) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22debianutils: 4.8 -> 4.8.1Robert Yang
(From OE-Core rev: dfd4c078a38c3df9ac91ae3e8d01787611bb8cab) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22qemu: Fix pci-assignHe Zhe
Fix iommu pci device assignment failure. "qemu-system-x86_64: -device pci-assign,host=02:00.0: No IOMMU found. Unable to assign device "(null)"" (From OE-Core rev: 2011d1cc6c05ff3979e4bd664ce918dc8eb8e8fb) Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22populate_sdk: don't force target debug packages into SDKRoss Burton
TOOLCHAIN_TARGET_TASK doesn't need to explicitly list sdk-target-dbg because if SDKIMAGE_FEATURES contains dbg-pkgs (as it does by default) then they'll all be installed anyway. This means that if the user removes dbg-pkgs from SDKIMAGE_FEATURES then the SDK correctly doesn't have debug packages in. [ YOCTO #9078 ] (From OE-Core rev: 4c711830ae26008f73bbf557964bdb86b8c922da) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22bitbake: cookerdata: Convert multiconfig to use BB_CURRENT_MCRichard Purdie
People are struggling with multiconfig as the point the conf file is injected into the data store is not what people expect. We can't really use a post config since that is too late and we can't really use a pre config file since that is too early. In OE terms, we need something right around the local.conf point so it behaves in a similar way. A way to handle this is to set the new variable BB_CURRENT_MC to be the currently selected multiconfig, then the metadata itself can choose when to inject the approriate configuration. (Bitbake rev: 518b9015c2be8d3894277a8e54890d6f04d656c0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22bitbake: runqueue: Only start fakeroot workers when neededRichard Purdie
Fakeroot workers usually have dependencies that need to be ready before they can be started. Starting them as a block therefore doesn't work as the dependencies may or may not have been built. Therefore start the multiconfig fakeworkers individually upon demand. [YOCTO #10344] (Bitbake rev: ab15486c636e451ed5a62e561980946887901c3b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22bitbake: runqueue: Ensure setscene tasks with overlapping stamps don't ↵Richard Purdie
parallel execute In multiconfig, mutliple tasks can execute which share the same stamp file. These must not execute in parallel, the idea is the first should execute, the subsequent ones should see a valid stamp and get skipped. The normal task execution code has stamps code to handle this, this adds similar code to the setscene execute() function to handle the issue there too. (Bitbake rev: 937acf267fa9e45f538695b2cf8aa83232a96240) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22bitbake: runqueue: Fix setscene issues with multiconfigRichard Purdie
setscene was being entirelu skipped for multiconfig variants as the tasks were simply not being spotted. If the default config was also being built it masked the problem. When this was fixed by using taskfn instead of fn in lookups against dataCache, several other instances of this problem were highlighted. This goes through and corrects the setscene code to correclty use taskfn instead of fn in the appropriate places meaning setscene tasks for multiconfig now work correctly. (Bitbake rev: cead85cf219c07b40aeb7c0d948c25f0429136db) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22bitbake: siggen: Fix clean_basepath to work with multiconfigRichard Purdie
Tasknames can now start with "multiconfig:" which broke the virtual: comparison code and lead to unpredictable checksums with nativesdk recipes. This adds in handling for the new additional prefix which unbreaks nativesdk builds when using multiconfig. (Bitbake rev: 4da296c0c93391ec37f8b6e2245071657759771e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22bitbake: build/uihelper: Show better information about multiconfig tasks on UIRichard Purdie
Currently the UI shows X is building, possibly multiple times but doesn't say which of the multilibs that might be. This adds a prefix to the task name so the mulitconfig being built can be identified. (Bitbake rev: d93ddd185dde53f50aea06ada094bb0d9b5ba4f0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22bitbake: runqueue: Ensure pseudo executes from the correct place (use the ↵Richard Purdie
right datastore with multiconfig) The location of the fakeroot command and the various environmental values need to be taken from the right multiconfig datastore, not the shared one. This patch ensures the right one is used for cases like a split TMPDIR. [YOCTO #10344] (Bitbake rev: 813a7600bc26b7132ac36d1515571d321f566afb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22lib/oe/utils: Drop python2 compatibility codeRichard Purdie
We've moved to python3, we don't need this compatibility code which just makes the code less readable. (From OE-Core rev: 425afe2484707640ac71194885fdb263e95e9950) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22libgcc-common: Don't apply symlinks for nativesdkRichard Purdie
nativesdk-libgcc doesn't need a symlink into the target space and if we do this sstate installation of the recipe can fail depending on whether it races with the cross-canadian toolchains. (From OE-Core rev: b2c1e1fe4221862e0dbf5d08960f0d0228e47c72) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-22bitbake.conf: Add inclusion of BB_CURRENT_MC.conf after local.confRichard Purdie
People are strugling with multiconfig as the up front inclusion of the configuration file doesn't do what people expect. The only way to meet user expectations is to include the file immediately after local.conf. We add BB_CURRENT_MC to bitbake so that the metadata can determine when to include the extra configuration. (From OE-Core rev: a6a3894fb2cb2097d2404b8b8cb2b85df595cfa9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-28 05:19:58 +0000