summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
* linux-yocto: nf_tables: Add nf_tables featureBruce Ashfield2015-10-273-3/+3
| | | | | | | | | Updating the META SRCREVs to make the nf_tables feature available. (From OE-Core rev: 43ed2494ae4f89cab6e018f289bb048289d478f5) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.19: fix ARM boot with gcc5.xBruce Ashfield2015-10-271-2/+2
| | | | | | | | | | | | Updating the SRCREVs to apply the same fix as 3.14 and 4.1 already have to fix qemuarm boots with gcc5.x [YOCTO: #8415] (From OE-Core rev: fa9852d5d7383e6d03c756b8ad615668857b0b86) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: skip kernel meta data branches when finding machine branchBruce Ashfield2015-10-271-1/+3
| | | | | | | | | | | | | | | | | | | | | | Before the fetcher validated the specified SRCREV was reachable on a specified branch, linux-yocto style kernel's were comparing the value of KBRANCH and branch on the SRC_URI and then allowing a SRC_URI specified branch to override KBRANCH. With the introduction of kernel meta data on the SRC_URI, this routine is incorrectly picking up a kernel-cache repository and then attempting to apply that branch information to the kernel repository. The rationalization of the branch specification is largely no longer required, and will may be removed in the future. But for now, to keep changes minimal, we can simply not return branch information that comes from kernel meta data by checking the 'type' parameter and skipping if it is of type 'kmeta'. (From OE-Core rev: 87363ec019e04b486dee5f07b7226465be7acd6c) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kern-tools: avoid duplicate .scc file processingBruce Ashfield2015-10-271-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | With the recent changes to improve patch processing times, the ability to skip already applied patches is not active by default. The automatic detection and resume was hiding issues with the include files generated by scripts like yocto-bsp. If a .scc file that contains a patch is included twice, the patch is applied twice, and the second appliation fails for obvious reasons. We can partially fix this by ensuring that already included configuration fragments are not forced into the meta-series. .scc files that are explicitly listed twice will continue to fail, and recipes must be modified to avoid this. [YOCTO: #8486] (From OE-Core rev: ed2da98bf3ac798009f58a53b91285b4dac69d5a) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/4.1: drm/i915: Fix the VBT child device parsing for BSWBruce Ashfield2015-10-273-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updating the 4.1 SRCREVs to integrate the following fix: [ drm/i915: Fix the VBT child device parsing for BSW Recent BSW VBT has a VBT child device size 37 bytes instead of the 33 bytes our code assumes. This means we fail to parse the VBT and thus fail to detect eDP ports properly and just register them as DP ports instead. Fix it up by using the reported child device size from the VBT instead of assuming it matches out struct defintions. The latest spec I have shows that the child device size should be 36 bytes for rev >= 195, however on my BSW the size is actually 37 bytes. And our current struct definition is 33 bytes. Feels like the entire VBT parses would need to be rewritten to handle changes in the layout better, but for now I've decided to do just the bare minimum to get my eDP port back. Cc: Vijay Purushothaman <vijay.a.purushothaman@linux.intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Reviewed-by: Damien Lespiau <damien.lespiau@intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> (cherry picked from commit 90e4f1592bb6e82f6690f0e05a8aadcf04d7bce7) Signed-off-by: abdul arif abdul muttalib <abdul.arif.b.abdul.muttalib@intel.com> Signed-off-by: Tan Jui Nee <jui.nee.tan@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> ] (From OE-Core rev: 1f575df04f003c1e1fe9413f95023c20a2f30e19) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: axxia configuration updatesBruce Ashfield2015-10-276-6/+6
| | | | | | | | | | Updating the configuration fragments for the Intel Axxia on the 3.14 and 4.1 kernels. (From OE-Core rev: a4964955257a1ab2586fd5efeedc2e32b725895d) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to jethro head revisionRichard Purdie2015-10-211-1/+1
| | | | | | (From OE-Core rev: 73f8a0bf3b99d480bf97e266da0fb048714b4caf) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* archiver.bbclass: Fixes and improves archiver class for kernel and gcc packagesAlejandro Hernandez2015-10-211-7/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | gcc packages use a shared source directory, this causes an issue since the archiver will try to patch the same source several times (one for each gcc package), producing an error, the archiver class used stamp-base to check this, nonetheless our gcc packages no longer use stamp-base, they use gcc-shared instead, which is what broke this functionality. This patch adds a check to see whether or not the source should be patched, avoiding patching the source when it shouldn't. Also, we dont need to create multiple identical tarballs for all gcc packages, this patch fixes this and creates a single source tarball for gcc. When requesting patched sources, a race condition is created for linux-yocto tasks, unpack_and_patch is executed along with kernel_configme, which most of the time causes errors during configure, since kernel_configme task is specific to the kernel, simply modifying the tasks order by creating a dependency to kernel_configme was impossible, causing errors on all other packages that didnt use kernel_configme, this is fixed by creating a special case for the kernel, adding tasks with correct dependencies, avoiding the race condition and behaving the way it should for all other packages as well. [YOCTO #8378] (From OE-Core rev: aecaa0e8739db1c228a6db78225a717d9f348a5b) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest: improve config writing and cleanupRoss Burton2015-10-213-20/+9
| | | | | | | | | | | | | | | | The selftest.inc configuration file is deleted in both tearDown() and setUp() so there's no need to use addCleanup() to remove statements from it. Use write_config instead of append_config if the intention is to start from an empty config file, for clarity. Finally remove some misleading comments that claim that append_config() writes to local.conf when it doesn't. (From OE-Core rev: ad33259b507914bfc8de92d1df12e0974157900e) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/wic: remove numbers from test namesRoss Burton2015-10-211-23/+23
| | | | | | | | | | There isn't any required ordering of tests, and the numbers meant that the tests didn't appear in oe-selftest --list-classes. (From OE-Core rev: 2a4ecc88ca10ef6abe55dddb96842b579b73497c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest: clean up selftest.inc in teardownRoss Burton2015-10-211-1/+1
| | | | | | | | | | | | | | | Test cases may want to do call bitbake in setUpClass() but at that point the previous selftest.inc is still present which could change the build configuration and result in any built artifacts being removed in the next bitbake invocation as part of the sysroot clean up. Resolve this by cleaning selftest.inc in the tearDown, the clean in setUp should be considered a safety net. (From OE-Core rev: 573bd03a7844a5ad762533f65f41214df31cd197) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/wic: fix cleaningRoss Burton2015-10-211-11/+8
| | | | | | | | | | | | | In some situations the native tools built in setUpClass() are wiped from the sysroot by the time the tests are executed, likely due to the cleanup performed in the base setUp() method. Avoid this by doing all of the preparatory building in setUpLocal. (From OE-Core rev: 2285ff17a391fa22f2095da701bc6f2c9615ae7b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/wic: corrected testcase decorator for test18_iso_imageDaniel Istrate2015-10-211-1/+1
| | | | | | | | | | Changed testcase decorator for TC test18_iso_image from 1264 to 1346. (From OE-Core rev: b845330133de6d47b63a03208aa083cf08801634) Signed-off-by: Daniel Istrate <daniel.alexandrux.istrate@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest: verify that devtool can use plugins in other layersRoss Burton2015-10-211-0/+12
| | | | | | | | | | | In selftest we want to exercise devtool's ability to use plugins from other layers, so add a basic command to reverse a string to meta-selftest and a test in oe-selftest to call it. (From OE-Core rev: 69f5bbc1041e15691af0b4845e2136957a4846a1) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/buildoptions: Use the correct script for cleaning the workdirLeonardo Sandoval2015-10-211-2/+2
| | | | | | | | | | The script 'cleanupworkdir' does not exit, so changing it to 'cleanup-workdir'. (From OE-Core rev: 9a2292a995de9f93e742bda6c465daa854279fed) 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>
* oeqa/selftest/bbtests: Updated bitbake TCsDaniel Istrate2015-10-211-10/+35
| | | | | | | | | | | | | | | | | | | | - Added new TC test_force_task_1 (1354); check that do_package_write_rpm() re-executes upon changes in package image. - Updated TC test_force_task_2 (163); changed test recipe to zlib and added do_package() to the task execution list. - Removed unnecessary imports. Fix for bug [YOCTO #5875]. (From OE-Core rev: 86a7e68803aca58feca9b6cf479552d14b00996c) Signed-off-by: Daniel Istrate <daniel.alexandrux.istrate@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/bbtests: clean up local DL_DIR/SSTATE_DIR safelyRoss Burton2015-10-211-1/+5
| | | | | | | | | | | | | | Now that the selftests clean selftest.inc in the tearDown using bitbake in a function passed to addCleanup (which happens after teardown) will use the default configuration and not the customised one. As the intention was to clean away the temporary DL_DIR and SSTATE_DIR, simple use track_for_cleanup to delete the entire directory instead. (From OE-Core rev: aa3b859524bb693d3b150a8873a2ee24c78eac0a) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/utils/ftools: From functions that expect data, check if NoneLeonardo Sandoval2015-10-211-0/+9
| | | | | | | | | | | ftools functions that expect data may get 'None'; this patch does this check and return immediately if this is the case. (From OE-Core rev: 5eaa4fa30e2362e6dd572b8a6f7a909b608e14bf) 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>
* oeqa/utils/ftools: Ignore the exception if file does not existLeonardo Sandoval2015-10-211-1/+10
| | | | | | | | | | | | | | There may be cases where the configuration file (path) does not exist, thus the remove_from_file should catch this exception. In case the exception is not the latter (errno.ENOENT), then re-raise it. [YOCTO #8540] (From OE-Core rev: 1136f9e02d9cbe2c2cda189321d72b763649ba42) 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>
* oeqa/selftest/manifest.py: Test support for manifestsBenjamin Esquivel2015-10-211-0/+163
| | | | | | | | | | | | | | | | | | | | | | | | adding support for tests to verify that manifest contents contain entries that exist in an specified pkgdata dir tests added: - manifest.VerifyManifest.test_image_manifest_entries - manifest.VerifyManifest.test_SDK_manifest_entries test support written for future tests: -adding a setUpClass that supports other manifest tests -a get dir from bb var function that verifies if the dir exists -a ManifestEntry class defined with missing items list -check for the paths and fail gracefully if not there -debug prints for failure analysis [YOCTO#8028] (From OE-Core rev: aed5b7aef33459f1bb5fa29560920c254a5fd637) Signed-off-by: Benjamin Esquivel <benjamin.esquivel@linux.intel.com> Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* useradd_base.bbclass: Do not warn without a reasonPeter Kjellerstedt2015-10-211-3/+3
| | | | | | | | | | | | | | | | In c0da4270c76375a7a8cbcc09319fe4570ebbc5bd two bbwarn were changed to bbnote for the case where an added user or group already exists. The same should have been done for groupmems, groupdel and userdel as well since the warnings that are currently generated are superflouous. The two remaining similar bbwarn for groupmod and usermod are left as is since there they actually make sense. (From OE-Core rev: f775e4cffe45edb673a414a2038c4f2b09b9b827) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: disable ValgrindRoss Burton2015-10-212-0/+20
| | | | | | | | | | | Qemu has an automatic dependency on valgrind which cannot be disabled, which causes non-deterministic builds and build failures. As Valgrind wasn't enabled previously make this deterministic by forcibly disabling it. (From OE-Core rev: 33960902b9c36575ddda3d926d70fa13bbad85f6) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* i2c-tools: fix inverted RDEPENDSMatt Madison2015-10-211-2/+1
| | | | | | | | | | | | The runtime dependency between i2c-tools and i2c-tools-misc was backwards when the packages were split. With this change, including i2c-tools in an image no longer drags in perl. (From OE-Core rev: e1837b51e4054a725ce01007f27544ee21db79ef) Signed-off-by: Matt Madison <matt@madison.systems> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: remove spurious build dependenciesRoss Burton2015-10-211-1/+1
| | | | | | | | | | | make, patch and binutils are assumed to exist on the host, so there's no need to have them in DEPENDS and can result in the building of make-native for no good reason. (From OE-Core rev: 4f48eeb9396ef904202ab1abeb38ec971feaeb4b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-5.2: Fix various _FOR_BUILD and related variablesMark Hatle2015-10-212-0/+124
| | | | | | | | | | | | | | | | | | When doing a FOR_BUILD thing, you have to override CFLAGS with CFLAGS_FOR_BUILD. And if you use C++, you also have to override CXXFLAGS with CXXFLAGS_FOR_BUILD. Without this, when building for mingw, you end up trying to use the mingw headers for a host build. The same goes for other variables as well, such as CPPFLAGS, CPP, and GMPINC. (From OE-Core rev: 85ca40c42950315f2783b98f57df16b261d2826e) Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sudo: fix file permission for /etc/pam.d/sudoChen Qi2015-10-211-1/+1
| | | | | | | | | | The file permission should be 0644 instead of 0664. (From OE-Core rev: 86c80f6d51b3700e090c70067808ea405d5a0b20) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssh: fix file permission for /etc/pam.d/sshdChen Qi2015-10-211-1/+1
| | | | | | | | | | The file permission should be 0644 instead of 0755. (From OE-Core rev: 38567f910130f8559c2ba6935e0bfad61f6b1f4f) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity.bbclass: expand warning when chmod failsAlex Franco2015-10-211-2/+2
| | | | | | | | | | | | | As suggested, add exception message to warning in sanity.bbclass when chmod fails on TMPDIR. [YOCTO #7669] (From OE-Core rev: f6609aca5c533325411567a79130114654c50f3b) Signed-off-by: Alex Franco <alejandro.franco@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate SDK: prepare calling of bb.utils for exceptionsBenjamin Esquivel2015-10-211-24/+52
| | | | | | | | | | | | | | | | | bb.utils.remove, bb.utils.movefile and bb.utils.mkdirhier can throw exceptions that need handling and proper error messages more work is required for these methods to handle properly the exceptions that can be raised within the various OS calls they make but this is a start to at least not hide the errors in the requested operations [YOCTO#8213] (From OE-Core rev: 2e81dbdce6f92908c4d4c980af032516581178de) Signed-off-by: Benjamin Esquivel <benjamin.esquivel@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: handle virtual providersPaul Eggleton2015-10-212-1/+37
| | | | | | | | | | | | | | For modify / extract / upgrade, if the specified "recipe" is not actually a recipe but a virtual target such as virtual/kernel, map it correctly to the actual recipe and make sure we use that name within the workspace. Thanks to Chris Larson for reminding me this was still broken and for a hint on how to fix it. (From OE-Core rev: 1f7752282ffb47d2621030ddb2fa42a5e491d6d2) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libc-package: Fix localedef multilib dependency issuesRichard Purdie2015-10-201-2/+2
| | | | | | | | | | | | | Building nativesdk-glibc-locale results in many messages like: QA Issue: nativesdk-locale-base-en-sg rdepends on localedef, but it isn't a build dependency? [build-deps] It should depend on ${MLPREFIX}localedef, not just localedef to fix these warnings. (From OE-Core rev: 80e2dfbfef2d40c3ab074142deac73317f89e3a2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-shar-extract.sh: print full-length title underlinePaul Eggleton2015-10-201-2/+3
| | | | | | | | | Print a line that's the full length of the title that it's underneath. (From OE-Core rev: 83729437c584fc74577a2b15dbb2ae094788339d) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_ext: detect and warn if running in OE environmentPaul Eggleton2015-10-201-0/+3
| | | | | | | | | | | | | | If you run the extensible SDK environment setup script in a shell session where oe-init-build-env has been run already, and attempt to use the two together, strange things happen - you may not even be running devtool from the extensible SDK, but the OE tree. This isn't a supported use case anyway, so show a warning recommending starting a new shell session. (From OE-Core rev: 41afc48ab979dff6ebb3ea4003dd6baefff7f644) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_ext: add note to env setup scriptPaul Eggleton2015-10-201-0/+2
| | | | | | | | | | Print a note at the end of the environment setup script pointing to devtool. (From OE-Core rev: ea1d566bc2ff61f2e086effb9ca6551b263eacbe) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_ext: prevent image construction from executing on installPaul Eggleton2015-10-202-1/+24
| | | | | | | | | | | | | | | | | | | | | | | In order to prepare the build system within the extensible SDK, we actually go ahead and build the targets specified by SDK_TARGETS (by default the image the SDK was built for). Assuming that's an image, we don't actually need to build the image itself - we just need to have everything done up to the point before building the image, so that we have everything needed in the sysroot. In order to do this, create temporary bbappends for each of the targets in the workspace layer that stub out do_rootfs and related tasks if they exist. This is a little bit of a hack but is the least intrusive fix at this point. To make things a bit tidier, I have split out the preparation commands into a separate script so we can run that in the appropriate environment rather than all the commands separately. Fixes [YOCTO #7590]. (From OE-Core rev: d2a2962897b89731a5705b0cbc7c6f36aa53dcc8) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_ext: consistent indentationPaul Eggleton2015-10-201-5/+5
| | | | | | | | | | Make indentation consistent here in preparation for the changes that follow. (From OE-Core rev: 59a3789c678bf58c0a04b8def416246654680841) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/runtime: Fix setUp and tearDown methodsMariano Lopez2015-10-194-6/+6
| | | | | | | | | | | | | | | | | | | | Currently some of the runtime test overwrites the setUp and tearDown methods provided by oeRuntimeTest, this will avoid some checks required when running the test suit. This patch changes the setUp and tearDown methods for their local counterparts, so when these tests are called, it will run the parent setUp and tearDown and also the local ones. [YOCTO #8465] (From OE-Core rev: 13282223b07787a92c251f89251e8a49a0e4e3eb) Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oetest: Add tearDownLocal classMariano Lopez2015-10-191-0/+6
| | | | | | | | | | | | | | | | | | | | In the current state there are some runtime test that don't run the tearDown method fromm oeRuntimeTest class because the tearDown class is overwritten in the child class. This change adds tearDownLocal method in oeRuntimeTest class that will run after tearDown. This method can be overwritten in the child classes to implement specific test functionality. [YOCTO #8465] (From OE-Core rev: b5917f8032d6965596868b2fe01da4e0682e2804) Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image-live: make SYSLINUX_ROOT changable in image recipesChris Hallinan2015-10-191-1/+1
| | | | | | | (From OE-Core rev: 33c3a74b0266c53773d7ca3983f9ff50c00b9000) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-shar-extract.sh: provide proper path for env_setup_scriptMaxin B. John2015-10-191-1/+1
| | | | | | | | | | | | | | | | | | The toolchain install script suggest the user to source env_setup_script from wrong path now. eg: " Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g. $ . /opt/poky/2.0//opt/poky/2.0/environment-setup-armv5e-poky-linux-gnueabi " fix it. (From OE-Core rev: b388468deda8d81df80d1509226196a5390183a8) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/base: provide hints on PACKAGECONFIG errorJoe MacDonald2015-10-191-1/+2
| | | | | | | | | | | | | | Commit 771f89498c introduces an error message that is very rarely hit and when it is, it is usually easy to trace the root cause very quickly. The information provided in the error message isn't enough to lead you back to the actual failure, however, so expand upon it a bit, pinpointing the specific package and flag that fails. (From OE-Core rev: ead4a552464309e6ef3381590994b6cea225ca20) Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* metadata_scm: rewrite git hash logicRoss Burton2015-10-191-11/+12
| | | | | | | | | | | The code to get the git and branch hash for the current commit in a specific repository was quite complex and prone to breakage, replace it with subprocess and git rev-parse. (From OE-Core rev: bd8ff33cf2439536c6e41cf0ee9dd8fb3b64770a) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* grub-efi, gummiboot: Emit correct path in startup.nshKhem Raj2015-10-192-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | when we generate hddimage and use it to prepare SD card using scripts/contrib/mkefidisk.sh as described here http://elinux.org/Minnowboard:MinnowMaxYoctoProject The content of startup.nsh contains bootx64.efi but this file is actually not in same dir as startup.nsh its in /EFI/BOOT so for this to work entry in startup.nsh should be fs0:\EFI\BOOT\bootx64.efi Otherwise the image is D-O-A (From OE-Core rev: 38fe481911e7c4e9f674ded8f66878dff9e12ce3) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* coreutils: fix for native and nativesdkRobert Yang2015-10-191-1/+1
| | | | | | | | | | | | | The do_install_append is used for moving/renaming for ALTERNATIVE, but it breaks native and nativesdk, for example there is no ln, but ln.coreutils, that makes coreutils-native or nativesdk-coreutils doesn't work. This patch fixes the problem. (From OE-Core rev: e789603c9470ad22f935ab993a13f9ee7c9630eb) 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>
* gcc-4.x: fix wrong warning when using the universal zero initializer {0}Kai Kang2015-10-194-0/+216
| | | | | | | | | | | | | | | | | | | | | When I upgrade efivar to 0.21, it fails to compile with error messages: | linux.c:850:9: error: missing braces around initializer [-Werror=missing-braces] | struct ifreq ifr = { 0, }; | ^ It is a known issue of gcc. Backport patch from https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53119 to fix wrong warning when using the universal zero initializer {0}. (From OE-Core rev: ef16c20e6936218ff96c599cce0200c34f5017dd) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tzdata: reinstate changes reverted in 2014c upgradePaul Eggleton2015-10-191-2/+3
| | | | | | | | | | | | | | OE-Core commit 57af3fb9662106f0a65a1b4edf83e2398be0a8f1 upgraded tzdata but also reverted a couple of changes to SUMMARY and LIC_FILES_CHKSUM. Reinstate these (with an update to the README md5 value since that has changed slightly, without any change to the licensing statements within). (From OE-Core rev: cea4f6b86129f84a99700207777929bf7e811ed6) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-compare: drop PATCHTOOL settingPaul Eggleton2015-10-191-1/+0
| | | | | | | | | | | | We don't need PATCHTOOL to be set to git in this recipe, and setting it that way requires that the running user has git user & email configured, which on a build server it might well not be. (From OE-Core rev: ae8dcdc3c8e090fe392de86dc59135a38f06e9ca) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* common-licenses: use correct GFDL-1.1 license textPaul Eggleton2015-10-191-124/+82
| | | | | | | | | | | | It seems that the GFDL 1.1 license file that was originally committed was actually the 1.2 version. Replace it with the 1.1 version fetched from http://www.gnu.org/licenses/old-licenses/fdl-1.1.txt. (From OE-Core rev: d22252a9e0729abb5e1dd39fc2b6359caf948c43) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe/image.py: Fix dependency handling for compressed typesOtavio Salvador2015-10-141-8/+10
| | | | | | | | | | | | | | | | | | | | | The dependency code needs to also include the dependency of base types. For example: - sdcard.gz image with ext4 The dependency chain needs to include: - sdcard - ext4 - gz Until this change, the ext4 dependency were not being taken into account when using the compressed one. (From OE-Core rev: 10e5df3503632a6e1c54612055b19f7258c3ae2f) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bash: Disable custom memory allocatorAníbal Limón2015-10-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Bash is failing trying to allocate memory [1] using the custom memory allocator if we disable it the issue is fixed. The major distributions also disabled by default [2], so we don't have a good reason to use it. The underlying issue is due to bash’s malloc using brk() calls to allocate memory, which fail when address randomization is enabled in kernel. sbrk() based custom allocators are obsolete. There may be some performance impact of this however correctness is more important. [YOCTO #8452] [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=8452#c0 [2] https://bugzilla.yoctoproject.org/show_bug.cgi?id=8452#c5 (From OE-Core rev: e42d8eff9eed7d1454b4f331d96dcee6dea232df) Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.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-11-19 10:27:21 +0000