summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* gcc: musl related fixes for ppc/secure-plt and gthrKhem Raj2016-02-073-0/+146
| | | | | | | | | | | These issues are fixing building gcc for target, ppc issue helps in fixing discrepency between gcc cmdline and linker cmdline (From OE-Core rev: 6af50d8865335aed68fb4f9b319edb81ce93a04e) 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>
* gcc: Assume libssp and dl_iterate_phdr on muslKhem Raj2016-02-071-0/+1
| | | | | | | | | | | gcc configure fails to set these settings correctly on musl based builds (From OE-Core rev: f1cdd7bf1d9351005867b5c77c05fdddfc9656fd) 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>
* security_flags: wipe security flags for gcc/glibc and related librariesKhem Raj2016-02-071-3/+8
| | | | | | | | | | | It causes a catch-22 situation where we build libssp in gcc-runtime but also pass -fstack-protector flags which require libssp (From OE-Core rev: 61ef8212cc6880f502f1e05e2683d232ea782ae4) 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>
* security_flags: use -fstack-protector-strongKhem Raj2016-02-071-5/+5
| | | | | | | | | | | | | | | This is a better version of -fstack-protector-all with reduced stack usage and better performance yet giving same amount of coverage. It's available in gcc 4.9 onwards. https://outflux.net/blog/archives/2014/01/27/fstack-protector-strong/ has more details. (From OE-Core rev: 4ca946c029f04ba3991ed0f1f65355a7a7840ff4) 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>
* security_flags: ensure security flags only apply to target buildsKhem Raj2016-02-071-2/+2
| | | | | | | | | | | As otherwise the security flags can leak into target builds. This can result in flags that the host compiler doesn't support, causing build failures. (From OE-Core rev: ff2c8af73046f55aa733ce8289b6236c88300290) 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>
* gcc: Fix build on musl with -fstack-protectorKhem Raj2016-02-074-12/+59
| | | | | | | | | | | | | | | | | When enabling the secutity flags on musl based targets the builds fail due to libssp(gcc-runtime) build asking to link with libssp and libssp_nonshared.a when configuring libssp itself. This does not work with musl since it does provide ssp implementation but not like glibc where these libraries are separate to libc Fix the nios2 patch with upstream status while at it and generate the patch after applying to my tree (From OE-Core rev: 77fb841f2e747dc7fb5e9234d870a7a32a74d09b) 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>
* isoimage-isohybrid.py: fix cpio working directoryIoan-Adrian Ratiu2016-02-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | Take `pwd` to be <initial-dir>. The %s path is relative to it. The value of %s is "output_folder/build". The current code works as follows: Changing directory to %s and finding the sources (after cd'ing) to cpio with output redirection to %s/initrd.cpio triggers the following error "Error: exec_cmd: cd output_folder/build/INITRD && find . | cpio -o -H newc >output_folder/build/initrd.cpio returned '1' instead of 0" This happens because after the cd, `pwd` is <initial-dir>/%s and by the redirect we write the result to to <initial-dir>/%s/%s/initrd.cpio which obviously does not exist. Fix this by getting the sources with "find %s" instead of "cd && find ." (From OE-Core rev: 07fa4783566d22d46ce719a621eee5404932dbbe) Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glib-2.0: use the system libpcreRoss Burton2016-02-071-0/+4
| | | | | | | | | | Instead of using the internal copy of libpcre, use one that we build. Note that this requires libpcre enables Unicode properties. (From OE-Core rev: 365f4092070b2e7978b8db65298308f4e770a501) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libpcre: enable unicode properties by defaultRoss Burton2016-02-071-2/+3
| | | | | | | | | | | | | | Enable Unicode properties by default, as they're useful and for example GLib needs them. As there is an impact to code size add this as a PACKAGECONFIG so tightly constrained environments can save space by potentially disabling them. Also change --enable-utf8 to --enable-utf, as the former is a compatibility option for the latter. (From OE-Core rev: 839eebceecf33d106592bab154481486533ece75) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: remove optimize by default patchRoss Burton2016-02-072-60/+0
| | | | | | | | | | | | Python 3 resurrected the default to optimised patch, on the rationale that embedded systems want all the performance they can get. Unfortunately the only impact Python "optimisation" has is to remove all asserts which can be actively harmful, so remove this patch. (From OE-Core rev: 1e43b836106ed13cde294e2c565eaea6fe5efca7) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags.inc: don't do -pie for syslinuxRoss Burton2016-02-071-0/+1
| | | | | | | | | | | sysroots/x86_64-linux/usr/libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/5.3.0/ld: syslinux.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC (From OE-Core rev: b87a9c82663446fa8c002e144de57127e8902b54) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* neon: convert to PACKAGECONFIGAndre McCurdy2016-02-071-8/+19
| | | | | | | | | | | | | Along with the conversion to PACKAGECONFIG, drop unnecessary dependencies on time (it's an app, not a library?) and libxml2 (neon requires either expat or libxml2 for xml parsing, defaulting to expat if both are available). (From OE-Core rev: e4e5b8a1d3febd72d65392ecec6e2b4de16f4022) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toaster: reinstate ID on edit columns buttonElliot Smith2016-02-061-1/+1
| | | | | | | | | | | | | | | | | The ID was omitted from the "edit columns" button on the "projects", "all builds" and "project builds" tables when they were converted to ToasterTable. This caused the QA tests to fail. Reinstate the ID so the tests can identify the "edit columns" button correctly. [YOCTO #9051] (Bitbake rev: 934b82badcf063c8ff252d806c2fb019f7a2e55f) Signed-off-by: Elliot Smith <elliot.smith@intel.com> Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker: shutdown cooker parser on shutdownEd Bartosh2016-02-061-0/+3
| | | | | | | | | | | | | | | | | | | Currently any not catched exception in cooker causes bitbake to hang because of not terminated children of CookerParser. Long term solution would be to reimplement Cooker as a context manager and terminate parser children in its __exit__ method. Partial fix is to call CookerParser.shutdown in Cooker.shutdown in hope that all Cooker exceptions are caught and shutdown method is called. [YOCTO #8900] (Bitbake rev: 3f67600dc3292bc8208644ce89e8bf7ab95cf2e7) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/osc: Clean up old variable syntaxRichard Purdie2016-02-061-5/+5
| | | | | | | | Since people do copy and paste these things, clean up old syntax styles. (Bitbake rev: 4fb028b0bd14d3e4b3fd7a89c643528728566476) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/osc: Remove hardcoded urlRichard Purdie2016-02-061-1/+1
| | | | | | | | This shouldn't be in here, use a variable instead. (Bitbake rev: 2e25d09a1ab62ccc3573d13114d59838cf4b07f2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cross-localedef-native: add ABI breaking glibc patchJens Rehsack2016-02-061-0/+1
| | | | | | | | | | | | | | | Add patch from commit 96b1b5c127e9e0e637aaf7948cf3330a94a5cd57 to cross-localedef-native to avoid broken images built with ENABLE_BINARY_LOCALE_GENERATION set to 1: $ sh -c "export LANG=de_DE; ls -la" sh: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_COLLATE) / sizeof (_nl_value_type_LC_COLLATE[0]))' failed. Aborted (From OE-Core rev: be456fb6160bf4ef0e90ebe2014a349318d58310) Signed-off-by: Jens Rehsack <sno@netbsd.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative: Improve error handlingRichard Purdie2016-02-061-1/+3
| | | | | | | | | | | | We need to improve the error handling here, things were breaking and yet the user wasn't seeing the issues. We need to skip libraries as we process the files. (From OE-Core rev: 95b161a6661faf654fed5c69b905157e927bcb5f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* patchelf: Add patch to handle large filesRichard Purdie2016-02-062-1/+32
| | | | | | | | | | | | | There were "maximum size exceeded" errors from patchelf when processing qemu-native. There is an issue open for this upstream, add a patch proposed there for this issue. "32" was increased to "64" to handle our qemu-ppc binary. (From OE-Core rev: 79d320544202d719eeb5affd9b687505dcd9b725) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_manager.py: fix python indentation bug (opkg)Ioan-Adrian Ratiu2016-02-061-8/+8
| | | | | | | | | | | | This if branch is causing the following error during do_rootfs: "Exception: UnboundLocalError: local variable 'cfg_file' referenced before assignment". This happends because the cfg_file variable is defined at a deeper nesting level (just above the if branch). (From OE-Core rev: 555981c10e6b7f5c2be7f2c3fefb89b1add72cab) Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_ext: Make populate_sdk_ext depend on sdk_extra_confRandy Witt2016-02-061-2/+3
| | | | | | | | | | If a user changes sdk_extra_conf, it should cause populate_sdk_ext to run. (From OE-Core rev: 5de9b123f35a62a0a81f434a10492cdd92668ef0) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_ext: Add support for a "minimal" typeRandy Witt2016-02-061-7/+8
| | | | | | | | | | | If the user sets the SDK_EXT_TYPE variable to "minimal" then the sdk won't contain any sstate. The sstate can come from an sstate mirror and be installed on demand as usual. (From OE-Core rev: 35f79652ab5f1ca754fb726a9bc88d0add0114c8) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_ext: Don't set sdk_update_targets in the configRandy Witt2016-02-061-1/+0
| | | | | | | | | | sdk_update_targets isn't used by any code, so there is no reason to set it. (From OE-Core rev: e9349939e22ca9cf0efe0795291c01fbdeb96a8c) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-scripts.bbclass: Use PYTHONPATH instead of PYTHONHOMERandy Witt2016-02-061-1/+1
| | | | | | | | | | | | | | | In the extensible sdk it was originally intended that the native sstate would always be setscened as part of the sdk installation. However, the soon to come "minimal" sdk won't do that. A side effect of that is that pointing PYTHONHOME at the native sysroot within the "bitbake workspace" won't work. For now only set PYTHONPATH instead and continue using the python that comes from buildtools. (From OE-Core rev: 81f126f4a8944e395f3909de2317065c09b04b5e) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* copy_buildsystem.py: Pass the nativelsb argument to gen-lockedsig-cacheRandy Witt2016-02-061-1/+8
| | | | | | | | | | | | | | If the nativelsb argument is not used, then create_locked_sstate_cache() can get collisions when moving the files from the input_sstate_cache to the output_sstate_cache. The specific case where this was encountered was when a "universal" nativelsb directory already existed in the input_sstate_cache. (From OE-Core rev: 760f7178e0267f930c8af9cb59039e317149f944) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnome-mime-data: removeRoss Burton2016-02-062-33/+0
| | | | | | | | | | gnome-mime-data is part of the GNOME 2 desktop, and the only dependency on it is gnome-vfs which is in meta-gnome where this recipe should live. (From OE-Core rev: 26c4fd5c57996a3f600096d02c7e765ef36d7853) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk-theme-torturer: remove from oe-coreRoss Burton2016-02-062-25/+0
| | | | | | | | | | | This recipe is very old, unmaintained, not used at all in OE-Core, and not useful in a world that has moved to GTK+ 3 (even if Sato is slow at catching up). (From OE-Core rev: d9ecac4828cb316230c3681670e7bf6d197e3a30) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl.inc: drop obsolete mtx-1 and mtx-2 over-ridesAndre McCurdy2016-02-061-4/+0
| | | | | | | | | | Machine specific over-rides for mtx-1 (aka MeshCube) and mtx-2 (aka SurfBox 2nd generation) don't belong in oe-core. (From OE-Core rev: cf0b94629d135b2fa211fae89f48e00469974279) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/devtool: Add getVarFlag expand argumentRichard Purdie2016-02-061-1/+1
| | | | | | (From OE-Core rev: afa9b1081848cf0dbc40bbaf565bcc2ee19e8f6e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/native/nativesdk: Set PKG_CONFIG_SYSTEM_ at top levelRichard Purdie2016-02-063-2/+4
| | | | | | | | | | | | | | Setting PKG_CONFIG_SYSTEM_{HEADERS/INCLUDE}_PATH for nativesdk isn't enough, we also need to deal with multlib cases where libdir from pkg-config-native isn't correct. Native builds are about the only case where this variable shouldn't be set. Therefore move the code from nativesdk to bitbake.conf and unexport it in the native case. (From OE-Core rev: 46c48c26ab1916e2dfb841d74a0f2a58d8b2b870) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pango: unset LDFLAGS when building gen_all_unicodeRoss Burton2016-02-061-1/+1
| | | | | | | | | | | | | When building the native gen_all_unicode binary we need to also unset LDFLAGS as otherwise the *target* LDFLAGS will be used. At best the options are harmless but if there are options that the host compiler doesn't support then the compile will fail. For example, if the host gcc is version 4.8 but LDFLAGS contains -fstack-protector-strong which in 4.9 onwards. (From OE-Core rev: 20031e167f772ce2eb3ba4b93adb82c1f4805d42) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pango: merge bb and incRoss Burton2016-02-062-46/+44
| | | | | | | (From OE-Core rev: 71e374aa5b6c466cc6ddfffeaa7cee9a6b3d2f0e) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* e2fsprogs: Ensure we use the right mke2fs.conf when restoring from sstateRichard Purdie2016-02-051-0/+15
| | | | | | | | | | | | | | | | | If we don't do this, we can use an mke2fs.conf from a different path which may contain incompatible flags and lead to obtuse build failures such as: Invalid filesystem option set: has_journal,extent,huge_file,flex_bg,metadata_csum,64bit,dir_nlink,extra_isize To fix this, wrap the mke2fs binary and its hardlinks and point at the correct configuration file. In particular this fixes conflicts between master and jethro builds affecting the main autobuilder. (From OE-Core rev: 11a6227759515da433230eb44eca1a4cb2ac3b14) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk: Set PKG_CONFIG_SYSTEM_ variablesRichard Purdie2016-02-051-0/+2
| | | | | | | | | | | | | | When building nativesdk recipes, we noticed paths going into .pc files which should have been suppressed since these were standard library search paths. pkgconfig-native sets these variables to sane values for native recipes, we need it set to values for our specific library paths in the nativesdk case. Setting these values cleans up the .pc files and suppresses the paths. (From OE-Core rev: 837c8b749b06457ba4a5a76a34ffe45d36bf4ef3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* local.conf.sample.extended: Document HOW-TO enable systemd or busbox for ↵Khem Raj2016-02-051-0/+18
| | | | | | | | | | | | | init system OE core provides systemd,busybox as options for system init system along with sysvinit being the default. Document the needed settings to enable systemd and busybox as options if user wishes. (From meta-yocto rev: 36ea4c99bd1d769e1b4098c8cc9baffc161131b6) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* local.conf.sample: Remove trailing whitespacesKhem Raj2016-02-052-18/+17
| | | | | | | (From meta-yocto rev: 93c7a1a72cb485fabd5f247e6245ec44b4cb26bf) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: parse/ast: Mark anonymous functions as python functionsRichard Purdie2016-02-041-2/+2
| | | | | | | | | | Anonymous functions are python functions, set the variable flags as such so we can detect them and avoid expansion where needed. (Bitbake rev: 1b303785c578bbae3a89be8d751d80fba860f62e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: codeparser: Improve handling of data.expand() dependenciesRichard Purdie2016-02-041-0/+12
| | | | | | | | | | | | | | | | | Currently bitbake doesn't parse into data.expand() expressions, relying on high level expansion of python code to handle this. One of the tests does however test this works. We don't really want to be doing string expansion on python code, so specifically parse into expand() function calls so that when the high level behaviour is tweaked, the self tests continue to pass and that we do continue to handle expand() function calls as best we can. (Bitbake rev: b12c17be5e4a74c9680876605c87f46501f78d28) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: lib/bb: Add expansion parameter to getVarFlagRichard Purdie2016-02-048-39/+39
| | | | | | | | | | | | | | | This sets the scene for removing the default False for expansion from getVarFlag. This would later allow True to become the expand default. On the most part this is an automatic translation with: sed -e 's:\(\.getVarFlag([^,()]*, [^,()]*\)):\1, False):g' -i `grep -ril getVar *` There should be no functional change from this patch. (Bitbake rev: 7c3b99c6a716095af3ffce0b15110e91fb49c913) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/gitsm: Fix when repository change submodulesFelipe F. Tonello2016-02-041-1/+1
| | | | | | | | | | | | | | This fix a problem when checking out a commit that changes the submodules previously checkout. Example: Recipe uses branch A and then it updates to use branch B, but branch B has different submodules dependencies then what branch A previously had. (Bitbake rev: 54a3864246f2be0b62761f639a1d5c9407aded4f) Signed-off-by: Felipe F. Tonello <eu@felipetonello.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: data_smart: Add missing expand parameter to getVar callRichard Purdie2016-02-041-1/+1
| | | | | | (Bitbake rev: 2876019e696ff2af164961d5d4c8e3ea9dfefc23) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: prserv: do not clear umask when daemonizingDiego Santa Cruz2016-02-041-1/+0
| | | | | | | | | | | | | | | Clearing the umask when daemonizing is not the correct thing to do, as it will create files writable by anyone by default. For instance the pid file was being created with mode 777. This could also potentially affect the sqlite database. Better let the calling process decide on the umask. [YOCTO #9036] (Bitbake rev: ff6d3f53a4504eae7ec4c190b9f7595b09aed017) Signed-off-by: Diego Santa Cruz <Diego.SantaCruz@spinetix.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: prserv: SIGTERM handling hung processDiego Santa Cruz2016-02-041-1/+1
| | | | | | | | | | | | | | | | | | The current SIGTERM handler hungs the process instead of making it exit. The problem seems to be that the handler thread is not signaled to quit, so it stays there doing its work, as it is not a daemon thread. Setting the quit variable fixes this. While at it, to not use the SystemExit exception to terminate upon SIGTERM but instead left the quit flag do its job. This way the PID file is properly removed. [YOCTO #9035] (Bitbake rev: 655ec800d54da581229f12efb6f0baf54975fed4) Signed-off-by: Diego Santa Cruz <Diego.SantaCruz@spinetix.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: prserv: -wal and -shm sqlite lost when daemonizingDiego Santa Cruz2016-02-041-5/+8
| | | | | | | | | | | | | | | | | | | | | | | | When daemonizing the PR service the -wal and -shm sqlite files were being deleted, although they should never be. While the daemonized process keeps the file descriptors open and thus a clean exit does not loose any data, a power outage would loose all data in the WAL. Removing these files also breaks sqlite collaboration between processes and furthermore prevents taking proper backups without stopping the PR service. The reason this happens is that the DB connection is opened in the initial process, before forking for daemonization. When the DB connection is closed by the exiting parent processes it can delete the -wal and -shm files if it considers itself to be the last connection to the DB. This is easily fixed by opening the DB connection after all forking. [YOCTO #9034] (Bitbake rev: bc867c81e3894da5bdd2e45fa695bb5f5f1bb58b) Signed-off-by: Diego Santa Cruz <Diego.SantaCruz@spinetix.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky-tiny: Use musl for default system C libraryKhem Raj2016-02-041-20/+5
| | | | | | | | | | | | | | poky-tiny is reference for smallest footprint distro that can be generated using yocto project infrastructure. Therefore switch to using musl which gives the smallest footprint with a lot of extra stretching for adding new package if needed, core-image-minimal for qemux86 comes out to be 716K ( rootfs only ), boot tested on qemux86/poky-tiny (From meta-yocto rev: e1b4918a4f3a19a125537a984ce4dadb79badcea) 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>
* maintainers.inc: Set me as Maintainer of QEMU.Aníbal Limón2016-02-041-3/+3
| | | | | | | | (From meta-yocto rev: eb1e3fa0644099295b4fe5a5a5415804b5fda693) 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>
* insane: Fix populate_sysroot sanity test pathRichard Purdie2016-02-041-1/+1
| | | | | | | | | | This was correct for native/cross paths but not for target ones which meant the tests weren't running in some cases. Fix the path to be correct in both cases. (From OE-Core rev: 3739aaf644d5a0f28e85fd07c67cecbfa5b8fb8a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* socat: upgrade to 1.7.3.1Ross Burton2016-02-041-2/+2
| | | | | | | | | | | This fixes Socat Security Advisory 7 (MSVR-1499) and 8. [ YOCTO #9024 ] (From OE-Core rev: 4be6104e8466e977e2ea45d068d277c089b2a9d1) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libffi: move from recipes-gnome to recipes-supportRoss Burton2016-02-043-0/+0
| | | | | | | (From OE-Core rev: a2c43ffe55e022cb5621d549c8aae914c6fa54a1) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libffi: ensure sysroot paths are not in libffi.pcRoss Burton2016-02-043-19/+23
| | | | | | | | | | Remove a previous patch and solve the problem in a different way, as the same root cause was causing the absolute sysroot path to appear in libffi.pc. (From OE-Core rev: 9ffc1757a1578832463d29f558914c3b489a3782) 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-06-30 07:59:21 +0000