summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFiles
2016-02-28uninative-tarball: respect SDKMACHINE when buildingRoss Burton1
So that a single machine can build multiple architectures for the uninative-tarball respect SDK_ARCH instead of BUILD_ARCH. This means a x86-64 host can build a i686 uninative-tarball by setting SDKMACHINE=i686. Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28boost.inc: enable more verbose build logsAndre McCurdy1
The default build output is very terse. Add -d+2 (ie "Show commands as they are executed") to BJAM_OPTS to make the do_compile logs more informative. Also add -q (ie "Stop at first error") to BJAM_OPTS and fix typo in comments. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28gstreamer1.0-plugins-XXX: move inherit gettext into common .inc fileAndre McCurdy5
gstreamer1.0-plugins-base/good/bad/ugly.inc all independently inherit gettext. Move into the common gstreamer1.0-plugins.inc include file. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28gstreamer1.0.inc: add explicit PACKAGECONFIG initAndre McCurdy1
Although gstreamer1.0.inc doesn't currently set any default PACKAGECONFIG options, add explicit initialisation in order to match the style / structure of the other gstreamer1.0 recipes. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28gstreamer1.0-libav: move LIBAV_EXTRA_CONFIGURE_COMMON_ARG into .incAndre McCurdy3
The LIBAV_EXTRA_CONFIGURE_COMMON_ARG definition is now common to both the git and the versioned gstreamer1.0-libav recipes, so move it into gstreamer1.0-libav.inc Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28gstreamer1.0-libav_git: add --ranlib option to LIBAV_EXTRA_CONFIGURE_COMMON_ARGAndre McCurdy1
The versioned gstreamer1.0-libav recipe includes --ranlib in LIBAV_EXTRA_CONFIGURE_COMMON_ARG, but the git recipe does not. It appears to be a historical mistake. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28boost.inc: limit ARM_INSTRUCTION_SET over-rides to armv4/armv5Andre McCurdy1
The original over-ride dates back to 2009: http://git.openembedded.org/openembedded-core/commit/?id=43e94412c45b4b79485a64010c76d89b245bb235 There are no obvious issues seen now when building boost in thumb2 for Cortex A15. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28populate_sdk_ext: Add images to SDK_INSTALL_TARGETSRandy Witt1
When running ext-sdk-prepare.py during sdk installation a check is done to make sure no tasks would run that aren't provided by the "leaf" recipes specified in SDK_INSTALL_TARGETS. However sometimes an image recipe can cause other images to be created such as an initramfs. So make sure those additional images are recognized by ext-sdk-prepare.py and don't flag an error. Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28boot-directdisk.bbclass: drop IS_VM chechkingRobert Yang1
The IS_VM was used for making menus for vmdk, vdi and qcow2, except hddimg, there is no reason to not make menus for hddimg, so drop it. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28image-live/boot-directdisk.bbclass: remove AUTO_SYSLINUXCFGRobert Yang2
No one uses it. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28testimage.bbclass: reuse generic test suitesAlex Franco1
Modify existing default test suites to reuse the new generic test suites. Related to [YOCTO #8410] Signed-off-by: Alex Franco <alejandro.franco@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28testimage.bbclass: add generic, image test suitesAlex Franco1
Add generic test suites MINTESTSUITE, NETTESTSUITE, DEVTESTSUITE to group common test suites. Add DEFAULT_TEST_SUITES_pn- variables for: * core-image-minimal-dev * core-image-full-cmdline * core-image-x11 * core-image-lsb * core-image-lsb-dev New default test suites use generic test suites. Existing default test suites not modified. [YOCTO #8410] Signed-off-by: Alex Franco <alejandro.franco@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28gconf: remove redundant dependenciesRoss Burton1
The explicit native dependencies are identical to the class-generated dependencies so remove them. The dbus-x11 package hasn't existed for some time and is RPROVIDEd by dbus, so there's no need to depend on it. Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28gtk-doc-stub: don't inherit autotoolsRoss Burton1
There's quite an overhead in inheriting autotools, but this package just has a hand-crafted configure script and Makefile. Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28os-release: sanitise VERSION_ID fieldJoshua Lock1
Per os-release(5) the VERSION_ID field should be: a lower-case string (mostly numeric, no spaces or other characters outside of 0-9, a-z, ".", "_" and "-") Do some string manipulation to try and ensure the VERSION_ID field we write is valid. Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28apr-util: add ldap crypto and sqlite3 to PACKAGECONFIGIoan-Adrian Ratiu1
Enable apr-util's cryptographic routines so that the apache2 package can encrypt session data. Also add sqlite3 and ldap modules, disabled by default. Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28apr-util: fix loadable module packagingIoan-Adrian Ratiu1
A new QA check was introduced by 47d38d4d86ec6a which catches recipes which install loadable modules (*.so) inside -dev packages instead of symlinks. Install apr-util's modules into ${PN} and also skip the QA check [dev-so] because it is the reverse of the check introduced by 47d38d4d86ec6a (thus if a recipe passes one it fails the other). Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28glibc.inc: improve optimisation level sanity checkingAndre McCurdy1
- Avoid code duplication to handle -O, -O1 and -Os cases - Consider the effective optimisation level only (avoids spurious warnings if multiple optimisation flags are present). - Prefix warnings with PN instead of hardcoding "glibc" (avoids confusing warnings since the test is also applied to glibc-initial, nativesdk-glibc, nativesdk-glibc-initial, etc, and each could potentually have different optimisation flags). Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28rsync: add native variantJoshua Lock1
Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28core-tools-profile: add lttng tools for aarch64Tudor Florea1
Signed-off-by: Tudor Florea <tudor.florea@enea.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28lttng-ust: add support for aarch64_beTudor Florea2
Signed-off-by: Tudor Florea <tudor.florea@enea.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28liburcu: add support for aarch64_beTudor Florea2
Signed-off-by: Tudor Florea <tudor.florea@enea.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28harfbuzz: add explicit dependency on fontconfigAndre McCurdy1
The fontconfig dependency was previously met indirectly (via cairo). Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28harfbuzz: update 1.2.0 -> 1.2.1Andre McCurdy1
Overview of changes leading to 1.2.1 Friday, February 23, 2016 ==================================== - CoreText: Fix bug with wrong scale if font scale was changed later. https://github.com/libass/libass/issues/212 - CoreText: Drastically speed up font initialization. - CoreText: Fix tiny leak. - Group ZWJ/ZWNJ with previous syllable under cluster-level=0. https://github.com/behdad/harfbuzz/issues/217 - Add test/shaping/README.md about how to add tests to the suite. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28fontconfig: Don't add font directories from hostMartin Jansa1
* when enabled, configure check for "fonts" directory existence in following directories: /usr/X11R6/lib/X11 /usr/X11/lib/X11 /usr/lib/X11 on _host_ system and if it exists it adds <dir> element to /etc/fonts/fonts.conf * update_font_cache postinst will then fail if host system has e.g. /usr/lib/X11/fonts while the rootfs doesn't have it * if you're installing fonts to other directories, you'll need to adapt this EXTRA_OECONF to find them that's why it's in separate variable [YOCTO #9155] - update_font_cache postinst failing with read-only filesystem Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28musl: Upgrade to 1.1.14Khem Raj1
There has been regressions seen in 1.1.13 hence a quick 1.1.14 release is made license checksum changed due to updates to authors/contributors list here is the list of all changes between 1.1.13 and 1.1.14 http://git.musl-libc.org/cgit/musl/log/?qt=range&q=v1.1.13..v1.1.14 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28oe-selftest: devtool: add an additional test for devtool upgradePaul Eggleton3
Add a test for devtool upgrade with a recipe pointing to a git repository, since this uses several different code paths. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28oe-selftest: devtool: rework devtool upgrade testPaul Eggleton8
* Use a more real-world test of a recipe pointing to a remote file * The cleanup tracking / teardown commands need to be added towards the top, or they won't have the desired effect of cleaning up if the test fails. * Check that a versioned subdirectory gets renamed to match the new version * Ensure the recipe contents gets changed as we expect it to * Check that the recipe directory is deleted by devtool reset at the end Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28devtool: upgrade: print new recipe namePaul Eggleton1
Make this consistent with "devtool add" so that the user knows where to find the new recipe. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28devtool: upgrade: drop PR on upgradePaul Eggleton1
The PR value should be reset to the default when upgrading, so we need to drop it from the newly created file. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28devtool: upgrade: eliminate unnecessary datastore copyPaul Eggleton1
We aren't modifying the datastore copy here, so we don't need a copy at all. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28devtool: upgrade: fix several issues with extraction of new sourcePaul Eggleton1
Fix several issues when extracting the new version source over the top of the old one (when the recipe is not fetching from a git repo): * Delete the old source first so we ensure files deleted in the new version are deleted. This also has the side-effect of fixing any issues where files aren't marked writeable in the old source and thus overwriting them failed (harfbuzz 1.1.3 contains such files). * Fix incorrect variable name in abspath statement that made it a no-op Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28devtool: upgrade: fix constructing new branch from tarball releasesPaul Eggleton1
When we do an upgrade from one tarball version to another we want to: 1) Check out the old version as a new branch 2) Record the changes between the old and new versions as a commit 3) Check out the old version with patches applied 4) Rebase that onto the new branch Where we went wrong was step #1 where instead we checked out the old version with patches applied as the new branch, which meant the rebase didn't do anything and any changes made by the patches to files still in the new version were wiped out. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28devtool: upgrade: fix renaming of recipe if PV is not in namePaul Eggleton1
If the actual value of PV isn't in the name of the recipe (for example, a git or svn recipe) there's no point trying to rename it. Additionally, we already have the original filename, there's no need to guess it - just pass it in. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28devtool: upgrade: fix moving version-specific files directoryPaul Eggleton1
We were trying to move this from the current directory instead of the path. Let's just use shutil.move() instead of shelling out to mv. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28devtool: upgrade: fix version argument checkingPaul Eggleton1
For recipes that specify SRCREV, the code here wasn't quite doing the right thing. If the recipe has a SRCREV then that needs changing on upgrade, so ensure that the user specifies it. If it doesn't, then it'll be "INVALID" not None since the former is the actual default, so handle that properly as well. Additionally an unset variable was being erroneously passed when raising the error about the version being the same leading to a traceback, so fix that as well. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28devtool: upgrade: drop superfluous call to validate_pnPaul Eggleton1
The recipename argument to devtool upgrade specifies an existing recipe, so by definition the name will be valid (or it won't exist) - we don't need to validate it ourselves, that's only needed for situations like in devtool add where we're creating a new recipe. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28devtool: upgrade: make source tree path optionalPaul Eggleton1
Make devtool upgrade consistent with devtool add/modify in defaulting to sources/<recipename> under the workspace if no source tree path is specified. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28devtool: modify: fix source tree default name when mapping virtualsPaul Eggleton1
If you for example ran devtool modify virtual/libusb0 without specifying a source tree path, the default was <workspace>/sources/virtual/libusb0 which isn't correct - it should be using the mapped name i.e. libusb-compat (in the default OE-Core configuration). Reorder some of the code to ensure that the mapped name is used. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28devtool: add: tweak auto-determining name failure messagePaul Eggleton1
As suggested by Khem Raj. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28uninative.bbclass: if the loader can't be found disable instead of failingRoss Burton1
Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28uninative: use check_output instead of Popen directlyRoss Burton1
Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28lib/oe/qa: add explicit exception for 'file isn't an ELF'Ross Burton3
Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28libdrm: fix build with uclibcMaxin B. John2
Fix 'O_CLOEXEC' undeclared error with uclibc Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28strace: fix ptest executionDengke Du1
When run the strace ptest on the target, the test files located in the "/usr/lib/strace/ptest/tests", but the run-test script use the path "srcdir = ../../strace-*/tests"to find the necessary files, so it can't find the necessary files, it fails. So change the variable srcdir, replace the strace-* to ptest when do the do_install_ptest() function using the following: sed -i -e '/^src/s/strace.*[1-9]/ptest/' ${D}/${PTEST_PATH}/${TESTDIR}/Makefile Signed-off-by: Dengke Du <dengke.du@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28clutter-1.0: Fix confgure test errors found by clangKhem Raj2
We were using nested functions inadvertantly and they were compiling fine with gcc but clang doesnt support nested functions hence configure tests for cogl started to fail, but it was a test error not compiler error which was undetected thus far Backport a fix from upstream to help clang compile clutter Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28oeqa/parselogs: Updated whitelistCristina Agurida1
Moved an error to common, and whitelisted the BAR errors and ati module. Also the uvesafb related errors will be ignored in LSB images which do not have graphic interface. Fix for [YOCTO #8387] Fix for [YOCTO #8590] Fix for [YOCTO #6820] Fix for [YOCTO #7897] Signed-off-by: Lucian Musat <george.l.musat at intel.com> Signed-off-by: Cristina Agurida <cristina-danielax.agurida@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28buildstats.bbclass: Don't assume /proc/<pid>/io presentJuro Bystricky1
It is not guaranteed Linux kernel was configured with process I/O statistics enabled. If process I/O statistcs are not present, issue a one time warning and do not attempt to read the non-existing stats counters. [YOCTO#9025] Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28sysvinit-inittab: Move start_getty scrip to base_bindir.Philip Tricca1
When this file is in ${sysconfdir}/init.d, SELinux labels it as a generic init script (initrc_t). This causes problms at runtime because SELinux doesn't let the login process execute generic init script. Moving this helper script to base_bindir results in it being labeled as a generic binary (bin_t). Nearly every SELinux domain is allowed to execute generic binaries and the login process is one of them. Signed-off-by: Philip Tricca <flihp@twobit.us> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-28oeqa/selftest/prservice: Added new TC: check pr-server starts and stop ↵Francisco Pedraza1
correctly on localhost. This test case validates if prservice start and stop properly the server. Using bitbake commands also validates the exit status. [YOCTO #8258] Signed-off-by: Francisco Pedraza <francisco.j.pedraza.gonzalez@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
generated by cgit v1.2.3 (git 2.25.1) at 2025-01-08 16:49:26 +0000