summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2018-12-27scripts/test-case-mgmt: enable manual execution and result creationsangeeta-tcmsMazliana
Integrated “manualexecution” operation to test-case-mgmt scripts. Manual execution script is a helper script to execute all manual test cases in baseline command, which consists of user guideline steps and the expected results. The last step will ask user to provide their input to execute result. The input options are passed/failed/blocked/skipped status. The result given will be written in testresults.json including log error from the user input and configuration if there is any.The output test result for json file is created by using OEQA library. The configuration part is manually key-in by the user. The system allow user to specify how many configuration they want to add and they need to define the required configuration name and value pair. In QA perspective, "configuration" means the test environments and parameters used during QA setup before testing can be carry out. Example of configurations: image used for boot up, host machine distro used, poky configurations, etc. The purpose of adding the configuration is to standardize the output test result format between automation and manual execution. To use these scripts, first source oe environment, then run the entry point script to look for help. $ test-case-mgmt To execute manual test cases, execute the below $ test-case-mgmt manualexecution <manualjsonfile> By default testresults.json store in <build_dir>/tmp/log/manual/ [YOCTO #12651] Signed-off-by: Mazliana <mazliana.mohamad@intel.com>
2018-12-27scripts/test-case-mgmt: store test result and reportingYeoh Ee Peng
These scripts were developed as an alternative testcase management tool to Testopia. Using these scripts, user can manage the testresults.json files generated by oeqa automated tests. Using the "store" operation, user can store multiple groups of test result each into individual git branch. Within each git branch, user can store multiple testresults.json files under different directories (eg. categorize directory by selftest-<distro>, runtime-<image>-<machine>). Then, using the "report" operation, user can view the test result summary for all available testresults.json files being stored that were grouped by directory and test configuration. The "report" operation expect the testresults.json file to use the json format below. { "<testresult_1>": { "configuration": { "<config_name_1>": "<config_value_1>", "<config_name_2>": "<config_value_2>", ... "<config_name_n>": "<config_value_n>", }, "result": { "<testcase_namespace_1>": { "status": "<PASSED or FAILED or ERROR or SKIPPED>", "log": "<failure or error logging>" }, "<testcase_namespace_2>": { "status": "<PASSED or FAILED or ERROR or SKIPPED>", "log": "<failure or error logging>" }, ... "<testcase_namespace_n>": { "status": "<PASSED or FAILED or ERROR or SKIPPED>", "log": "<failure or error logging>" }, } }, ... "<testresult_n>": { "configuration": { "<config_name_1>": "<config_value_1>", "<config_name_2>": "<config_value_2>", ... "<config_name_n>": "<config_value_n>", }, "result": { "<testcase_namespace_1>": { "status": "<PASSED or FAILED or ERROR or SKIPPED>", "log": "<failure or error logging>" }, "<testcase_namespace_2>": { "status": "<PASSED or FAILED or ERROR or SKIPPED>", "log": "<failure or error logging>" }, ... "<testcase_namespace_n>": { "status": "<PASSED or FAILED or ERROR or SKIPPED>", "log": "<failure or error logging>" }, } }, } To use these scripts, first source oe environment, then run the entry point script to look for help. $ test-case-mgmt To store test result from oeqa automated tests, execute the below $ test-case-mgmt store <source_dir> <git_branch> By default, test result will be stored at <top_dir>/testresults To store test result from oeqa automated tests under a specific directory, execute the below $ test-case-mgmt store <source_dir> <git_branch> -s <sub_directory> To view test report, execute the below $ test-case-mgmt view <git_branch> This scripts depends on scripts/oe-git-archive where it was facing error if gitpython package was not installed. Refer to [YOCTO# 13082] for more detail. [YOCTO# 12654] Signed-off-by: Yeoh Ee Peng <ee.peng.yeoh@intel.com>
2018-12-27scripts/oe-git-archive: fix non-existent key referencing errorYeoh Ee Peng
Without installing gitpython package, oe-git-archive will face error below, where it was referencing key that was non-existent inside metadata object. Traceback (most recent call last): File "<poky_dir>/scripts/oe-git-archive", line 271, in <module> sys.exit(main()) File "<poky_dir>/scripts/oe-git-archive", line 229, in main 'commit_count': metadata['layers']['meta']['commit_count'], KeyError: 'commit_count' Fix this error by checking the key existent from metadata before referencing it. [YOCTO# 13082] Signed-off-by: Yeoh Ee Peng <ee.peng.yeoh@intel.com>
2018-12-26glibc: Enable --with-default-linkKhem Raj
This lets linker to use its internal linker script for shared objects Fixes with when gold is default linker (From OE-Core rev: 7bbc453ac2b8d63680855789948a145fc448017f) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26base.bbclass, classextend.py: Drop catering to gcc-initialKhem Raj
(From OE-Core rev: 5d0307fbefbc8e6667edfa93d527166059a30100) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26tcmode-default: Drop pinnings for gcc-initial based recipesKhem Raj
(From OE-Core rev: 5b2fd1c72407d3024512982685d8b1227c2631af) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26musl: Move away from gcc-initial dependencyKhem Raj
gcc-initial step is no more needed (From OE-Core rev: fa47e2e65488dd03f94b1fefdeeb09f5e4a26373) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26libssp: Remove dependency on gcc-initialKhem Raj
Its not needed anymore and it can depend on gcc-cross instead (From OE-Core rev: 9dc6fcd492d41d6a65a8f5ab562830ba9372937a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26newlib: Move away from gcc-initial dependencyKhem Raj
gcc-initial step is no more needed (From OE-Core rev: 44539118ce29ba4fa916ab28ebf66e6fd5819738) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26recipes: Drop virtual/libc-for-gccRichard Purdie
We no longer have special "libc" for gcc so we can rely on plain virtual/libc and reduce the complexity in the dependencies. (From OE-Core rev: 122217b421f749b5fef52bea44ad6e04bc8f8d3a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26gcc: Drop the -initial versions of the compilerRichard Purdie
Separated out from the previous commit for clarity, this simply drops all the -inital pieces of gcc which are no longer needed after the previous commit. (From OE-Core rev: d84971928b68efddbdb6344b1021d998c9e26adb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26gcc: Drop gcc-cross-initial and use gcc-cross insteadRichard Purdie
We need a libgcc to build glibc. Tranditionally we therefore build a non-threaded and non-shared compiler (gcc-cross-initial), then use that to build libgcc-initial which is used to build glibc which we can then build gcc-cross and libgcc against. Firstly, we can drop the glibc dependency from gcc-cross, *if* we make two changes: a) specify the minimum glibc version to support in a configure option b) create a dummy limits.h file so that later when glibc creates one, the headers structure has support for it. We can do this with a simple empty file Once gcc-cross is libc independent, we can use it to build both libgcc-initial and then later libgcc. libgcc-initial is tricky as we need to imitate the non-threaded and non-shared case. We can do that by hacking the threading mode back to "single" even if gcc reports "posix" and disable libc presence for the libgcc-intial build. We have to create the dummy limits.h to avoid compiler errors from a missing header. glibc will fail to link with libgcc-initial due to a missing "exception handler" capable libgcc (libgcc_eh.a). Since we know glibc doesn't need any exception handler, we can safely symlink to libgcc.a. With those changes, gcc-cross can be used in all places and we only need one build of gcc for each architecture. For some reason ifunc was being disabled on mips prior to these changes but afterwards became enabled but caused assertion failures. This is therefore disabled until we can debug that. (From OE-Core rev: 62b7308b8c4d2b439a15a4f7cbc6f823077bb0be) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26glibc: Remove site_config and glibc-initialRichard Purdie
The only reason we appear to need glibc-initial at this time is to support the site_config code. The site_config code compiles and therefore needs at least some level of working C library to link against. This isn't a good reason to keep the complexity of glibc-initial around so remove it, and the site_config support which then breaks. Performance benchmarks suggest the time spent just rerunning configure for site_config just about equals any performance benefit for OE-Core image builds excluding the time spent adding glibc-initial to the dependency chain. I'm not opposed to readding some other form of site_config support but it needs to be rethought. (From OE-Core rev: c5df105e7583e43da9b682f739bebaf873dcd2f4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26crosssdk/cross-canadian: Set LIBCOVERRIDE correctlyRichard Purdie
(From OE-Core rev: 94bece16c23c9ec8850fd497aea37e6a265da30a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26oeqa/concurrencytest: fix for locating meta-selftestRobert Yang
The previous code assumed builddir and meta-selftest are in the same dir, but this isn't always true, builddir can be anywhere, use get_test_layer() to locate meta-selftest can fix the problem. (From OE-Core rev: 56d2493a9adfcc47ae7e265439e05ff42cdbbbbf) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26bitbake: process: Rewrite multiple connection handlingRichard Purdie
If the bitbake server recieved multiple connections, it currently closes ones it can't handle (while its dealing with another). This is rather antisocial behaviour which causes clients to quickly run through their retries and abort. Instead, queue any other connections until the current one is closed. This way the client can decide when it wants to stop waiting for the server. If the client is gone by the time we handle it, we handle that gracefully. This also fixes a number of bugs in the connection handling where connections which did drop early were badly handled causing tracebacks in the logs. Also, handle queue incomming connections in a loop to ensure that the main client handling doesn't starve that piece of the system. This code was stress tested by running 50 connection attempts in parallel at once, ensuring the code correctly handled them. (Bitbake rev: 02845a561b38658ac3edf5cc9c34625ed860d34f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26bitbake: process: Handle EWOULDBLOCK in socket connectRichard Purdie
Now that we set a timeout for the socket, it can return EWOULDBLOCK if a signal or other event happens to wake up even if we don't timeout. If this happens, retry the connection, else we simply see it quickly loop through the retries and abort the connection in a very short interval. (Bitbake rev: d5b0a9a302ac0eafa4f797ac15ea77db87e82b3c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26bitbake: main: When retrying the connection, show the attempt numberRichard Purdie
The current bitbake output makes it hard to know which retry is being attempted. Add this information to the output to make it clearer. (Bitbake rev: 0774e6e03d27adb7aca6fa9c47ab6ad426c937de) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26bitbake: process.py: Set socket timeout to 10 secondsRichard Purdie
The current value of 2 seconds has shown to be short in wider testing. (Bitbake rev: 8a1f2fcf35d61d83bbafa8fa3ae215fd5f51728b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-26bitbake: tests/persist_data: Add testsJoshua Watt
Adds a test suite for testing the persistent data cache [YOCTO #13030] (Bitbake rev: 96a4155049e834af17069d981cc2215e50d18c1a) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20populate_sdk_ext.bbclass: Include site.conf in parsing for contents for ↵Khem Raj
local.conf Some distros use site.conf to emit certain variables which are important for eSDK e.g. DISTRO with out which eSDK will not be able to ger right metadata when it tries to build (From OE-Core rev: 95659bed3f6f3216b346f70cfc9ffae9788c0fc1) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20i2c-tools: upgrade 4.0 -> 4.1Anuj Mittal
* For changes, see: https://git.kernel.org/pub/scm/utils/i2c-tools/i2c-tools.git/log/?qt=range&q=v4.0...v4.1 * Remove upstreamed patches (From OE-Core rev: 085530e8fff016d7cadcae4a769a82cddf9e6695) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20common-licenses: update Libpng license textAnuj Mittal
The new libpng license comprises the terms and conditions from the zlib license, and the disclaimer from the Boost license. The legacy libpng license license, used until libpng-1.6.35, is appended to the new license, following the precedent established in the Python Software Foundation License version 2. See for details: https://sourceforge.net/projects/libpng/files/libpng16/1.6.36/ (From OE-Core rev: 673c2dcf1045f7264570f81e2880d7a03befd2af) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20libpng: upgrade 1.6.35 -> 1.6.36Anuj Mittal
For changes, see: https://sourceforge.net/p/libpng/code/ci/libpng16/tree/CHANGES License-Update: Added authors to license, formatting, version changes, export classification clarification and a new libpng2 license with clarification: The new libpng license comprises the terms and conditions from the zlib license, and the disclaimer from the Boost license. The legacy libpng license license, used until libpng-1.6.35, is appended to the new license, following the precedent established in the Python Software Foundation License version 2. (From OE-Core rev: 099aecfaa3baf6b24c2b751da92d7d2fa0266bf9) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20harfbuzz: upgrade 2.1.3 -> 2.2.0Anuj Mittal
For changes, see: https://cgit.freedesktop.org/harfbuzz/tree/NEWS?h=2.2.0 Remove do_configure_append after the patch to remove pkg.m4 was merged upstream. (From OE-Core rev: 6574bb752335ce48b873d17b24496bfb669bfefe) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20sqlite3: upgrade 3.25.3 -> 3.26.0Anuj Mittal
For changes, see: https://www.sqlite.org/releaselog/3_26_0.html (From OE-Core rev: 8286e9d79dde1c951e92ac1c55bbf0b9798d9dbf) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20libatomic-ops: upgrade 7.6.6 -> 7.6.8Anuj Mittal
For changes, see: https://github.com/ivmai/libatomic_ops/compare/v7.6.6...v7.6.8 Also switch to using tarball release instead. (From OE-Core rev: a33170ff9a7abc5689e266e093069fd716c62622) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20gsettings-desktop-schemas: upgrade 3.28.0 -> 3.28.1Anuj Mittal
Changes from release notes: - Set default background image for screen lock to an existing one - Translation updates (From OE-Core rev: 6a10ff0bcd6e00660a419ca535239af55e30d5aa) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20eudev: upgrade 3.2.5 -> 3.2.7Anuj Mittal
For changes, see: https://github.com/gentoo/eudev/compare/v3.2.5...v3.2.7 (From OE-Core rev: dd2c4d9d85e70abacfa70fbe9281f393452875ea) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20icecc: patchelf is needed by icecc-create-envDouglas Royds
Although we could potentially build patchelf and all its dependencies, they would all have to be blacklisted to avoid trying to build them with icecc. We use the host patchelf instead. (From OE-Core rev: 0860216a81092fba084d29696db6d0c65a226c85) Signed-off-by: Douglas Royds <douglas.royds@taitradio.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20icecc: Don't generate recipe-sysroot symlinks at recipe-parsing timeDouglas Royds
The python function icecc_path() was being invoked inline by set_icecc_env(), meaning that it was being invoked at recipe-parsing time. As a side-effect, icecc_path() was creating the recipe-sysroot directory and symlinking icecc into it. Because this was done at parsing time (rather than configure time), we were generating otherwise-empty WORKDIRs for *all* parsed recipes, and for all virtual classes (-native, -nativesdk). In my build, this generated more than 800 of these otherwise-empty WORKDIRs. I have simplified icecc_path() to return only the intended path to the icecc symlinks in the recipe-sysroot, with no side-effect. We then create the directory and the icecc symlinks at configure time. Because get_cross_kernel_cc() is still invoked at parse-time, it needs a guard-clause for the non-kernel case. We are now finding the host icecc at do_configure time, so icecc needs to be in the HOSTTOOLS. I have made this non-fatal, so that we can still inherit icecc without icecc installed. (From OE-Core rev: d2fcaeb153fdc3f8d7143ea823139f1537055ff1) Signed-off-by: Douglas Royds <douglas.royds@taitradio.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20icecc: Syntax error meant that we weren't waiting for tarball generationDouglas Royds
If two bitbake processes try to generate the ICECC_VERSION tarball at the same time, the thread that fails to get the lock will wait 30 sec for the first to finish. A syntax error meant that this was not happening, and in particular, if tarball generation failed (eg. for lack of patchelf), it did so silently. (From OE-Core rev: 4455c46bf7f49c2b44f250aa89b63b342368e2e3) Signed-off-by: Douglas Royds <douglas.royds@taitradio.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20icecc: Trivial simplificationDouglas Royds
(From OE-Core rev: fa6bae80bc3392bf99ce53bbe19a0e05dbd0c4ee) Signed-off-by: Douglas Royds <douglas.royds@taitradio.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20icecc: readlink -f on the recipe-sysroot gcc/g++Douglas Royds
We were accidentally doing a readlink -f on simply 'gcc', for instance (From OE-Core rev: 6d6788a3ea45d9693743d9b3319fb0368a4d5d33) Signed-off-by: Douglas Royds <douglas.royds@taitradio.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20libxcrypt: Fix nativesdk build with gcc9Khem Raj
(From OE-Core rev: 1ee90ec89a8c2d0b639f76090c5f3da0c420d3a7) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-20gcc-runtime: Drop building libmpxKhem Raj
libmpx is not supported any longer and infact has been removed completely from gcc-9, see https://github.com/gcc-mirror/gcc/commit/1e42d5c637e1b1f65dfddd0923dfb25676bb56e5 (From OE-Core rev: 547174fc834273af67a2f7e50a3cf6c8e3b900f4) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-18linux-yocto-4.14: Drop bbappendRichard Purdie
(From meta-yocto rev: 5ec7bf02e21fd4137721184af41e1836b4a883ff) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-18poky-lsb: bump preferred kernel to 4.19Bruce Ashfield
(From meta-yocto rev: a612e5de9a6dbe08bb48ed5bd0cc3aa60a1954e7) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-18gcc-runtime: Add missing libc dependencyRichard Purdie
For reasons lost in the depths of time, perhaps performane related, we only have a dependency on libc at packaging time. This is too late, as demonstrated by a recent build failure on non-IA builds where the glibc 2.29 upgrade had been removed from the build: ld: recipe-sysroot/usr/lib/../lib/libstdc++.so: undefined reference to `log@GLIBC_2.29' libstdc++ should have been rebuilt but had not as the dependency wasn't present. Add the missing dependency to avoid this problem (and drop the other form of dependency which is no longer needed). (From OE-Core rev: 14c291e1fb6324da46885b69fbd7f01b3c6b053e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-18distrodata: RemoveRichard Purdie
The code in the tasks within this class are old and there are much better ways to do these things now such as through tinfoil rather than writing csv files incrementally with start/stop events and lock files. Existing users of the code (mainly the do_checkpkg task) have been ported over to tinfoil. Drop the class, any other users should also make use of the tinfoil functionality. (From OE-Core rev: 6e2a488f01e5e8bc6f06b6fac1d336bf5372a82b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-18scripts/distro: Remove as using obsolete APIs and need re-implementing sanelyRichard Purdie
(From OE-Core rev: 83d0049bb406e09251b368dba9478be71fe2b0a8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-18upstream-tracking.inc: Remove the long deprecated fileRichard Purdie
(From OE-Core rev: 22447eba250656489a6ed636fe58cb304d74e975) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-18oeqa/selftest/distrodata: Drop now unneeded distrodata inheritRichard Purdie
(From OE-Core rev: 1e03261d5e5e43ddda279750493f79aa865810c5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-18defaultsetup: Include maintainers.inc by defaultRichard Purdie
There is little harm in including this file rather than having a rather obscure and soon to be obsolete bbclass adding this information. (From OE-Core rev: 98536be8d1a5dcf620ee6d07135f23126a09d98f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-18libxcrypt: Upgrade to 4.4.1 releaseKhem Raj
License-Update: New files added to existing list Add -Wno-error=missing-attributes to compiler flags, this helps in compiling with gcc 9.0, eventually, the code should be fixed Add a patch to fix x32 build (From OE-Core rev: 59be9254df9ffeda594b21af8be433564c898474) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-18kernel-devsrc: fix usrmerge install pathAllen Wild
Update /lib to $nonarch_base_libdir to fix package QA errors when usermerge is enabled in DISTRO_FEATURES. ERROR: kernel-devsrc-1.0-r0 do_package_qa: QA Issue: kernel-devsrc package is not obeying usrmerge distro feature. /lib should be relocated to /usr. [usrmerge] (From OE-Core rev: a62085b5047e7943bdcc9d4ce3480d100618eeb1) Signed-off-by: Allen Wild <allenwild93@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-18systemd: Fix memory use after free errorsKhem Raj
Found with gcc trunk (From OE-Core rev: 381c63ad2a6e004658b0232b6e6763f49f412b2b) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-18go: Upgrade 1.11.1 -> 1.11.4 minor releaseKhem Raj
Changes: https://golang.org/doc/devel/release.html#go1.11 (From OE-Core rev: b964551a0d08aa921d4e0ceea2f1e28a5e83510e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-18linux-yocto: correct qemumips64el definitionBruce Ashfield
The big endian mips definition was used as the basis for the little endian machine. Unfortunatey, the KMACHINE definitions were not fully cleared, so big endian builds will match on the 'le' variant .. and break. We drop the BE machine definitions from the LE variant and we are fixed. (From OE-Core rev: 863e520059cdc96817ec87983d1e036f291bf37c) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-12-18linux-yocto: configuration updates (virtio and tpm)Bruce Ashfield
Integrating the following configuration changes: 1992fb4dad30 virtio.cfg: enable CONFIG_DRM_VIRTIO_GPU 9e9ba7cb6756 features/tpm: enable tpm support (From OE-Core rev: c4e273f6a2213ac898fbc504b9bfc12af633c9b8) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-30 08:27:56 +0000