summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core
Commit message (Collapse)AuthorAgeFilesLines
* build-appliance-image: Update to morty head revisionyocto-2.2.1morty-16.0.1Richard Purdie2017-02-081-1/+1
| | | | | | (From OE-Core rev: 55c835c73cc41b6fc809c941c295d62a612e49e0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* zlib: update SRC_URI to fix fetchingJoshua Lock2017-01-121-1/+1
| | | | | | | | | | | | | | | | Upstream have removed the file from zlib.net as a new version has been released, switch to fetching from the official sourceforge mirror. [YOCTO #10879] (From OE-Core rev: bb99e4a620efd59556539c156cd98ea23aae74c8) (From OE-Core rev: b7599330f1d629384e16a5fbeffc1a65c1555667) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to morty head revisionRichard Purdie2017-01-111-1/+1
| | | | | | (From OE-Core rev: ae3513b8e752d0dc1757fbfc681f644a3f2855b0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxml2: Fix more NULL pointer derefsAndrej Valek2017-01-112-0/+47
| | | | | | | | | | | | | | | | | The NULL pointer dereferencing could produced some security problems. This is a preventive security fix. (From OE-Core rev: 8f3008114d5000a0865f50833db7c3a3f9808601) (From OE-Core rev: 401d552f9e4ed3341e42864e566dddb2b26019dc) Signed-off-by: Andrej Valek <andrej.valek@siemens.com> Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxml2: fix CVE-2016-4658 Disallow namespace nodes in XPointer points and ↵Andrej Valek2017-01-112-0/+270
| | | | | | | | | | | | | | | | | | | ranges Namespace nodes must be copied to avoid use-after-free errors. But they don't necessarily have a physical representation in a document, so simply disallow them in XPointer ranges. (From OE-Core rev: 00e928bd1c2aed9caeaf9e411743805d2139a023) (From OE-Core rev: cf810d5cc17cb6b9f53d21a404c89afe372accb7) Signed-off-by: Andrej Valek <andrej.valek@siemens.com> Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxml2: Necessary changes before fixing CVE-2016-5131Andrej Valek2017-01-112-0/+68
| | | | | | | | | | | | | | | | | | xpath: - Check for errors after evaluating first operand. - Add sanity check for empty stack. - Include comparation in changes from xmlXPathCmpNodesExt to xmlXPathCmpNodes (From OE-Core rev: 96ef568f75dded56a2123b63dcc8b443f796afe0) (From OE-Core rev: 68b0f3a0bf8dfdf49be4aed1745a7f50662c555d) Signed-off-by: Andrej Valek <andrej.valek@siemens.com> Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Enable backtrace from abort on ARMYuanjie Huang2017-01-111-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ARM stack frames for abort and raise were limited to the the actual abort and raise call, such as: Obtained 4 stack frames. ./test-app(print_trace+0x1c) [0x10a08] ./test-app() [0x10b3c] /lib/libc.so.6(__default_sa_restorer+0) [0x4adae1e0] /lib/libc.so.6(gsignal+0xa0) [0x4adacf74] This is not terribly useful when trying to figure out what function may have called called the abort, especially when using pthreads. After the change the trace would now look like: Obtained 8 stack frames. ./test-app(print_trace+0x1c) [0x10a08] ./test-app() [0x10b3c] /lib/libc.so.6(__default_sa_restorer+0) [0x4befe1e0] /lib/libc.so.6(gsignal+0xa0) [0x4befcf74] /lib/libc.so.6(abort+0x134) [0x4befe358] ./test-app(dummy_function+0x50) [0x10adc] ./test-app(main+0xd4) [0x10c24] /lib/libc.so.6(__libc_start_main+0x114) [0x4bee7a58] (From OE-Core rev: 93bf8713d8e13c278543baea94fb8dad0cb80e49) (From OE-Core rev: b0e6a6048fa09dceac78bf8c46d484690ff5b098) Signed-off-by: Yuanjie Huang <yuanjie.huang@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> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxml2: Security fix CVE-2016-5131Yi Zhao2017-01-112-0/+181
| | | | | | | | | | | | | | | | | | | | | | | CVE-2016-5131 libxml2: Use-after-free vulnerability in libxml2 through 2.9.4, as used in Google Chrome before 52.0.2743.82, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to the XPointer range-to function. External References: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-5131 Patch from: https://git.gnome.org/browse/libxml2/commit/?id=9ab01a277d71f54d3143c2cf333c5c2e9aaedd9e (From OE-Core rev: 640bd2b98ff33e49b42f1087650ebe20d92259a4) (From OE-Core rev: 1e284447b9bf42e1fd6080f5a50fe01c8267a4e6) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: add su.1 to update-alternativesRoss Burton2016-11-161-3/+5
| | | | | | | | | | | | | | | | The su binary is handled by alternatives but the man page wasn't, so installing both util-linux-doc and shadow-doc produces errors. Also use d.expand() to neaten the code. (From OE-Core rev: 70a161ee88d3d54fec6d59039c181b43f1857dc3) (From OE-Core rev: bec07530536c36b2ab2a7818a9ffc475faba27ac) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* busybox/mdev.conf: Ignore eMMC RPMB and boot block devicesMike Looijmans2016-11-161-0/+2
| | | | | | | | | | | | | | | | | eMMC devices may report block devices like "mmcblk0rpmb" and "mmcblk0boot0". These are not actually block devices and any read/write operation on them will fail. To prevent spamming error messages attempting to mount them, just ignore these devices. (From OE-Core rev: 9f4a85eb929f67420d9689d7dddadd120ed49843) (From OE-Core rev: 50d97edaeb18a4c6374101d222410a3b0f344bf2) Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: CVE-2016-7795Chen Qi2016-11-162-0/+70
| | | | | | | | | | | | | | | | | | | | | The manager_invoke_notify_message function in systemd 231 and earlier allows local users to cause a denial of service (assertion failure and PID 1 hang) via a zero-length message received over a notify socket. The patch is a backport from the latest git repo. Please see the link below for more information. https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-7795 (From OE-Core rev: 543570cafa8d7f595b489d03d05f0aa4478f8539) (From OE-Core rev: df3f4785fc69d3ddbd30ccd954aad3d3618c5916) 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> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Fix incorrect PATHJuro Bystricky2016-11-161-1/+1
| | | | | | | | | | | | | | | | | | | | | When modifying the PATH variable in .bashrc, double quote characters were used, resulting in expanding the variable $PATH with the value of PATH of the system building the Build Appliance. The original intent was to enter an un-expanded (literal) $PATH. In order to that, one must use single quotes instead of double quotes. [YOCTO#10434] [YOCTO#10504] (From OE-Core rev: 6238faf901956e2a350315a66ca1ce557deaa513) (From OE-Core rev: ac2b0413526df46cfdcae2d3f9add1a29fe3c2b5) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-applance-image: Fix to use the release branch for mortyyocto-2.2morty-16.0.0Richard Purdie2016-10-261-1/+1
| | | | | | (From OE-Core rev: 2a59d0fa7bda78927435603e3049ce373cf6a198) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to morty head revisionRichard Purdie2016-10-261-1/+1
| | | | | | (From OE-Core rev: 742e6d462948cdc89e5c538c9d834ff4fb42352e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: add /sbin to PATHJuro Bystricky2016-10-251-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | runqemu script fails with an error when executed in Build Appliance. Typical use case: $ bitbake core-image-minimal $ runqemu qemux86 Observed error: runqemu - ERROR - In order for this script to dynamically infer paths ...snip... runqemu-ifup, runqemu-ifdown or ip not found The error is caused by the fact that "ip" is located in /sbin, however /sbin is not in user's ("builder") PATH. To fix this we add /sbin to PATH. The simplest place to do this is in user's .bashrc. [YOCTO#10434] (From OE-Core rev: 7561514454c20a86e9e126af80dcf114ccd23535) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2016-10-191-1/+1
| | | | | | (From OE-Core rev: 327e4bf5a84d5b49ccc65927df622c9ef6302d55) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxml2: Make tests non-executableJussi Kukkonen2016-10-151-0/+5
| | | | | | | | | | | | | | The XML W3C conformance test suite contains thousands of xml files all marked executable. We dutifully try to strip all these files of debug info in do_package. "chmod -x" improves build time by ~40 seconds. (From OE-Core rev: eb9cdf6b9277d23d1696233fccc4689e6030644c) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base-files: fix profile error under < /dev/nullRichard Tollerton2016-10-151-2/+4
| | | | | | | | | | | | | | Previous attempts to constrain execution of `resize` to only TTYs did not properly handle situations when `tty` would return the string "not a tty". The symptom is "/etc/profile: line 34: test: too many arguments". Fix this by utilizing the exit code of `tty`. Also use `case` instead of `cut` to eliminate a subshell. (From OE-Core rev: e67637e4472ff3a1e2801b84ee3d69d4e14b9efc) Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2016-10-111-1/+1
| | | | | | (From OE-Core rev: 1a2311c8fa9a3703568cd390c44639fe3335023e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysklogd and busybox: ignore return code from init script stopMarkus Lehtonen2016-10-111-1/+1
| | | | | | | | | | | | | | The init script will return '1' if we try to stop the service and it is not currently running. The prerm scriptlet must not fail because of this because it will cause package deinstallation of upgrade fail if opkg package manager is used. [YOCTO #10299] (From OE-Core rev: 806a910927f479207d47b06c20a0497e91203266) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2016-10-111-1/+1
| | | | | | (From OE-Core rev: 70b9b1f5bbc07d97f90b62793bf2c5aa01884436) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2016-10-111-1/+1
| | | | | | (From OE-Core rev: c33cd0b3d274d2c4253ff98f85b7ca4fced0aedb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_ext: add symlinks and unfsd to support Eclipse pluginPaul Eggleton2016-10-071-1/+1
| | | | | | | | | | | | | | The Yocto Project Eclipse plugin requires that runqemu and unfsd are accessible within the SDK, and indeed the standard SDK has these. This turns out to be fairly easy to do - we just need to add unfsd and symlink it, runqemu and a few other scripts into the SDK's bin directory. Fixes [YOCTO #10214]. (From OE-Core rev: 9007e0e3fce7e09b043fead54b17f69c1661d162) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Add mipsisa{32, 64}r6{el, } supportZubair Lutfullah Kakakhel2016-10-071-0/+4
| | | | | | | | | | | | | Add support for MIPS Release 6 ISA The loader is located at a new place for multiarch. For more details, check https://wiki.debian.org/Multiarch and https://sourceware.org/glibc/wiki/ABIList#mips (From OE-Core rev: 502145553e2368525a4b327c64d2971dac58d85b) Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base-files: don't export TZ="UTC" from /etc/profileAndre McCurdy2016-10-051-6/+0
| | | | | | | | | | | | | | | If no /etc/localtime (or /etc/TZ for uclibc) is found, then the libc will default to UTC, so setting UTC as a fallback default via the TZ environment variable is redundant. Since having the TZ environment variable set causes /etc/localtime to be ignored, it can cause confusion if /etc/localtime is added interactively after /etc/profile has been run. (From OE-Core rev: 98b6420952cbf73ddd1318f36c68d575c330eb71) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kbd: create ptest sub-packageKai Kang2016-10-013-0/+79
| | | | | | | | | | | | | | Create kbd-ptest sub-package: * add file run-ptest and runtime dependency make * modify installed Makefile to disable remake Makefile and the test cases when run the ptest * add patch to set proper path for test cases to get resource files (From OE-Core rev: 901ccb3e70e9036112c51acc6d18d05025f6e1bb) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* SDK: Allow changing SDKMACHINE without wiping TMP folderJuro Bystricky2016-09-283-3/+3
| | | | | | | | | | | | | | | | | | | When changing SDKMACHINE, we may encounter an error forcing us to wipe the TMP folder. Since only SDK_ARCH is captured in the PN of the crosssdk recipes, changes to SDK_OS result in conflicts. Eventually we hit the error: ERROR: ...: The recipe <...> is trying to install files into a shared area when those files already exist. The build has stopped as continuing in this scenario WILL break things This patchset addresses the problem by SDK_SYS as the recipe name suffix instead of SDK_ARCH. [YOCTO #9281] (From OE-Core rev: d2eccccb70e809d482c493922f23aef4409cfd82) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc-initial: use python3 instead of python (v2)Markus Lehtonen2016-09-281-1/+1
| | | | | | | (From OE-Core rev: 6946a19fdc8853fbb02fd531b76d9d6d9a3febc3) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-environment: ensure corret TOOLCHAIN_CONFIGSITE_NOCACHE valueChen Qi2016-09-261-0/+2
| | | | | | | | | | | | | Expand TOOLCHAIN_CONFIGSITE_NOCACHE value immediately before inheriting cross-canadian to avoid HOST_ARCH being changed from TARGET_ARCH to SDK_ARCH, thus ensuring its correct value. [YOCTO #10255] (From OE-Core rev: 1e13d1fd22186af5544e7248dc12635cd2f2e08b) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eudev: don't move udev directoryRobert Yang2016-09-241-9/+1
| | | | | | | | | | The code did "mv ${D}${base_libdir}/udev ${D}${nonarch_base_libdir}" which is not needed any more, eudev can work with ${base_libdir}/udev. (From OE-Core rev: 5e26b3df04716010b31b4c7ac0ac6b28982784f3) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: install udev.pcRobert Yang2016-09-241-0/+2
| | | | | | | | | | | | | | | | | | | | | It provides udev, but doesn't install udev.pc, which causes other recipes failed to figure out udevdir. Fixed when systemd in DISTRO_FEATURES: $ bitbake pcmciautils (or btrfs-tools): Package udev was not found in the pkg-config search path. Perhaps you should add the directory containing `udev.pc' to the PKG_CONFIG_PATH environment variable No package 'udev' found Their udev rules file may not be installed according to each pkg's implementation. (From OE-Core rev: a32dac24808bf8621fdbbecb654eff784acee47e) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools/uninative-tarball: Fix deployment overlap issuesuninative-1.4Richard Purdie2016-09-232-4/+4
| | | | | | | | | | | | | | | | | | We still have problems where deploying SDKMACHINE=i686 can cause removal of SDKMACHINE=x86_64 artefacts. The reason is that x86_64 is a BUILD_ARCH as well as an SDK_ARCH and the manifest namespaces overlap. To fix this, set PACKAGE_ARCH and the stamp-extra-into to include SDK_OS. SDK_OS may not be entirely correct but it is what sstate.bbclass uses for nativesdk and fixing that is a separate issue. This is confirmed to resolve artefact problems on the AB which have been delaying a new uninative release. (From OE-Core rev: 1dbc6ec4ca061570d2482c9abebcf720298db9b7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: improve stamp independenceJoshua Lock2016-09-231-2/+13
| | | | | | | | | | | | | | buildtools-tarball shouldn't be regenerated when MACHINE changes, nor should variants for other SDKMACHINE be removed from the deploy directory when SDKMACHINE changes. Remove target architecture dependencies so that deploy artefacts can overlap. (From OE-Core rev: b7d1a310f6b880e92b124a78af3c948abaab4236) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: fix indentationMaciej Borzecki2016-09-221-2/+2
| | | | | | | | (From OE-Core rev: 170157602932aa454e721ea849fbf1679b573618) Signed-off-by: Maciej Borzecki <maciej.borzecki@rndity.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: Make stamp independentRichard Purdie2016-09-221-0/+6
| | | | | | | | | | | | | | | | The uninative tarball only contains nativesdk compoents. It should not get regenerated when MACHINE changes for example. Currently its sstate arch is also incorrect so changing SDKMACHINE results in other variants being removed from the deploy directory. This patch removes the target architecture dependencies so that deploy artefacts can overlap and it doesn't continually rebuild. This also fixes various autobuilder/release artefact issues we're having as a result of these issues. (From OE-Core rev: 6edd0b8dccc6e1e21f2ef87013e2e0a40d19b0d6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: add SDKMACHINE to stamps-extra-infoJoshua Lock2016-09-211-1/+1
| | | | | | | | | | Otherwise the stamps for x86-64 and i686 uninative tarballs match and we can't deploy both to the DEPLOYDIR. (From OE-Core rev: fee426ae0c2b27925b05b856ada676958ee10869) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: add SDKMACHINE to stamps-extra-infoJoshua Lock2016-09-211-1/+1
| | | | | | | | | | Otherwise the stamps for x86-64 and i686 uninative tarballs match and we can't deploy both to the DEPLOYDIR. (From OE-Core rev: 2a9603759fe87d6326c145f6213ffffeb6afc6ae) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dropbear: deterministic selection of system -vs- bundled libtom libsAndre McCurdy2016-09-201-0/+4
| | | | | | | | | | | | | | Dropbear will use system versions of libtommath and libtomcrypt if available. To make builds deterministic, add a PACKAGECONFIG option to choose system libs or force use of the bundled versions. Note that currently there are no libtommath or libtomcrypt recipes in oe-core, so default to using the bundled versions. (From OE-Core rev: b7c2edd2d6ded287d8b34dd047ae84d3fd69d4c6) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dropbear: fix -ltomcrypt -ltommath order when using system libtom libsAndre McCurdy2016-09-202-0/+49
| | | | | | | | | | | | | | | To prevent build failures when using system libtom libraries and linking with --as-needed, LIBTOM_LIBS should be in the order -ltomcrypt -ltommath, not the other way around, ie libs should be prepended to LIBTOM_LIBS as they are found, not appended. Note that LIBTOM_LIBS is not used when linking with the bundled libtom libs. (From OE-Core rev: 62e96283fe77469e24e8df86c6c037c92009b00a) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Create image in correct locationJuro Bystricky2016-09-191-2/+1
| | | | | | | | | | | | | | | | Due to the recipe now using variable IMGDEPLOYDIR instead of DEPLOY_DIR_IMAGE, the final Build Appliance image ended up being created in a wrong location. This patch assures the final ZIP image is created in identical location as before: tmp/deploy/images/<machine>/Yocto_Build_Apliance.zip [YOCTO#10274] (From OE-Core rev: 5ac0604fdc7d5b783011c43d476210b427b5dae0) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: Disable bfs supportPatrick Williams2016-09-161-1/+1
| | | | | | | | | | | | Disable building of mkfs.bfs, which is used to create BFS file-systems used by SCO UnixWare. This is highly unlikely to be utilized and there are otherwise no references to 'bfs' throughout the rest of the tree. (From OE-Core rev: 3226d89ff743c223181fda90f605c7579337941a) Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: Disable minix support.Patrick Williams2016-09-161-5/+4
| | | | | | | | | | | | | | | Disable building of {mkfs,fsck}.minix, which are used to support minix file-systems. Minix predates Linux and support for its file-systems is unlikely to be needed. No recipes otherwise reference minix, except in patches to autotools configuration scripts, so there should be no impact to other recipes. (From OE-Core rev: fc66762d7c112fb798c2444dd902ce03baf975c4) Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* busybox: Avoid race building libbbJuro Bystricky2016-09-155-66/+151
| | | | | | | | | | | | | | | | | | | When building busybox, an occasional error was observed. The error is consistently the same: libbb/appletlib.c:164:13: error: 'NUM_APPLETS' undeclared (first use in this function) while (i < NUM_APPLETS) { The reason is the include file where NUM_APPLETS is defined is not yet generated (or is being modified) at the time libbb/appletlib.c is compiled. The attached patchset fixes the problem by assuring libb is compiled as the last directory. [YOCTO#10116] (From OE-Core rev: a866a05e2c7d090a77aa6e95339c93e3592703a6) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eudev: Add missing pkgconfig dependenciesRichard Purdie2016-09-141-1/+1
| | | | | | | | | | Building eudev from scratch in an sstate build results in configure errors since the pkg-config macros can't be found. Add in a missing pkg-config dependency using the appropriate class to avoid such failures. (From OE-Core rev: 6b527bbfea5088c20da98cd72abe5caa4b399787) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: remove hard-coded reference to gcc -EJérémy Rosen2016-09-142-1/+41
| | | | | | | | (From OE-Core rev: 2c0a72d4e7eafee225e702f4c91cd206bc05ec55) Signed-off-by: Jérémy Rosen <jeremy.rosen@smile.fr> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* busybox: allow overriding compiler name in KConfigJérémy Rosen2016-09-141-1/+1
| | | | | | | | | | | | The KConfig infrastructure needs to build HOST binaries in order to provide its infratstructure. Yocto needs to force the HOSTCC and HOSTCPP variables to BUILD_CC and BUILD_CPP to make sure that the proper compiler is used when compiling host binaries (From OE-Core rev: 50fb24c889b6add053a5638a7367a8896dfebd8a) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: do not enable gtk-doc and explain whyAlexander Kanavin2016-09-091-0/+1
| | | | | | | (From OE-Core rev: ea98b08c65de100623a641505f3160848c8fdf20) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dbus-glib: enable gtk-docAlexander Kanavin2016-09-091-1/+1
| | | | | | | (From OE-Core rev: c7eb50aa65c6168945a8dacda0c3126b098c3c4f) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: drop unused gtkdoc-related variableAlexander Kanavin2016-09-091-2/+0
| | | | | | | (From OE-Core rev: 3fa84900b0a008993dfbf0d5af12416f4bc3980f) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd_230.bb: Set journal RuntimeMaxSize to 64M as defaultAníbal Limón2016-09-081-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | At this time systemd journald uses the /run tmpfs to store logs by default systemd uses 15% of available space [1] of the /run partition, when the space runs out journald starts to vaccum/store the logs into /var/log [1]. It causes two problems one of them is timeout dev-ttySN.device's when enable debug and use journal as systemd.log_target [2] the other is related to don't find syslog entries into the journal log [3]. This problems are now more evident because i recently enabled the systemd debug option in testimage [4]. One area of improvement will be add support in systemd journald to read these parameters from the kernel cmdline like systemd.log_target, if the support exists we could add that parameter at level of testimage. [1] https://www.freedesktop.org/software/systemd/man/journald.conf.html#SystemMaxUse= [2] https://bugzilla.yoctoproject.org/show_bug.cgi?id=8142#c19 [3] https://bugzilla.yoctoproject.org/show_bug.cgi?id=10128#c4 [4] http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=a86a1b2703372c12e7fca18918695d093ea6ee53 [YOCTO #10128] (From OE-Core rev: 808952bf6d2b7549b456293ead4728b4dbf0d89b) 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>