summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core
Commit message (Collapse)AuthorAgeFilesLines
* musl: Fix issues in relative symlink creationAmarnath Valluri2017-03-242-11/+53
| | | | | | | | | | | Make use of lnr/ln -r while creating relative symlinks than guessing the relalive path. (From OE-Core rev: 8205b92631bc1dcb3419c709ef5a98b2b3cd9d70) Signed-off-by: Amarnath Valluri <amarnath.valluri@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base-files: Replace hardcoded root paths with appropriate bitbake variablesAmarnath Valluri2017-03-241-2/+3
| | | | | | | | | | | /bin, /sbin, /lib are replaced with ${base_bindir}, ${base_sbindir} and ${base_libdir}. (From OE-Core rev: 9b490e61938e06fda881b2213565c4de1f740f98) Signed-off-by: Amarnath Valluri <amarnath.valluri@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: glibc-gconv-{utf-16, cp1252} for binutils windresNathan Rossi2017-03-241-0/+3
| | | | | | | | | | | | | | The windres binutils binary which is used for Windows resource files requires utf-16 and cp1252 encoding support in order to correctly generate resource files with strings. As such when using uninative to build mingw resources for a nativesdk target the windres binary is executed on the native host, thus using the uninative libc and gconv modules. (From OE-Core rev: 778fb2342da55e202cfb7af04bbf120c1b68620a) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ovmf: fix toolchain selectionPatrick Ohly2017-03-222-66/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For the native tools, a static patch inserted gcc/g++/ld/ar while later adding BUILD_LDFLAGS and BUILD_CFLAGS with sed. Now it's all done with sed, which has the advantage that it uses the actual compile variables. However, in practice those are the same. More importantly, picking the build tools for the target was broken. ovmf-native tried to insert TARGET_PREFIX into the tools definition file, but that variable is empty in a native recipe. As a result, "gcc" was used instead of "${HOST_PREFIX}gcc", leading to an undesirable dependency on the host compiler and potentially (probably?!) causing some of the build issues that were seen for ovmf. The new approach is to override the tool selection in ovmf-native so that the HOST_PREFIX env variable is used, which then gets exported during do_compile for the target. While at it, Python code that gets appened to do_patch only to call shell functions gets replaced with the do_patch[postfuncs] mechanism. Incremental builds now always use the tools definition from the current ovmf-native; previously, only the initial build copied the template file. Probably the entire split into ovmf-native and ovmf could be removed. This merely hasn't been attempted yet. (From OE-Core rev: 23a12d87a6e82f80f4ccc1a01c707faa89ff7abd) 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>
* util-linux,shadow: Make 'nologin' alternative commandAmarnath Valluri2017-03-221-2/+3
| | | | | | | | | | | | Both shadow and util-linux packages provides 'nologin' binary in ${base_sbindir} and ${sbindir} respectively, this leads to conflict when 'usrmerge' feature is enabled, where ${sbindir} == ${base_sbindir}. Hance, handle this to alternative system to resolve the conflict. (From OE-Core rev: 07d6d0fb4dc689008bb0022d7d2ecc890c9159e5) Signed-off-by: Amarnath Valluri <amarnath.valluri@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: Make sure '${base_bindir}/reset' is part of util-linux-reset ↵Amarnath Valluri2017-03-221-1/+1
| | | | | | | | | | | | | package. update-alternative.bbclass might rename the 'reset' binary when LINK_NAME == TARGET, This is true (${base_bindir} == ${bindir}) in 'usrmerge' distros. Hence, suffix with * to properly package the renamed binary. (From OE-Core rev: ebf5cc1a6fecb0761fd88e113fac785b49bc1a45) Signed-off-by: Amarnath Valluri <amarnath.valluri@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: Do not add libnss_* to systemd packageAmarnath Valluri2017-03-221-1/+0
| | | | | | | | | | | libnss_* files should be part of corresponding sub-packages, the split happens by do_package_split(). By adding ${libdir}/libnss_* to FILES_${PN}, those files end up in the systemd package when ${libdir} == ${base_libdir}. (From OE-Core rev: 46046880e42ae924548eb5c0ec53f9448f6f932e) Signed-off-by: Amarnath Valluri <amarnath.valluri@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: Fix packaging with "usrmerge"Jussi Kukkonen2017-03-221-3/+3
| | | | | | | | | | Make sure fsck.cramfs is packaged before fsck so the latter does not steal the fsck.cramfs binary when building with usrmerge. (From OE-Core rev: 333e959448c2bc0d2c472e0b7d1dab606ab723e6) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Ensure ldconfig is packaged into glibcJussi Kukkonen2017-03-221-1/+1
| | | | | | | | | | If base_bindir=bindir, /usr/sbin/ldconfig gets packaged into glibc-utils instead of glibc: Switch PACKAGES order to prevent this. (From OE-Core rev: 2794b1cc12af051db404d46aea4db4c74e8e1fe3) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* busybox: ignore the largefile distro feature ( always enable LFS )Andre McCurdy2017-03-222-3/+3
| | | | | | | | (From OE-Core rev: f16723f66837a2acad3c114e4064e0ab1cb3a7a6) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-packagegroup-sdk-host.bb: add cmakebrian avery2017-03-171-0/+1
| | | | | | | | | | | | The Eclipse plugin uses cmake from the SDK and currently has issues because cmake is not installed as a host tool. This patch adds cmake as a host tool for the sdk/esdk. (From OE-Core rev: b1ccab95464855877558972c4523956be32dee36) Signed-off-by: brian avery <brian.avery@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gettext: split recipe's descriptionLeonardo Sandoval2017-03-171-1/+4
| | | | | | | | | | Split long recipe description into multiple lines. (From OE-Core rev: 13cf0df0252941b9575da613488cbc141e043a8a) Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* musl: Update to latestKhem Raj2017-03-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | Rich Felker (11): fix ld-behavior-dependent crash in ppc64 ldso startup rework ldso handling of global symbol table for consistency reorder addend handling before symbol lookup in relocation code emulate lazy relocation as deferrable relocation fix free of uninitialized buffer pointer on error in regexec in static dl_iterate_phdr, fix use of possibly-uninitialized aux data fix possible fd leak, unrestored cancellation state on dns socket fail fix wide scanf's use of a compound literal past its lifetime fix one-byte overflow in legacy getpass function avoid loading of multiple libc versions via explicit pathname remove unused refcnt field for shared libraries Szabolcs Nagy (1): treat STB_WEAK and STB_GNU_UNIQUE like STB_GLOBAL in find_sym (From OE-Core rev: 2b1e9ddb10d4766cc4f8be3e55e4fc3d2810bbcb) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: use update-alternatives for more manpagesPaul Gortmaker2017-03-171-1/+3
| | | | | | | | | | | | | | | | | To fix: file /usr/share/man/man1/eject.1 conflicts between attempted installs of util-linux-doc-2.29.1-r0.core2_64 and eject-doc-2.1.5-r1.core2_64 and file /usr/share/man/man1/logger.1 conflicts between attempted installs of util-linux-doc-2.29.1-r0.core2_64 and inetutils-doc-1.9.4-r0.core2_64 (From OE-Core rev: a65e69d006bceacb042b377f2cd0dd8a3e72ea62) Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* readline: Remove unused patchJussi Kukkonen2017-03-161-34/+0
| | | | | | | | | | config-dirent-symbols.patch was removed from SRC_URI as "already applied in upstream" in 983a4986947. (From OE-Core rev: 43e764a54458c9c6665bb7734b1fc7e7956bffdc) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: ensure pod2man present in BAJuro Bystricky2017-03-161-1/+1
| | | | | | | | | | | | | | | | | | "pod2man" went missing from BA, but it is required. This patch fixes the Toaster error: <...> ERROR: These tools appear to be unavailable in PATH, please install them in order to proceed: pod2man <...> [YOCTO#11144] (From OE-Core rev: 562c184d52db2182eafde3cf9866606145784deb) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: fix build errorsJuro Bystricky2017-03-161-0/+2
| | | | | | | | | | | | Remove any symlinks before creating new ones to avoid potential build errors such as: FileExistsError: [Errno 17] File exists: '../../usr/src/kernel' -> ... ' (From OE-Core rev: 376aa835dd70e646a00706272db6f5ac7f419ce7) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: use pip3-nativeJuro Bystricky2017-03-161-2/+4
| | | | | | | | | | | | | Do not rely on pip3 being installed on the host. Use pip3-native instead. [YOCTO#10909] [YOCTO#11022] (From OE-Core rev: 0c349f06b6b026e9bbd3e9a8188e3d8645fd00d9) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* run-postinsts: simplify the logic of whether to install it to imagesAlexander Kanavin2017-03-141-1/+1
| | | | | | | | | | The logic is scattered all over the place, but amounts to "install, unless the rootfs is read only". Let's express that directly. (From OE-Core rev: 697804229a172125ce7d3bfc9b343812d6fe3240) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-packagegroup-sdk-host: replace smartpm with dnfAlexander Kanavin2017-03-141-1/+1
| | | | | | | (From OE-Core rev: 45b97161915ce7872ef7161451a5c83507072a72) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base-files: do not write the current date into /etc/issue and /etc/issue.netAlexander Kanavin2017-03-111-2/+4
| | | | | | | | | | | This is causing a problem in multilib where base-files and lib64/32-base-files clash because they may have different dates. Also, if the package is coming from sstate it has an incorrect date anyway. (From OE-Core rev: 846c86ffc4574feafd89a028e50f7719075633f2) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: do the multilib_header magic also for bits/long-double.hAlexander Kanavin2017-03-111-1/+1
| | | | | | | | | | Otherwise it will cause conflicts in mutlilib setting, as it varies from one machine to another. (From OE-Core rev: a3b19882e2f50089c785b1e2591550356c12a175) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glib-2.0: improve determinism for GIO ptestsRoss Burton2017-03-111-0/+4
| | | | | | | | | | | Previously the GIO tests would be built or not depending on whether the host had a dbus-daemon binary available. Fix this by seeding the AC_CHECK_PROGS check with the right value, and adding a RDEPENDS for dbus-daemon on the target. (From OE-Core rev: 1944c9a1764105c15844c7dbf1d430389c02b631) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* busybox: ifupdown:pass interface device name for ipv6 route commandHaiqing Bai2017-03-102-0/+53
| | | | | | | | | | | | | IPv6 routes need the device argument for link-local routes, or they cannot be used at all. E.g. "gateway fe80::def" seems to be used in some places, but kernel refuses to insert the route unless device name is explicitly specified in the route addition. (From OE-Core rev: 96ed437d57316153453bb5e170a4fd4f3a95883d) Signed-off-by: Haiqing Bai <Haiqing.Bai@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dropbear: drop support for DSA host keys in dropbear init scriptAndre McCurdy2017-03-101-30/+6
| | | | | | | | | | | | | | Bring the dropbear init script into sync with the systemd service file (dropbearkey.service supports RSA host keys only) and with recent versions of openssh which deprecate DSA host keys. https://www.gentoo.org/support/news-items/2015-08-13-openssh-weak-keys.html (From OE-Core rev: 6bd7341a38a8bb5387ea81dbccfed327370569f3) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* zlib: Upgrade 1.2.8 -> 1.2.11Peter Marko2017-03-085-3/+3
| | | | | | | | | | | | | | Licence updated by removing its first line which was containing copyright notice including year, which could change quite often. Additional empty line was deleted, too. (From OE-Core rev: 8b15b7bd10db83b3390827231b54aeb3452bcb6f) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Andrej Valek <andrej.valek@siemens.com> Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: start to ignore the largefile distro featureAndre McCurdy2017-03-081-2/+2
| | | | | | | | | | | | | | | | | | | | | The largefile distro feature has been enabled by default in oe-core for a long time and, more recently, also in poky-tiny. Building without the largefile distro feature receives little or no testing. Many packages now enable LFS without exposing a configure option, so there should be very little expectation that disabling the distro feature will result in a distro which globally disables LFS. Respecting the distro feature adds a maintenance over-head and may be the source of configurations oddities (e.g. dbus-native currently builds with LFS disabled for no clear reason - fixed by this commit). Ignore the largefile distro feature more widely, as a first step towards deprecating and eventually removing it. (From OE-Core rev: a75ccaea77c8aad8d46e87e8ed4af2e2e0ad5327) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: Move out stale GPLv2 versions to a seperate layeruninative-1.5Richard Purdie2017-03-0724-6695/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These are recipes where the upstream has moved to GPLv3 and these old versions are the last ones under the GPLv2 license. There are several reasons for making this move. There is a different quality of service with these recipes in that they don't get security fixes and upstream no longer care about them, in fact they're actively hostile against people using old versions. The recipes tend to need a different kind of maintenance to work with changes in the wider ecosystem and there needs to be isolation between changes made in the v3 versions and those in the v2 versions. There are probably better ways to handle a "non-GPLv3" system but right now having these in OE-Core makes them look like a first class citizen when I believe they have potential for a variety of undesireable issues. Moving them into a separate layer makes their different needs clearer, it also makes it clear how many of these there are. Some are probably not needed (e.g. mc), I also wonder whether some are useful (e.g. gmp) since most things that use them are GPLv3 only already. Someone could now more clearly see how to streamline the list of recipes here. I'm proposing we mmove to this separate layer for 2.3 with its future maintinership and testing to be determined in 2.4 and beyond. (From OE-Core rev: 19b7e950346fb1dde6505c45236eba6cd9b33b4b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* musl: Update to tipKhem Raj2017-03-071-1/+1
| | | | | | | | | | | | | | | | | | | Bring in some needed chnages for arm Bobby Bingham (1): s390x: implement dlsym Rich Felker (2): fix build regression in arm atomics asm with new binutils allow page size to vary on arm Szabolcs Nagy (1): fix lsearch and lfind to pass key as first arg to the compar callback (From OE-Core rev: 1e47495223aa75ebee6018429c92271c359ec2b9) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: check "ldconfig" distro feature when setting PACKAGECONFIGAndre McCurdy2017-03-041-2/+1
| | | | | | | | | | | Avoid trying to call ldconfig at run-time in distros which don't provide ldconfig on the target. (From OE-Core rev: faff19f046e881f546c1ad397e101c000c9bba3d) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: replace USE_LDCONFIG with new "ldconfig" distro featureAndre McCurdy2017-03-041-6/+3
| | | | | | | | | | | | | | | | | | | | | USE_LDCONFIG could previously be set to 0 by distros which do not require ldconfig or ld.so.conf on the target. Since more and more recipes may need to respect that option, replace the ad-hoc variable with a distro feature. Distros which previously set: USE_LDCONFIG = "0" Should now instead use: DISTRO_FEATURES_BACKFILL_CONSIDERED_append = " ldconfig" (From OE-Core rev: a905df2dd8f43a2febffa64a39b6e508510326a0) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-estsdk-toolchain: use WORKDIR instead of D to hold locked-sigsRoss Burton2017-03-021-1/+1
| | | | | | | | | | | | | | do_locked_sigs() uses ${D} to hold a file as input to the sstate staging code. Generally this isn't a problem as it happens after packaging, but sometimes (if the recipe is rebuild, perhaps) do_package() will see the file inside ${D} and fail because there is an uninstalled file. Solve this by using a directory under ${WORKDIR} so it can't be packaged. (From OE-Core rev: 97056011c17f343e697aa9f0d418f6487b9f7465) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glib-2.0/glib.inc: If 'charset.alias' exists drop itNathan Rossi2017-03-011-4/+4
| | | | | | | | | | | | Delete the 'charset.alias' file during the do_install task if it exists. This file is not shipped in any packages and on the targets that it is generated (musl and mingw32) it is undesired. (From OE-Core rev: ba69323b58071593fa917bf902314eb6eace25a8) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glib-2.0/glib.inc: Only apply MLPREFIX renaming to class-targetNathan Rossi2017-03-011-5/+5
| | | | | | | | | | | | | When renaming the 'gio-querymodules' binary to prefix with the current MLPREFIX, only do this for target packages where the MLPREFIX makes sense. This skips renaming for nativesdk targets which have MLPREFIX set to 'nativesdk-'. (From OE-Core rev: a84ac3667d8b216164b80c88866325908c5ad98f) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glib-2.0: Upgrade 2.50.2 -> 2.50.3Jussi Kukkonen2017-03-011-2/+2
| | | | | | | | | | Tiny bug fix release. (From OE-Core rev: 41f44be8e35f73e78cf0c7a025cb8dc56c3ac258) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kbd: update to 2.0.4Alexander Kanavin2017-03-011-2/+2
| | | | | | | | (From OE-Core rev: 40b19c1710aff449b8c7cf93f2b635b44fa85e7d) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* zlib: fix upstream version checkAlexander Kanavin2017-03-011-0/+1
| | | | | | | | (From OE-Core rev: a684148e9e0f5473078f2d087e2489ab3352aeac) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts/sysfs.sh: mount configfs if presentMike Looijmans2017-03-011-0/+4
| | | | | | | | | | | | configfs is another kernel virtual file system that should be mounted if configured, so if it's configured into the kernel, mount it. It is used to configure e.g. USB gadget mode and devicetree overlays. (From OE-Core rev: 4f52130475d026c32f0380d301f56f6fa3df7ac9) Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: Make use of the new bb.utils.filter() functionPeter Kjellerstedt2017-03-018-16/+11
| | | | | | | (From OE-Core rev: 0a1427bf9aeeda6bee2cc0af8da4ea5fd90aef6f) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ovmf: increase path length limitPatrick Ohly2017-03-012-0/+34
| | | | | | | | | | | | The VfrCompile tool has a hard-coded maximum length for path names which turned out to be too small by around 20 characters in the Yocto autobuilder setup. Increasing the maximum by a factor of 4 is relatively easy and makes the problem less likely. (From OE-Core rev: ea296ab42a7a65055657b950d8248d94f0ac56f1) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ovmf: remove BGRT patchPatrick Ohly2017-03-012-111/+0
| | | | | | | | | | This patch was added to meta-luv for kernel testing purposes and probably is not relevant for OE-core. (From OE-Core rev: 240e96e6196c32ddabb0c1aff3ee83458c98a9bd) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ovmf: build image which enrolls standard keysPatrick Ohly2017-03-014-0/+1167
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When booting a qemu virtual machine with ovmf.secboot, it comes up with no keys installed and thus Secure Boot disabled. To lock down the machine like a typical PC, one has to enroll the same keys that PC vendors normally install, i.e. the ones from Microsoft. This can be done manually (see https://wiki.ubuntu.com/SecurityTeam/SecureBoot and https://github.com/tianocore-docs/Docs/raw/master/White_Papers/A_Tour_Beyond_BIOS_into_UEFI_Secure_Boot_White_Paper.pdf) or automatically with the EnrollDefaultKeys.efi helper from the Fedora ovmf rpm. To use this with qemu: $ bitbake ovmf-shell-image ... $ runqemu serial nographic qemux86 ovmf-shell-image wic ovmf.secboot ... UEFI Interactive Shell v2.1 EDK II UEFI v2.60 (EDK II, 0x00010000) Mapping table FS0: Alias(s):HD2b:;BLK4: PciRoot(0x0)/Pci(0x5,0x0)/HD(1,GPT,06AEF759-3982-4AF6-B517-70BA6304FC1C,0x800,0x566C) BLK0: Alias(s): PciRoot(0x0)/Pci(0x1,0x0)/Floppy(0x0) BLK1: Alias(s): PciRoot(0x0)/Pci(0x1,0x0)/Floppy(0x1) BLK2: Alias(s): PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0) BLK3: Alias(s): PciRoot(0x0)/Pci(0x5,0x0) Press ESC in 1 seconds to skip startup.nsh or any other key to continue. Shell> fs0:EnrollDefaultKeys.efi info: SetupMode=1 SecureBoot=0 SecureBootEnable=0 CustomMode=0 VendorKeys=1 info: SetupMode=0 SecureBoot=1 SecureBootEnable=1 CustomMode=0 VendorKeys=0 info: success Shell> reset Remember that this will modify deploy/images/qemux86/ovmf.secboot.qcow2, so make a copy and use the full path of that copy instead of the "ovmf" argument if needed. The ovmf-shell-image contains an EFI shell, which is what got started here directly. After enrolling the keys, Secure Boot is active and the same image cannot be booted anymore, so the BIOS goes through the normal boot targets (including network boot, which can take a while to time out), and ends up in the internal EFI shell. Trying to invoke bootia32.efi (the shell from the image) or EnrollDefaultKeys.efi then fails: Shell> bootia32.efi Command Error Status: Security Violation The main purpose at the moment is to test that Secure Boot enforcement really works. If we had a way to sign generated images, that part could also be tested by booting in a locked down qemu instance. 0007-OvmfPkg-EnrollDefaultKeys-application-for-enrolling-.patch is from https://src.fedoraproject.org/cgit/rpms/edk2.git/tree/0007-OvmfPkg-EnrollDefaultKeys-application-for-enrolling-.patch?id=b1781931894bf2057464e634beed68b1e3218c9e with one line changed to fix https://bugzilla.redhat.com/show_bug.cgi?id=132502: "EFI_STATUS Status = EFI_SUCCESS;" in EnrollListOfX509Certs() lacked the initializer. (From OE-Core rev: 1913ace7d0898b5a23a2dbdc574ab1d8648927c5) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ovmf_git.bb: enable Secure BootPatrick Ohly2017-03-011-0/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When enabled via PACCKAGECONFIG = "secureboot" (off by default because of the extra work and license change), the recipe compiles OVMF twice, once without Secure Boot, once with. This is the same approach as in https://src.fedoraproject.org/cgit/rpms/edk2.git/tree/edk2.spec The results are "ovmf.qcow2" and "ovmf.secboot.qcow2" in the image deploy directory, so runqemu <machine> <image> ovmf.secboot will boot with Secure Boot enabled. ovmf.secboot.code.qcow2 is provided for those who want separate code and variable flash drives. The normal ovmf.vars.qcow2 can be used with it. In contrast to Fedora, no attempt is made to strip potentially patent encumbered algorithms out of the OpenSSL archive. OVMF does not use the ones considered problematic for Fedora, so this shouldn't be a problem. Fixes: luv-yocto/#38 (From OE-Core rev: d493f0b4760808f880a0fd6dedf918a3b85006b7) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ovmf_git.bb: enable parallel compilationPatrick Ohly2017-03-011-2/+3
| | | | | | | | | | | | | | | | | | | The Fedora srpm [1] seems to have no problems with parallel compilation, so let's also use that for the target. The native tools however indeed have dependency problems: | test_Ecc_CParser (CheckPythonSyntax.Tests) ... gcc -o ../bin/EfiRom -L/fast/build/ostro/x86/tmp-glibc/sysroots/x86_64-linux/usr/lib -L/fast/build/ostro/x86/tmp-glibc/sysroots/x86_64-linux/lib -Wl,-rpath-link,/fast/build/ostro/x86/tmp-glibc/sysroots/x86_64-linux/usr/lib -Wl,-rpath-link,/fast/build/ostro/x86/tmp-glibc/sysroots/x86_64-linux/lib -Wl,-rpath,/fast/build/ostro/x86/tmp-glibc/sysroots/x86_64-linux/usr/lib -Wl,-rpath,/fast/build/ostro/x86/tmp-glibc/sysroots/x86_64-linux/lib -Wl,-O1 EfiRom.o -L../libs -lCommon | /usr/bin/ld: cannot find -lCommon | collect2: error: ld returned 1 exit status ERROR: Task (virtual:native:.../meta/recipes-core/ovmf/ovmf_git.bb:do_compile) failed with exit code '1' [1] https://src.fedoraproject.org/cgit/rpms/edk2.git/tree/edk2.spec (From OE-Core rev: be307609a067b7d23dc2cd8e39e3a35f770bebc7) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ovmf: deploy firmware in image directoryPatrick Ohly2017-03-011-11/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When used with '-drive if=pflash', qemu will store UEFI variables inside the firmware image file. That is unexpected for a file located in the sysroot, which should be read-only, while it is normal for image files in the deploy/images directory. Therefore that directory is a better place for use with runqemu. The name was chose so that "runqemu ovmf" can be used as shorthand for "runqemu <full path>/ovmf.qcow2" by treating "ovmf" as the base name of the firmware file. "ovmf.secboot.qcow2" is meant to be used for the Secure Boot enabled firmware. qcow2 is used because it is needed for "savevm" snapshots of a virtual machine. With code and variables stored in the same ovmf.qcow2 it is not possible to update the firmware code without also overwriting the variables. For users who care about persistent variables, the code and variables are also provided as separate files, in ovmf.code.qcow2 and ovmf.vars.qcow2. The traditional usage of OVMF via the qemu bios parameter ("biosdir" and/or "biosfilename" in runqemu) is no longer recommended, and therefore this recipe no longer provides the bios.bin file. Instead, OVMF is meant to be used as flash drive in qemu. See the "runqemu: support UEFI with OVMF firmware" patch for details on how to use OVMF that way. (From OE-Core rev: 6f84653e34b75a821fbf31b9f1aa912858e27f43) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ovmf: explicitly depend on nasm-nativePatrick Ohly2017-03-011-0/+2
| | | | | | | | | | Fixes a build issue when nasm was not build already because of something else. (From OE-Core rev: 92198bdda7add49f2c76ce55ab1f310e2128bf8f) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ovmf: move from meta-luv to OE-coremeta-luv2017-03-015-0/+350
| | | | | | | | | | | This is an unmodified copy of github.com/01org/luv-yocto/meta-luv/recipes-core/ovmf revision 4be4329. (From OE-Core rev: 49cdce8716ded0b612069d7614c3efe7724e5b40) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ncurses: 6.0+20160625 -> 6.0+20161126Hongxu Jia2017-02-232-1/+20
| | | | | | | | | | Add a patch to fix the CC/CFLAGS mangling that broke builds. [RB] (From OE-Core rev: e5d1cbbc1a04b0b190f3706e7ab7421c87d46c78) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dbus: do not use systemctl from host for configureAndy Kling2017-02-231-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | configure.ac from dbus uses $PATH to get the location of systemctl. If it is not found /usr/bin/systemctl is used. It is possible to override the location by passing SYSTEMCTL=[value] to configure. The value is used to replace @SYSTEMCTL@ in systemd-user/dbus.socket.in. dbus.socket sets the environment variable DBUS_SESSION_BUS_ADDRESS using systemctl. dbus does not depend on systemd-systemctl-native, so location from host installation or the default value gets used. Adding systemd-systemctl to the build would give path from sysroot. Forcing SYSTEMCTL=${base_bindir}/systemctl for target gives the correct path there and the environment variable is set after a user session was opened. [YOCTO #11002] (From OE-Core rev: e9471f8da3946439141ccdd8284200aa614df46c) Signed-off-by: Andy Kling <andreas.kling@peiker-cee.de> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gettext: fix formatting issuesRobert Yang2017-02-232-0/+88
| | | | | | | | | | | | | | | | | | | Fixed when compile with "-Wformat -Wformat-security -Werror=format-security": | gettext-tools/gnulib-lib/libcroco/cr-statement.c: In function 'cr_statement_dump_charset': | gettext-tools/gnulib-lib/libcroco/cr-statement.c:2661:17: error: format not a string literal and no format arguments [-Werror=format-security] | fprintf (a_fp, str) ; And: gettext-tools/gnulib-lib/libxml/timsort.h:326:80: warning: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'unsigned int' [-Wformat=] fprintf(stderr, "Error allocating temporary storage for tim sort: need %lu bytes", sizeof(SORT_TYPE) * new_size); [YOCTO #9544] (From OE-Core rev: 41eb2da1b05515e3803a331686fa6ca763ae2e69) 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>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-24 07:01:56 +0000