summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2019-06-12util-linux: upgrade to 2.33.2ChenQi/util-linux-2.33.2Chen Qi
The license files' names are changed, but the contents remain the same. However, the LICENSE section of the recipe was wrong. This upgrade change the 'BSD' part to 'BSD-3-Clause & BSD-4-Clause'. Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
2019-06-11bitbake: cooker: Ensure mcdeps are processed even if only one multiconfigRichard Purdie
If you have no BBMULTICONFIG set but set mcdepends, they're currently ignored. We can handle them correctly with this small tweak. (Bitbake rev: 578f0c02f6a13f4315e7c2ce8b5e876dd2025055) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-11bitbake: build: implement custom progress handlers injected via OE_EXTRA_IMPORTSChris Laplante
A separate patch to base.bbclass (in poky) will add the OE_EXTRA_IMPORTS variable. The contents are appended into OE_IMPORTS. This provides a mechanism by which layers (in their layer.conf) can make custom progress handlers available. As a backup, individual recipes can inject progress handlers into __builtins__. Custom handlers are expected to have this __init__ signature: def __init__(self, d, outfile=None, otherargs=None): Recipes can then use the handlers like this: do_task[progress] = "custom:mylayer.util.ProgressHandler[:args]" The last part (everything after and including the second colon) is optional. If provided, it is passed to HandlerClass's __init__ as otherargs="args". Otherwise, otherargs=None. (Bitbake rev: 20289d62c84c393990dd3deb0cca1b17c09092e6) Signed-off-by: Chris Laplante <chris.laplante@agilent.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-11bitbake: build/progress: use context managers for progress handlersChris Laplante
It seems context management support was half-implemented, but never finished. For example, LogTee has __enter__ and __exit__ but they haven't been exercised until now. (Bitbake rev: bf522ad3e0c52cdb69b406226840d870ff4f2766) Signed-off-by: Chris Laplante <chris.laplante@agilent.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-11bitbake: build: extract progress handler creation logic into its own methodChris Laplante
(Bitbake rev: a841efa50d3aaf7c57446806327b2b687371cb29) Signed-off-by: Chris Laplante <chris.laplante@agilent.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-11bitbake: knotty: allow progress rate for indeterminate barsChris Laplante
(Bitbake rev: 85f0b443b7ab1848abc6eb658be489fc1718004c) Signed-off-by: Chris Laplante <chris.laplante@agilent.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-11kernel.bbclass: Make task clean depend on cleaning of make-mod-scriptsHaiqing Bai
The package 'make-mod-scripts' creates files in 'kernel-build-artifacts/include/config' which are removed by 'cleanall/cleansstate' of 'virtual/kernel'. And this causes the below error while building out of tree kernel module: ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing. Run 'make oldconfig && make prepare' on kernel src to fix it. Suggested-by: Jun Nie <jun.nie@linaro.org> (From OE-Core rev: f79c95f6a883e999e0c2ecfd60b6b696b7595497) Signed-off-by: Haiqing Bai <Haiqing.Bai@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-11tune-thunderx: Set the correct PACKAGE_EXTRA_ARCHS_tune-thunderxKevin Hao
The value of PACKAGE_EXTRA_ARCHS_tune-thunderx should be based on PACKAGE_EXTRA_ARCHS_tune-armv8a-crc-crypto instead of armv8a-crc-crypto. Otherwise we would get some sanity check error like this: OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: Error, the PACKAGE_ARCHS variable (all any noarch armv8a-crc-crypto thunderx qemuarm64) for DEFAULTTUNE (thunderx) does not contain TUNE_PKGARCH (aarch64) (From OE-Core rev: 13cc0f7c0bd98ea228e9bdf51043117d38837ce7) Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-11meta: license: fix non-SPDX license being removed from INCOMPATIBLE_LICENSEQuentin Schulz
A non-SPDX license (which is not an alias to an SPDX license) cannot currently be marked as incompatible in INCOMPATIBLE_LICENSE. In the current state, we take all INCOMPATIBLE_LICENSE and pass them through expand_wildcard_licenses which is only adding SPDX licenses that match the glob regexp of what is in INCOMPATIBLE_LICENSE (be it a direct match to an SPDX license or via an alias). This does not work well with custom licenses. E.g.: foo.bb: LICENSE = "FooLicense" conf/local.conf: INCOMPATIBLE_LICENSE = "FooLicense" `bitbake foo` Gives no warning, no error, builds and packages successfully, because INCOMPATIBLE_LICENSE is basically empty since FooLicense is neither in SPDXLICENSEMAP nor in SRC_DISTRIBUTE_LICENSES. Let's add the original licenses to the list returned by expand_wildcard_licenses to be able to handle the aforementioned case. INCOMPATIBLE_LICENSE = "FooLicense GPLv2 GPLv3+" used to "resolve" to "GPLv2 GPLv3". It now resolves to "FooLicense GPLv2 GPLv3 GPLv3+" which fixes the issue with custom licenses not being in SPDXLICENSEMAP or SRC_DISTRIBUTE_LICENSES and thus being left out of the blacklisted licenses. I needed to pass a list to expand_wildcard_licenses from the license_image class instead of the current output of map() because the operator [:] does not work on this kind of type, and list(map()) or anything that iterates over map() actually moves the iterator and breaks the forloop right after in expand_wildcard_licenses. (From OE-Core rev: 2d976587d703462db2b7b78661b05ac22fb93787) Signed-off-by: Quentin Schulz <quentin.schulz@streamunlimited.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-11wic/plugins: kernel image refer to KERNEL_IMAGETYPEChee Yang Lee
replaced hardcoded kernel image with KERNEL_IMAGETYPE. set kernel image to "bzImage" incase KERNEL_IMAGETYPE not set. (From OE-Core rev: 88a9fef761c5e67b2964fedc85a7e8ad37067564) Signed-off-by: Chee Yang Lee <chee.yang.lee@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-11json-c: Backport --disable-werror patch to allow compilation under iceccDouglas Royds via Openembedded-core
icecc preprocesses source files locally before shipping them off to be compiled on remote hosts. This preprocessing removes comments, including /* fallthough */ comments in switch statements that normally prevent an implicit-fallthrough warning, see https://github.com/icecc/icecream/issues/419 Rather than turning off -Werror, the upstream project has implemented a configure option, --disable-werror, in response to Ross's https://github.com/json-c/json-c/issues/489 This patch from https://github.com/json-c/json-c/commit/21c886534f8927fdc0fb5f8647394f3e0e0874b8 Upstream-Status: Backport [Not yet released] (From OE-Core rev: c668b467415599cb95d93a231eb51d77137a57e4) Signed-off-by: Douglas Royds <douglas.royds@taitradio.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-11dhcp:"dhclient -x eth0" action is not correct.Jiping Ma
The action of "dhclient -x eth0" and "dhclient -r eth0" is same when enable ENABLE_GENTLE_SHUTDOWN. Disable ENABLE_GENTLE_SHUTDOWN that will use the default signal hander. (From OE-Core rev: 8e5c85332f222efd5ffddaa9da9272c6e42881f5) Signed-off-by: Jiping Ma <jiping.ma2@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-11gstreamer1.0-python_1.16.0.bb: Override libpython dirJaewon Lee
As mentioned in upstream commit a2cf84affff8a78fdaa8fabcfa9b40be1936678e, "gstpythonplugin hardcodes the location of the libpython from the build workspace and then fails at runtime." In other words, PYTHON_LIB_LOC was set to the recipe-sysroot-native dir in the gstreamer1.0-python workspace on the host. Overriding PYTHON_LIB_LOC with /usr/lib by adding --with-libpython-dir=${libdir} to EXTRA_OECONF to fix this issue. The error that was seen is: ** (gst-plugin-scanner:2343): CRITICAL **: 23:08:18.327: Couldn't g_module_open libpython. Reason: ${project}/build/tmp/work/${arch}/ gstreamer1.0-python/1.14.4-r0/recipe-sysroot-native/usr/lib/libpython3.5m.so: cannot open shared object file: No such file or directory The comment continues and says "it still fails because it looks for a symlinked library ending in .so instead of the actually library with LIBNAME.so.MAJOR.MINOR. Although we could patch the code to use the path we want, it will break again if the library version ever changes." This isn't the case anymore as the package is deploying /usr/lib/gstreamer-1.0/libgstpython.cpython-37m-i386-linux-gnu.so, a versionless so. (From OE-Core rev: ac1d6d55e9cc647caf104e94465e32cf25647ad1) Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-10build-appliance-image: Update to master head revisionRichard Purdie
(From OE-Core rev: 86266dfcd70b8e3435d267538c3e6e4d69be829e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-10recipetool: add python3 supportMaciej Pijanowski
Add support for generating python3 recipes using the recipetool / devtool. Drop python2 support at the same time. Tested with: oe-selftest -r recipetool.RecipetoolTest [YOCTO #13264] (From OE-Core rev: d8b2f58974482b3b1ccc65c5f93104d0d7ba87bc) Signed-off-by: Maciej Pijanowski <maciej.pijanowski@3mdeb.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-10runqemu: QB_FSINFO to support fstype wic imagesAdrian Freihofer
wic images are handled as vmtype images. Starting qemu with "-kernel" parameter and an image of type wic is not supported. Especially for "-machine virt" the combination of wic with -kernel parameter would be beneficial. The new parameter QB_FSINFO allows to pass image type specific flags to runqemu. QB_FSINFO is a space separated list of parameters. Parameters are structured according to the following pattern: image-type:flag. For now two parameters are supported: - wic:no-kernel-in-fs The wic image is treated as rootfs only image. A -kernel option is passed to qemu. - wic:kernel-in-fs The wic image is treated as VM image including a bootloader and a kernel. This is still the default behavior. Example: QB_DEFAULT_FSTYPE = "wic" QB_FSINFO = "wic:no-kernel-in-fs" QB_KERNEL_ROOT = "/dev/vda1" QB_SYSTEM_NAME = "qemu-system-aarch64" QB_MACHINE = "-machine virt" ... [YOCTO #13336] (From OE-Core rev: 2aa79a67affd22dfa37e4c2945c6ab0c86321f98) Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-10bitbake: cooker: Add compability handling for multiconfig: prefix migrationRichard Purdie
This allows "multiconfig:" targets to continue to work by internally mapping them to the new "mc:" naming, allowing older builds to work as before. (Bitbake rev: c4d90890547af642e99cc541af3415df3559563e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-10bitbake: multiconfig: Switch from 'multiconfig' -> 'mc'Richard Purdie
After real world use its clear the "multiconfig:" prefix to multiconfig tasks, whilst clear, is also clumbersome. Switch to use the short version instead. mcdepends will continue to work with "multiconfig:" for now as well. The commandline will only accept mc: going forward. [YOCTO #11168] (Bitbake rev: 821daf093b76504067a8b77dfa4b181af6ec92b4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-10multiconfig: Adapt to bitbake switch 'multiconfig' -> 'mc'Richard Purdie
(From OE-Core rev: 8a6f7c1e455156966f467008645fef14db679ccf) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-10oeqa: Add reproducible build selftestJoshua Watt
Adds an initial test for reproducible builds to the OE selftest. This initial test builds core-image-minimal using sstate, then does a clean build without sstate in another build directory, and finally does a binary comparison of the resulting package files between the two builds. The test is currently always skipped since it doesn't pass yet, but it can easily be enabled locally (From OE-Core rev: 2e591bdf93ec9e59b900562263dfe8e72b163baa) Signed-off-by: Joshua Watt <JPEWHacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-10bitbake: toaster: Fix Thud Bitbake release metadataDavid Reyna
Fix the Bitbake version ID for Thud (1.40). [YOCTO #13356] (Bitbake rev: 7d0ab11a0d1a2510515d7ebab66b922fbfc411c3) Signed-off-by: David Reyna <David.Reyna@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08base.bbclass: Add OE_EXTRA_IMPORTSChris Laplante
OE_IMPORTS is not intended to be touched by users, but there are cases in which layers might want to make additional Python modules available to Python functions. For example, Python modules defined in the layer themselves (under meta-layer/lib). (From OE-Core rev: 00fa8391365863fa7805ad61b2d1a8425b9ea040) Signed-off-by: Chris Laplante <chris.laplante@agilent.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08testimage: consider QB_DEFAULT_FSTYPEAdrian Freihofer
testimage.bbclass starts qemu with the first image type found in the IMAGE_FSTYPES list. It's weird: this ['wic', 'tar'] works but this ['tar'. 'wic'] does not. If QB_DEFAULT_FSTYPE is defined, this fstype is booted. (From OE-Core rev: aedb6bf9b6ccf37f69372642bc4c5dbbca92d0d9) Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08qemurunner: fix undefined variableAdrian Freihofer
While hacking on this I got an Exception. It's better to define variables also in python. Signe:-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> (From OE-Core rev: 1ea225a86cdee4ed932ede509d3351d5aecae497) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08oeqa/runtime: add simple test for sconsTim Orling
This test simply compiles a hello world program using scons. (From OE-Core rev: bf6e3f0f3a7a134e8e3cb16366ef01b8c956e4c8) Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08serf: switch to python3-scons-nativeTim Orling
SCons has supported python3 since v3.0.0, use it. (From OE-Core rev: e1de553bb2c1885f8323d9ce31b35175d5da3ef2) Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08scons.bbclass: use python3-sconsTim Orling
SCons has supported python3 since 3.0.0 release, use it. [YOCTO #13381] (From OE-Core rev: 2ce507d65cd2558edc9e7929aff7b80463c26998) Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08python3-scons-{native}: add recipe for v3.0.5Tim Orling
SCons has supported python 3 since v3.0.0 https://scons.org/tag/releases.html Fix shebangs in scripts [YOCTO #13381] (From OE-Core rev: 1873f777aeddfbbf3ce06e93df3fa5318decb7b7) Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08openssh: Document skipped test dependencyRichard Purdie
In minimal images the agent-ptrace test is skipped unless gdb is installed which explains the difference in test counts. We don't want a build dependency on gdb and the test isn't critical so just document the dependency. (From OE-Core rev: d3f29e6e52367e124e3f543f970038c0332ad3e1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08gawk: ptest fixesRichard Purdie
In minimal images all tests pass due to a missing dependency on make. Add the missing dependecy. The test list created by the run-ptest script is incorrect as it includes entries like "fi". Simplify it and correct it. Some tests are skipped due to mpfr not being enabled. Correctly mark these as SKIP. Some tests need the "../gawk" script, create a link to it so the tests work correctly. Also print more information in the failed test cases. (From OE-Core rev: 8392d60e05c4eed0b08273c1a934eeea54215079) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08parted: drop patch for linux <2.6.20 supportRoss Burton
We don't really care about kernels this old anymore, so drop the patch. (From OE-Core rev: b9630048451342a0ca1080955b0df35b0c94ce46) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08parted: swap patches for the commits that landed upstreamRoss Burton
Several of the parted fixes are actually upstream in slightly different form. (From OE-Core rev: 90e032a4dc8e7d56db667d35a15cbf30b9fcdf06) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08libxslt: add comment saying when a workaround can be removedRoss Burton
(From OE-Core rev: 0dc31cb680ecb07f013ae110cff688c62f20573b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08glib-2.0: udpate 2.58.3 -> 2.60.3Alexander Kanavin
Drop autotools-specific parts from patches, as all autotools files have been removed upstream (meson is now the only option). Remove autotools-specific 0001-Revert-Use-absolute-paths-in-pkg-config-files.patch Remove backported fix-nl-abaltmon.patch Add a hunk to Enable-more-tests-while-cross-compiling.patch which comments out the part of the tests that hard-codes native ld for building. (From OE-Core rev: c7479bfd5fad4b9ba2e4299048a0c432200a5204) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08mesa: Update 19.0.5 -> 19.0.6Fabio Berton
Mesa 19.0.6 is a bug fix release which fixes bugs found since the 19.0.5 release. For full log see: - https://www.mesa3d.org/relnotes/19.0.6.html (From OE-Core rev: 1e4a5fe4652bd957d822d0d3d6e7c8b7b4ff5b8e) Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-08wic/filemap: handle FIGETBSZ failingRoss Burton
Some file systems don't support fetching the block size (notably the file system Docker uses for containers), so handle the iotctl() failing and raise the expected error. (From OE-Core rev: 3757073726a00c5250556aae3d0daac76b88085e) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-07ref-manual: Grammar correctionScott Rifenbark
I left out the word "not" in a key sentence in the new "Checking on the Upgrade Status of a Recipe" section. Little words can make big differences. (From yocto-docs rev: 46a524a0d6c9e2ed6428039a4454e384a6ef648d) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-07ref-manual: Updates to check-recipe-upgrade devtool commandScott Rifenbark
I updated the section to include more detail on what the user sees in the returned table. (From yocto-docs rev: 671279548dde7f356888ba1ad1551b8bb1f70a65) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-07ref-manual: do_checkpkg - added link to checking upgrade statusScott Rifenbark
I show the "devtool check-upgrade-status" command as part of the "do_checkpkg" task section. I added a cross-reference link to the "Checking on the Upgrade Status of a Recipe" section in the ref-manual. (From yocto-docs rev: 034054f431cc9f0e61c8e156eed66bdf6e1198a1) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-07dev-manual: Added check-upgrade-status blurb to upgrading recipesScott Rifenbark
The section "Upgrading Recipes" covers several ways of upgrading a recipe. I added some stuff in the introductory area that mentions the fact a user might want to check the upgrade status of a recipe first. (From yocto-docs rev: bd2fd8d0a91b64455c282ebf4974e40874274f46) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-07ref-manual: New section "Checking Upgrade Status of a Recipe"Scott Rifenbark
I added a new section showcasing the "devtool check-upgrade-status" command. Also, added a note in the "Upgrading a Recipe" section" to tell the reader they might want to check on a recipe's upgrade status before upgrading a recipe. (From yocto-docs rev: 974f63fe8836fccd51f12b511c23644235cbd4b4) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-07ref-manual: Udated devtool help output examples.Scott Rifenbark
Specifically missing was the "devtool check-upgrade-status" command. (From yocto-docs rev: beaa40e8d1037f237ab588ec6ce256b8c3a18543) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-07ref-manual: Removed "distutils-tools" class.Scott Rifenbark
This class was removed for 2.7 and I took the reference section out of the class area. (From yocto-docs rev: daf786bebb0286d2ced46c97957d80a94c921c56) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-07ref-manual: Removed bugzilla.bbclassScott Rifenbark
The migration section noted this class as becoming obsolete. I removed it from the class reference section. (From yocto-docs rev: 63128888242493fb5671f11a2e5e470f2da6b22a) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-07dev-manual, ref-manual: removed "distrodata" classScott Rifenbark
Ousted these since it was noted in the migration section that the class had been removed. Modified all references to the removed class as needed. (From yocto-docs rev: 7000acc76da6b7ee850b799347ab9083663c7e6a) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-07ref-manual: Updated "do_fetch" to have a link to "Fetchers"Scott Rifenbark
Fixes [YOCTO #10098] This task needed to cross-reference the "Fetchers" section, which is in the BitBake User Manual. (From yocto-docs rev: c8862f4c8cc43777acead0e93fc728f2e8be4641) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-07sdk-manual: Added link to BB manual fetcher section.Scott Rifenbark
In the "Use devtool upgrade to Create a Version of the Recipe that Supports a Newer Version of the Software" section, we reference "fetchers" but do not link to the section on them in the BB manual. I added a link. (From yocto-docs rev: 633ac78daa2ab3bdde17ecb1a203f6addd6ee4af) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-07ref-manual: Remove irda featureAdrian Bunk
IrDA support was removed in upstream kernel 4.17, and irda-utils as well as the feature are now also removed. (From yocto-docs rev: 5650b3c733310b4d478440449d427de417946c81) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-07gnutls: Use the sysconfdir variable for the ca-certificates pathPhilippe Normand
(From OE-Core rev: 666f6192aaa9e847ad0d920a487b82d984b58d26) Signed-off-by: Philippe Normand <philn@igalia.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-06-07slang: modify an array testJoe Slater
One array test attempts to create an array that is far too large to exist. Different exceptions are thrown for 32 and 64 bit machines, so we account for that when catching them. (From OE-Core rev: 03e3721674fe7fc22911ec738524cef86c7a5357) Signed-off-by: Joe Slater <joe.slater@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-05-20 07:43:41 +0000