summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* bind: fix build with python3 PACKAGECONFIG enabledChen Qi2019-08-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | If the PACKAGECONFIG item, python3, is enabled, we get the following QA issue when multilib is enabled. ERROR: bind-9.11.5-P4-r0 do_package: QA Issue: bind: Files/directories were installed but not shipped in any package: /usr/lib /usr/lib/python3.7 /usr/lib/python3.7/site-packages /usr/lib/python3.7/site-packages/isc-2.0-py3.7.egg-info /usr/lib/python3.7/site-packages/isc /usr/lib/python3.7/site-packages/isc/policy.py [snip] The thing is, when --with-python is specified with a path instead of 'yes', the --with-python-install-dir is in fact ignored. Fix this issue by specifying the correct arguments. (From OE-Core rev: 2c36b3e5c7caae07ffe0cfb816d37fad52d69fc9) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devsrc: update arm64 scripts/prepare for kernels 5.3+Bruce Ashfield2019-08-301-1/+3
| | | | | | | | | | We need to include a few more small files for on target module builds for 5.3+ kernels. (From OE-Core rev: 9b3134995cf054679d573f28f916a629332ce126) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: v5.3+ build fixesBruce Ashfield2019-08-301-0/+4
| | | | | | | | | | | | | | | | In the 5.3+ perf builds, there are multiple unistd.h files that need to be kept in sync. So not only do we update one, we update both to ensure that libc-headers and the perf build are in sync. perf checks some key files itself to be sure they are in sync, and bits.h can be out of sync. There's no build error that results with bits.h at the moment, but we still make sure they are in sync to avoid the configure/compile warning. (From OE-Core rev: b850ee597e7116cc2a7546853f2b976c891196ef) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: change dependencies on python to python3Bruce Ashfield2019-08-301-8/+11
| | | | | | | | | | | | | | | | | | | | The upstream kernel can now handle python3 for the perf scripts, coupled with the impending EOL of python2, we switch the dependencies in perf (scripting) to python3. Outside of dependency changes, we also pass the following two variables to the perf build: PYTHON=python3 PYTHON_CONFIG=python3-config. To ensure that our python3 components are used. For configurations that disable perf scripting, there is no change in behaviour. [YOCTO #13358] (From OE-Core rev: 584af667e0000129bcb5c9e8108485f2f6590eaf) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel-devsrc: remove python2 dependencyBruce Ashfield2019-08-301-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Witht the approaching EOL of python2, the kernel packages need to be updated to depend on python3. The core kernel scripts are now python3 safe, making the RDEPENDS change relatively simple. but There are some scripts that are captured in the devsrc files that are not used, but reference /usr/bin/python. The python3 package does not provide /usr/bin/python so any package managers with automatic dependency detection will fail to assemble a rootfs due to the missing intepreter. We could drop the scripts from the source capture, but that risks dropping something that we need in certain operations and we'd miss when they are updated in tree to explicitly call python3 (since they won't be revisited often). Light testing shows that the scripts do run with python3, so rather than removing them, we change the interpreter once they are copied, and automatic dependency detection won't cause us rootfs assembly issues. (From OE-Core rev: 6745088b6c9e5c70df59d667347ede470df9a91d) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez5: fix build against libc-headers 5.2+Bruce Ashfield2019-08-302-0/+69
| | | | | | | | | | | | | | | | | | | Backporting the following upstream commit to fix the build against kernel 5.2+ headers: [ Subject: [PATCH] tools: Fix build after y2038 changes in glibc The 32-bit SIOCGSTAMP has been deprecated. Use the deprecated name to fix the build. ] Upstream-Status: backport commit f36f71f60b1e68c0f12e615b9b128d089ec3dd19 (From OE-Core rev: b4731a1202cfa45c7e1f635552398b89a37f2eeb) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: reproducible: Do two clean buildsJoshua Watt2019-08-301-20/+28
| | | | | | | | | | | | | Perform two clean builds without sstate instead of one partial rebuild with sstate and one clean build without. There are some classes of reproducibility issues that this solves, and while we would like to resolve them in the long term the direction to do so is not currently clear. (From OE-Core rev: e97c529bfa4e1d0038ea44f15ee3298003daf981) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: Enable reproducible build testJoshua Watt2019-08-301-1/+0
| | | | | | | | | [YOCTO #13323] (From OE-Core rev: 3fc08155b72f711c48f9a667539305eea869b5e9) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: reproducible: Record packages in test resultsJoshua Watt2019-08-301-0/+10
| | | | | | | | | | | | | Records the results of the reproducibility analysis in the JSON test results file. This makes it easier to do post-test analysis on the packages. [YOCTO #13324] (From OE-Core rev: 6c357c8eee322163da96df676a54ff70a0bdc911) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: Set LD_LIBRARY_PATH when executing native commandsJoshua Watt2019-08-301-0/+3
| | | | | | | | | | | | | Some commands like to look for libraries at runtime manually (e.g. Python's ctype.utils.find_library() function). For this to work properly, the libraries in the native sysroot must be findable. To accomplish this, set LD_LIBRARY_PATH to search library paths in the native sysroot. (From OE-Core rev: 3a7305bdfded3c8988484c3f430110cc121123b5) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: reproducible: Use subTest for packagesJoshua Watt2019-08-301-10/+11
| | | | | | | | | | | Runs each package class reproducibility test in a separate sub-test. This allows the other sub tests to still run in the event that one fails. (From OE-Core rev: f0095e6c1b915e1e6ded111f4bf77fff0362e29a) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: reproducible: Cleanup reproducible buildJoshua Watt2019-08-301-3/+10
| | | | | | | | | | | | Cleans up the output from the reproducible build before building to ensure consistent results. Note that the output put is purposely left after around after the build so that non-reproducible packages can be diffed. (From OE-Core rev: f67bb34c8e7950779920b696f8502dbaed9eded5) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ltp: cve/meltdown.c: Fix kernel symbol findingHe Zhe2019-08-302-0/+82
| | | | | | | | | | Backport a patch to fix the following error. safe_file_ops.c:219: BROK: Expected 3 conversions got 2 at meltdown.c:272 (From OE-Core rev: 372a211657bfddd7f32f30043ec06198f8c27101) Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* common-licenses: update BSD-2-CLAUSE license textChristophe PRIOUZEAU2019-08-301-7/+4
| | | | | | | | | | Using the generic BSD-2-CLAUSE license as specified on https://opensource.org/licenses/BSD-2-Clause (From OE-Core rev: d532d19d35e19beb8d80ee38429562aa08cc9039) Signed-off-by: Christophe Priouzeau <christophe.priouzeau@st.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nfs-utils: 2.3.3 -> 2.4.1Robert Yang2019-08-308-268/+41
| | | | | | | | | | | | | | | | | | | | | - Remove 0001-Do-not-pass-null-pointer-to-freeaddrinfo.patch, the new api can check the pointer before free it. - Rmove 0001-makefile.am-update-the-path-of-libnfs.a.patch, it is already in the source. - Rmove nfs-utils-musl-limits.patch, it is already fixed. - Rebased the following patches: 0001-Makefile.am-fix-undefined-function-for-libnsm.a.patch 0001-configure.ac-Do-not-fatalize-Wmissing-prototypes.patch bugfix-adjust-statd-service-name.patch nfs-utils-musl-res_querydomain.patch (From OE-Core rev: 5601523e16ebd35d7de8d22ec5590618ea9f7ffb) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ccache: 3.7.1 -> 3.7.3Robert Yang2019-08-302-7/+7
| | | | | | | (From OE-Core rev: 891f69f0fea7376b6fe5de95af2b32219bfe6e31) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: disable gallium swrast driver on x86 x32Alexander Kanavin2019-08-302-1/+7
| | | | | | | | | It was found to crash the X server on startup under qemu. (From OE-Core rev: 045011ed29c0ab45892ad0881a4a8987f2adc977) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: set default RAM to 256M for all machinesAlexander Kanavin2019-08-305-6/+2
| | | | | | | | | | | | | | | | There was a discussion about what amount of RAM is appropriate for a default; the outcome was that for now it is still 256M. Some qemu machine definitions have however set this to 512M so for the sake of treating all architectures fairly, they are reset back to 256M. Also runqemu is adjusted to use 256M if QB_MEM is not set at all. http://lists.openembedded.org/pipermail/openembedded-core/2019-August/285900.html (From OE-Core rev: 04c01b6cc5be3e6d45d0e04571640648a5655a8b) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: resolve a host contamination issue for mono packagingAlexander Kanavin2019-08-302-0/+59
| | | | | | | | | | | This is perhaps not the most elegant patch but it be dropped once rpm is updated to the soon-to-be-released version 4.15 where upstream has removed mono dependency resolution altogether. (From OE-Core rev: c829e89f99c973787f31422b4c32eeebe8c383d3) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ca-certificates: Fix reproducibilty and multilib issueRichard Purdie2019-08-291-1/+1
| | | | | | | | | | | | | | This command was dependent on the order of files on the disk and for multilib builds could result in: Error: Transaction check error: file /etc/ca-certificates.conf conflicts between attempted installs of ca-certificates-20190110-r0.core2_32 and lib64-ca-certificates-20190110-r0.x86_64 Sorting the file makes things deterministic. (From OE-Core rev: c8f329fc562c9eecdcc1cb10d2c7661f44110fb4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky-altcfg: Replace poky-lsb with poky-altcfgRichard Purdie2019-08-293-13/+17
| | | | | | | | | | LSB has been removed, replace poky-lsb with poky-altcfg, a place where we can test different configurations on the autobuilder as well as showing an example of how to subclass a distro configuration. (From meta-yocto rev: 00fdefff55717331a220fe624f29c387970d31d7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Remove LSB support bitsAdrian Bunk2019-08-293-5/+2
| | | | | | | | | | | | LSB as a standard isn't current and isn't well suited to embedded anyway. Its putting artifical constraints on the system and with modern layer technology, would now be better off as its own layer. As such its time to split it out. (From meta-yocto rev: 8bb0237a74c2b66d0d0f19e600a5fb39df67894f) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* beaglebone: use the default of 256M rather than 512MAlexander Kanavin2019-08-291-1/+0
| | | | | | | | | | | This is done for the sake of using the same default everywhere; see here for details: http://lists.openembedded.org/pipermail/openembedded-core/2019-August/285900.html (From meta-yocto rev: f4ba98ed3c866ec3db90404f894d5aeaa5d79dfd) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Remove LSB supportAdrian Bunk2019-08-2928-1503/+50
| | | | | | | | | | | | | | | | LSB as a standard isn't current and isn't well suited to embedded anyway. Its putting artifical constraints on the system and with modern layer technology, would now be better off as its own layer. As such its time to split it out. The only part with some (marginal) usage is lsb_release, which is split from the lsb package into an own lsb-release package. (From OE-Core rev: fb064356af615d67d85b65942103bf943d84d290) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker.py: remove generation of recipe-depends.dotChen Qi2019-08-281-21/+4
| | | | | | | | | | | | | | | | | | | | | | The information of recipe-depends.dot is misleading. e.g. $ grep xz recipe-depends.dot | grep bzip2 "bzip2" -> "xz" "xz" -> "bzip2" Users would wonder why they get some circular dependency. The information is derived from removing the task names of task-depends.dot. It's not giving people any additonal information, and it's misleading. So we remove the generation of this file. (Bitbake rev: 4c484cc01e3eee7ab2ab0359fd680b4dbd31dc30) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: respect force flag in runall and runonlyJoshua Watt2019-08-281-14/+18
| | | | | | | | | | | | | | | | | Specifying the force flag will now cause runall and runonly to invalidate the tasks before running them. This allows a --runall or --runonly to force the tasks to run, even if they would have otherwise been skipped, e.g.: bitbake -f --runall fetch Will run all do_fetch tasks even if they wouldn't be necessary (for example, skipped by setscene) (Bitbake rev: 71e52d3822016027106f2a2e74b8dfdf20f5dc1e) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/lib/resulttool/report.py: Add more result typesNathan Rossi2019-08-281-3/+3
| | | | | | | | | | | Add additional result types into the dictionary to handle dejagnu style test results. These include PASS, FAIL, XPASS, XFAIL, UNSUPPORTED, UNTESTED, UNRESOLVED and ERROR. (From OE-Core rev: 684fc36402a23760b203f4761f284043031c799c) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/utils/nfs: Add unfs_server function to setup a userspace NFS serverNathan Rossi2019-08-282-2/+41
| | | | | | | | | | | | | | | | | | | | Add a nfs module into oeqa utils. This module provides unfs_server which allows a test case to build unfs3-native and setup the unfs server on a target directory of the host. This directory is then shared and can be mounted by the host or a target device attached to the host (e.g. qemu via tap or slirp). The nfs server is setup over UDP and automatically assigns user privileged ports. The function provides the UDP ports for the server as part of a returned python contextmanager which handles cleanup of the server process on completion or exception. Also add a 'udp' arg to get_free_port to get a free UDP port. Note: unfs3 still requires the host to have rpcbind or portmap running. (From OE-Core rev: c754fd85be85ad0a381b642365eca17cea8eb627) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Fix mips patch which changes default emulationNathan Rossi2019-08-281-6/+3
| | | | | | | | | | | | The patch incorrectly removes 'mips_elf32_ntrad_le_vec' from the 'targ_selvecs' replacing it with duplicate entries for 'mips_elf32_ntrad_be_vec'. Correct this so that the default binutils can still handle 'mips_elf32_ntrad_le_vec' binaries. (From OE-Core rev: cdd499f23c129306da879b6f614ca1b720724300) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* commands.py: fix typoChen Qi2019-08-281-1/+1
| | | | | | | (From OE-Core rev: 9b1c150573ffd0e68d37772d5f47482d86ddde6d) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libedit: fix failed to get historyChangqing Li2019-08-282-0/+35
| | | | | | | | | | | | | | | Reproduce steps: run fileman under examples, history command not work, nothing is output. Fix by increase history_offset when add history, if not, it will make current history event not align with offset, and cannot get history correctly. (From OE-Core rev: a1ff64bee270c151532e68a5151e622de71b5321) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bbtests.py: remove recipe-depends.dotChen Qi2019-08-281-1/+1
| | | | | | | | | | | This file is giving misleading information. There's a patch for bitbake to remove the generation of this file. Remove it from OEQA as well. (From OE-Core rev: 691a45265a6a451c4bc7720ef39d99b84342822a) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libffi: Make it build for MIPS o32Peter Kjellerstedt2019-08-282-0/+32
| | | | | | | | | | | | | | | This solves the following errors: src/mips/o32.S: Assembler messages: src/mips/o32.S:286: Error: opcode not supported on this processor: mips32r2 (mips32r2) `s.d $f12,((16*4)-10*4)($fp)' src/mips/o32.S:287: Error: opcode not supported on this processor: mips32r2 (mips32r2) `s.d $f14,((16*4)-8*4)($fp)' (From OE-Core rev: 250d85144c0118aebfce105f02425c25cb028087) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: Update to the latest 242 branchAdrian Bunk2019-08-286-247/+1
| | | | | | | | | Remove backported patches applied upstream. (From OE-Core rev: 5919729f1bd21ba8bf08ce02edb7cc3624c5d4b9) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-dtb.inc: RemoveAdrian Bunk2019-08-281-3/+0
| | | | | | | | | | It only printed a warning since Yocto 2.4, documented to be removed in a future release. (From OE-Core rev: 8976319d5ba0c9d4dbcee9b5226c105df30a2166) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: Print a buildtime warning about the status with muslAdrian Bunk2019-08-281-0/+6
| | | | | | | | | It is possible if a user really has to use it, but not recommended. (From OE-Core rev: 10c1a27501a32740a03c3c6c0684c7d24374af08) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sqlite3: explicitly set target endian-nessAndre McCurdy2019-08-281-1/+5
| | | | | | | | | | | Unless SQLITE_BYTEORDER is predefined, the code falls back to build time huristics - which are not always correct (e.g. in sqlite 3.28.0 big-endian ARM is mis-detected). (From OE-Core rev: c0fc43c228acd44499d9a1c257ec5e4cf42ed050) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sqlite3: make CFLAGS consistent across native, nativesdk and target casesAndre McCurdy2019-08-281-2/+2
| | | | | | | | | | | | | | | The previous simplification: https://git.openembedded.org/openembedded-core/commit/?id=604777acfc54d285f315b622bd147ed02d55d6fd looked OK but didn't actually work as expected. The native and nativesdk classes re-set CFLAGS after the += has been applied and so any modifications made via += are lost. Use _append instead. (From OE-Core rev: b02d83f7ffc72b96799a7964a90709eef02aa29d) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base-files: nsswitch.conf is glibc specificAndre McCurdy2019-08-281-1/+4
| | | | | | | (From OE-Core rev: e9f751a6fd6a4fc1cfac74202e1b71291aade705) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rootfs-postcommands.bbclass: add inittab tweak to read_only_rootfs_hook()Andre McCurdy2019-08-281-0/+5
| | | | | | | | | | | It's not clear that we actually need to call mount -o remount,XX from the busybox-inittab inittab at all, but as we currently do, let's respect read-only-rootfs in IMAGE_FEATURES and not remount / as rw. (From OE-Core rev: 8840a831d47a94f36bb2e173164dbaf9b955e809) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-boot: drop duplicate MACHINE_ESSENTIAL_EXTRA_RDEPENDS, etcAndre McCurdy2019-08-281-6/+0
| | | | | | | | | | | Default values for MACHINE_ESSENTIAL_EXTRA_RDEPENDS and MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS are set from bitbake.conf and so don't need to be duplicated in the packagegroup-core-boot recipe. (From OE-Core rev: 82983c94da2446ab86b189a0278156ee884d0976) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-ep9312.inc: fix TUNEVALID descriptionAndre McCurdy2019-08-281-1/+1
| | | | | | | (From OE-Core rev: 62afb4e79f3f8e491db290e5932a54f3dc3f962a) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-arm1176jz-s.inc: add support for arm1176jz-s CPU specific tuningAndre McCurdy2019-08-281-0/+17
| | | | | | | (From OE-Core rev: 95823b7eab141f8969367c4f9b76b73bf2e664dc) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-arm1136jf-s.inc: add hardfloat supportAndre McCurdy2019-08-281-1/+4
| | | | | | | (From OE-Core rev: 6e057cc367ab9cf82901ba8c7c3cfab35c4cb9ab) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: drop FETCHCMD, GITDIR, etc fetcher over-ridesAndre McCurdy2019-08-281-12/+0
| | | | | | | | | | | | | | This completes cleanup originally proposed in 2012: http://lists.openembedded.org/pipermail/openembedded-core/2012-July/064224.html Current versions of bitbake have "sane" default fetcher commands so it's no longer necessary for bitbake.conf to over-ride them. (From OE-Core rev: 4ff058226cfc3e7d5bf9a873d1de4475f65ef2f2) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: Remove PYTHONLSBOPTS that hasn't been set for some timeAdrian Bunk2019-08-281-1/+0
| | | | | | | (From OE-Core rev: 26f086834c05f97cbfd17fd16e003a89753dc995) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/recipes.txt: Stop documenting the long removed recipes-lsb4Adrian Bunk2019-08-281-1/+0
| | | | | | | (From OE-Core rev: 0d7d2afdad9f0a04c2090367107aa81e636a54b2) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* iputils: upgrade to s20190709Changhyeok Bae2019-08-284-145/+55
| | | | | | | | | build system is changed to meson. (From OE-Core rev: 3d2085642a8b4058ded6ab0c426feefc097f85c1) Signed-off-by: Changhyeok Bae <changhyeok.bae@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pip:upgrade 19.2.2 -> 19.2.3Zang Ruochen2019-08-281-2/+2
| | | | | | | (From OE-Core rev: f8901d9c2a019e37357e8d82e483948a1bdc7f5a) Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/kerneldevelopment: Able to apply a single patch to the Linux kernel sourceMazliana2019-08-281-0/+67
| | | | | | | | | | | | | | | | | | | | Purpose of kernel development is basically to customize our own recipes kernel by reused existing recipes.   This is an initiative of automating manual kernel development test cases. Applying a single patch to the Linux kernel source is one of the manual test cases of kernel development. Objective of this test is as a developer we can make changes of a file in kernel source and able to apply a single patch to the kernel source.   ref:https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases (From OE-Core rev: 00a5df641b94ef47eec36e742630db7b659102a4) Signed-off-by: Mazliana <mazliana.mohamad@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-11-16 12:13:09 +0000