summaryrefslogtreecommitdiffstats
path: root/meta/conf
Commit message (Collapse)AuthorAgeFilesLines
* security_flags.inc: disable -pie and -fpie from Python3 compilation.Topi Kuutela2015-08-091-0/+1
| | | | | | | | | | | | | | | If security_flags.inc is 'required' to the image, -pie and -fpie options are added to CFLAGS. These are not compatible with -shared GCC option. The result is several errors of following form and missing Python3 modules in the image: *.o In function `_start': *.S undefined reference to `main' collect2: error: ld returned 1 exit status (From OE-Core rev: 94818c5240b793464700945d0cf057bffb9e1008) Signed-off-by: Topi Kuutela <topi.kuutela@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* arch-mips.inc: don't override TRANSLATED_TARGET_ARCHDmitry Eremin-Solenikov2015-08-011-4/+0
| | | | | | | | | | | | | | Currently MIPS64 N32 is broken. There is internal disagreement between TARGET_ARCH (which doesn't contain ABIEXTENSION) and TRANSLATED_TARGET_ARCH (which contains ABIEXTENSION). ABI is already encoded into the TARGET_OS. ARM tunes in the same situation override neither the TARGET_ARCH nor the TRANSLATED_TARGET_ARCH. So let's drop this override. (From OE-Core rev: 3ee5c9ad302bc05c75badbe29dd983a043a114c2) Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* arch-armv7a.inc, feature-arm-vfp.inc: add tunes for vfpv3 and vfpv3d16André Draszik2015-07-312-4/+60
| | | | | | | | | | | | | | This adds tunes for ARM's v3 Vector Floating Point unit for 16 and 32 bit implementation: http://www.arm.com/products/processors/technologies/vector-floating-point.php See also https://wiki.debian.org/ArmHardFloatPort/VfpComparison for a nice comparison and why vfpv3d16 is useful. (From OE-Core rev: f9de9521477a1de8f6a399bcdc8260e28e34dfb3) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Add support for nativesdk-gccRichard Purdie2015-07-311-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Being able to build a nativesdk gcc is useful, particularly in cases where the host compiler may be of an incompatible version (or a 32 bit compiler is needed). Sadly, building nativesdk-gcc is not straight forward. We install nativesdk-gcc into a relocatable location and this means that its library locations can change. "Normal" sysroot support doesn't help in this case since the values of paths like "libdir" change, not just base root directory of the system. In order to handle this we do two things: a) Add %r into spec file markup which can be used for injected paths such as SYSTEMLIBS_DIR (see gcc_multilib_setup()). b) Add other paths which need relocation into a .gccrelocprefix section which the relocation code will notice and adjust automatically. This patch adds tweaks to the relocation script to handle the new section too. (From OE-Core rev: cd3d874fced2ee4c950d9964d30c0588fd8772e7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security-flags: Disable PIE for coreutils, elfutils, gcc, iptablesRichard Purdie2015-07-271-2/+4
| | | | | | | | | With gcc 5, we need to disable the PIE flags for more recipes in order to have successful builds. (From OE-Core rev: ec2f1b5af102ab6a8fcc23bf115c8f0451ab7eb8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: update to 4.1Bruce Ashfield2015-07-231-1/+1
| | | | | | | | | | | | Updating the libc-headers to match the 4.1 LTSI kernel version. We also tweak the logic in linux-libc-headers.inc to look in the 4.x subdirectory if a 4.x kernel is specified as the header source. (From OE-Core rev: 3143920c541b55b543b9dcc12b18af4e0e4b7ae1) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-cortexa17: add tunes for ARM Cortex-A17Trevor Woerner2015-07-231-0/+36
| | | | | | | | | | http://www.arm.com/products/processors/cortex-a/cortex-a17-processor.php (From OE-Core rev: bf6fea14d0575e7f2dd6a35c79efb45412d70b76) Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: fix qemu user mode linux for qemuarm64Cristian Iorga2015-07-161-0/+1
| | | | | | | | | | | OLDEST_KERNEL is invalid for aarch64, it didn't exist back in our current version. Use a more recent version for aarch64 to allow user mode qemu to work correctly. (From OE-Core rev: 27149fb98fd9d5bba4e07d256a6a0b4921cf00a9) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add BUILD_ARCH and SSTATE_PKGARCH to HASHBASE whitelistRichard Purdie2015-07-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | As Chris Larson points out in the bug, "BUILD_ARCH changing doesn't change native/cross sstate checksums, because its calculated in ${@}, so just its unexpanded form is in the signature. But BUILD_ARCH ends up included in the sstate filenames, so changes to BUILD_ARCH will result in rebuilds of native/cross but not rebuilds of the target recipes which depend on them, which is just what we want." However it does mean we can't easily test 32 and 64 bit signatures. In order to make the tests work, we need to add BUILD_ARCH to the HASHBASE whitelist. BUILD_ARCH is used in the workdir paths and so on so changing it does still rebuild when we need it to. With improvements to function dependency tracking, a dependency on SSTATE_PKGARCH was also introduced causing problems for 32/64 bit build signature equivalence. Since this is reflected in the sstate filenames, we can safely whitelist this too. [YOCTO #5970] (From OE-Core rev: 4f6636be97e654c7f3d58e2649328b1dde8ef696) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: eliminate FORTIFY_SOURCE for debug buildsJoe Slater2015-07-081-3/+8
| | | | | | | | | | | | If -D_FORTIFY_SOURCE=2 is included in CFLAGS for debug builds, many warnings will be generated and some packages will fail to build. So, only conditionally include it. (From OE-Core rev: 1b576012a6a2b2ebc2c507cdaebd62174810b191) Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-core2.inc: set X86ARCH32 to i686 (instead of i586)Andre McCurdy2015-07-021-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use i686 as TARGET_ARCH for 32bit core2 (and corei7 and atom) builds. In most cases, i586 and i686 are equivalent values for TARGET_ARCH, however one important exception is glibc. When configured for i686, glibc enables optimised string functions (SSE, SSE2, etc), which are not used when building for i586. The benefits of i686 optimised string functions vary depending on the application and the CPU, however in some cases the improvements are significant. In one test, a 50% increase in FPS was seen when running the 'smashcat' benchmark [1] in a qtwebkit browser on an Intel Atom based SoC. The gain seems to comes from a 3x improvement in memcpy performance when copying graphics buffer lines (5120 bytes, or 1280 x 4 bytes/pixel), from the CPU to GPU. Note that very large memcpy's (e.g. 32MB) on the same machine show no particular performance increase between i586 and i686. [1] http://www.smashcat.org/av/canvas_test/ Warning: The change in TARGET_ARCH means that _i586 architecture specific over-rides will no longer take effect. Both oe-core and meta-oe have been updated to replace _i586 over-rides with _x86, however other layers may still need review and updating. (From OE-Core rev: dd09fab685de2eaf04aa5ab60f8220b89c1deae9) 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>
* feature-arm-thumb.inc: Fix ARMPKGSFX_THUMB valueMartin Jansa2015-07-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * my previous thumb related commit: commit 3e760031f91fb87c3e2f62b77a117eb41164f259 Author: Martin Jansa <martin.jansa@gmail.com> Date: Wed Feb 18 15:40:35 2015 +0100 feature-arm-thumb.inc: respect ARM_INSTRUCTION_SET when adding thumb suffix unfortunately removed conditional on "thumb" in TUNE_FEATURES, when setting ARMPKGSFX_THUMB * in case we have MACHINE without "thumb" in TUNE_FEATURES and distro setting ARM_INSTRUCTION_SET to "thumb" we end with: ARM_INSTRUCTION_SET="thumb" ARM_THUMB_OPT="thumb" ARM_M_OPT="thumb" # TUNE_CCARGS correctly not adding -mthumb TUNE_CCARGS=" -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon" # but ARMPKGSFX_THUMB and TUNE_PKGARCH including "t2": ARMPKGSFX_THUMB="t2" TUNE_PKGARCH="armv7at2-vfp-neon" # causing following error: Error, the PACKAGE_ARCHS variable does not contain TUNE_PKGARCH (armv7at2-vfp-neon). (From OE-Core rev: 951200673af27538beaef647a33308b4f15d1fb0) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: document KERNEL_CLASSESMarek Vasut2015-07-021-0/+1
| | | | | | | (From OE-Core rev: 4809aa9c9d5ac13b30cac1aeada09584f53eecbe) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-i586-nlp: Add new tune file to support Quark/X1000 CPUSaul Wold2015-07-011-0/+19
| | | | | | | | | | This tune file is needed to enable a GAS option specific to this cpu family in order to disable the usage of lock prefix instructions. (From OE-Core rev: 7eb0abc5f4d971d9a511c93cfb2eb52b72e6f228) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: Add explict getVar param for (non) expansionRichard Purdie2015-06-231-8/+8
| | | | | | | | | | | | | | Rather than just use d.getVar(X), use the more explict d.getVar(X, False) since at some point in the future, having the default of expansion would be nice. This is the first step towards that. This patch was mostly made using the command: sed -e 's:\(getVar([^,()]*\)\s*):\1, False):g' -i `grep -ril getVar *` (From OE-Core rev: ab7c1d239b122c8e549e8112c88fd46c9e2b061b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags.inc: remove duplicated over-ridesAndre McCurdy2015-06-231-2/+0
| | | | | | | | | | | | | The following over-rides were both defined twice: SECURITY_CFLAGS_pn-grub-efi-x86-64-native SECURITY_CFLAGS_pn-ltp (From OE-Core rev: dfae10889ab0fce2bae94294a78f4ea0aaf1b81e) 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>
* Add license file XFree86-1.0Kai Kang2015-06-111-1/+1
| | | | | | | | | | | | | | | Add license file XFree86-1.0 which is needed by packages such as hwdata. It is from: http://www.x.org/archive/X11R7.5/doc/LICENSE.html#AEN28 And add 'XFree86-1.0' to SRC_DISTRIBUTE_LICENSES. (From OE-Core rev: be91551041c623e7e9b34780cc6322f898f8cf7f) 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>
* documentation.conf: Document do_vmimgJuro Bystricky2015-06-111-1/+1
| | | | | | | | | | Changes due to new combined support for both vmdk and vdi files. (From OE-Core rev: e4244af33888ef3c39e31ed89c5184f6a4c5e80c) 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>
* sanity.conf: Bump minimum bitbake version to 1.27.1 for sstate changeRichard Purdie2015-06-101-1/+1
| | | | | | (From OE-Core rev: b925be92e8be2ab3b945069a699859809615c78f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xserver-xorg: Upgrade 1.16.3 -> 1.17.1 (OELAYOUT_ABI change)Jussi Kukkonen2015-06-031-1/+1
| | | | | | | | | | | | | | | | | | | * Increase OELAYOUT_ABI: this is required because the xf86-video-modesetting package moves from its own recipe to xserver-xorg and sanity check cannot handle that currently. The upgrade will delete old xf86-video-modesetting files from sysroots. * Remove upstreamed xserver-xorg patches * Remove xf86-video-modesetting recipe: the driver is now included in xserver-xorg recipe, which now produces the xf86-video-modesetting package. The package version changes from 0.9 to 1.17.1 * Update xserver-xorg license checksum: modesetting license info (another MIT one) has been added to the file (From OE-Core rev: 950846d019ffac21909a96d90af8cf7e5bdd5738) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* soc-family.inc: Add a default SOC_FAMILY valueRichard Purdie2015-06-031-0/+1
| | | | | | | | | | | | | | | | | Otherwise, if MACHINEOVERRIDES is expanded before SOC_FAMILY is set (which may happen as MACHINEOVERRIDES is included in OVERRIDES) we can see: ExpansionError: Failure expanding variable MACHINEOVERRIDES, expression was ${@['', '${SOC_FAMILY}:']['${SOC_FAMILY}' != '']}p1022ds which triggered exception SyntaxError: EOL while scanning string literal (MACHINEOVERRIDES, line 1) To avoid this, give SOC_FAMILY a default empty value so it doesn't get read as None. (From OE-Core rev: dee005b6e1bc353230f9f27a469b2054a644e542) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: Add comment about what it does and who uses itRichard Purdie2015-05-301-0/+7
| | | | | | | | | It was pointed out that people couldn't easily see who used this or why so add some comments about that. (From OE-Core rev: 67f09e9086b8fb1c0c8a1dd19419afb1a5af8daf) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Use immediate expansion for os.uname()Richard Purdie2015-05-291-2/+4
| | | | | | | | | | Use immediate expansion for BUILD_ARCH and BUILD_OS since there is no point in repeatedly calling os.uname() throughout parsing. This is worth around 2% of parsing time, small but measurable. (From OE-Core rev: 03482382b797f3501c3fb0df0fe12bd4e5e51a39) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: programatically generate COMBINED_FEATURESRoss Burton2015-05-241-11/+1
| | | | | | | | | | | Instead of hard-coding the set of features that can be considered in COMBINED_FEATURES, simply generate the intersection of DISTRO_FEATURES and MACHINE_FEATURES. (From OE-Core rev: a66f812d4395dc27e22d0c99568aed0a6493df12) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/base.bbclass: Drop PRINC supportRichard Purdie2015-05-051-1/+0
| | | | | | | | | | | | PRINC is no longer needed since we have the PR service instead which people should be using. Drop the PRINC code. This has been deprecated with a warning and then an error for quite some time so we can remove it now. (From OE-Core rev: a4d530bcf55f03258078c10a123e2717444e1060) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: Add python-numpy to pie incompatible listRichard Purdie2015-05-031-0/+1
| | | | | | | | | With poky-lsb (security flags enabled), python-numpy doesn't build with pie flags. (From OE-Core rev: d4694ac5e18db1d0db314d0d8b1104c073037a60) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: backfill bluez5 featureCristian Iorga2015-05-031-1/+1
| | | | | | | | | | | If bluez4 is not explicitly passed as a distro feature, bluez5 should be used as the default, so backfill it. (From OE-Core rev: ae2d2fbafab638fa6c2496a836c8d00529a40d83) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-distrovars: Clean up gcc license issuesRichard Purdie2015-04-301-1/+1
| | | | | | | | | | | | | | | There are several entries here which are not needed with the modern license handling code: gcc-source - moved to direct handling in base.bbclass (due to version appended to the name) libgcc - Listed as GPLv3 exception for its packages libgcc-initial - Listed as GPLv3 exception gcc-runtime - Indivisual packages listed as GPLv3 exception where appropriate (From OE-Core rev: 48c4922ab921a1bb2103cc331d0839febd36beb8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-shared-source: Add PV to PNRichard Purdie2015-04-301-1/+0
| | | | | | | | | | | | | | | | | | This means you can have one gcc version for some gcc recipes (e.g. crosssdk/nativesdk) and another gcc version for target code. Also remove the preferred version entry from the default toolchains list since the version issue is now handled automatically. We also need to specifically handle gcc-source in the license handling code since expanding ${PV} in the base class isn't possible. Since gcc-source doesn't generate any packages directly this shouldn't be an issue and whitelisting in this way is easiest (and matches the rest of the toolchain handling). (From OE-Core rev: 67db7182faf6742b0d971d61d8c5ba34f69d2e12) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* musl: Enable NLSKhem Raj2015-04-131-1/+1
| | | | | | | | | | | | It supports it, so lets enable it even though we can compile lot of stuff without NLS but its harder to get them all compiled without NLS Change-Id: I49a06c05b004654dabbef980c4e6ad991d581341 (From OE-Core rev: 6cf978dfcc90632680db15b58f8f9edbbd7c083b) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add sed-native to ASSUME_PROVIDEDDmitry Eremin-Solenikov2015-04-131-0/+1
| | | | | | | | | | There is no reason to build sed for the host, however now: ERROR: Nothing RPROVIDES 'sed-native' (but virtual:native:/OE/sources/openembedded-core/meta/recipes-extended/groff/groff_1.22.2.bb RDEPENDS on or otherwise requires it) (From OE-Core rev: 5111407cfe59bd368e2528d953282b74d78057ed) Signed-off-by: Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags.inc: elfutils on ARM fails with PIE flagsDenys Dmytriyenko2015-04-091-0/+1
| | | | | | | | | | The error messages look like this: R_ARM_TLS_LE32 relocation not permitted in shared object (From OE-Core rev: a915adfd1eaad9a0d65dffe9da92811284e491c8) Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcmode-default: Pin gdb to 7.9Khem Raj2015-04-081-1/+1
| | | | | | | | Change-Id: I034a3bf7b9288df4579744f242e990f213193e85 (From OE-Core rev: 00e4324aee6ad436e1a4fbdd968c51cd01273f05) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: upgrade to 2.25Robert Yang2015-04-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Remove the following patches since they are already in the new code: binutils/fix-pr15815.patch binutils/fix-pr16428.patch binutils/fix-pr16476.patch binutils/fix-pr2404.patch binutils/replace_macros_with_static_inline.patch binutils/binutils_CVE-2014-8484.patch binutils/binutils_CVE-2014-8485.patch binutils/binutils_CVE-2014-8501.patch binutils/binutils_CVE-2014-8502.patch binutils/binutils_CVE-2014-8502_1.patch binutils/binutils_CVE-2014-8503.patch binutils/binutils_CVE-2014-8504.patch binutils/binutils_CVE-2014-8737.patch * The file src-release is gone. * Updated patches for the new code. (From OE-Core rev: a8446ea78daa5875de43eb5bcccd8f536ea07e1c) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> Conflicts: meta/conf/distro/include/tcmode-default.inc Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toaster: update toasterconf.json for fido releaseBelen Barros Pena2015-03-311-5/+20
| | | | | | | | | | | | | | | | | | We update the toasterconf.json for the 1.8 "fido" release. A small update to the release help text in the toasterconf.json file shipped with the openembedded-core layer. We now make explicit that Toaster will build with the tip of the selected branch, and we add links to the OpenEmbedded repository. (From OE-Core rev: f5af78cabb693692fa369730af4b0c70cca9bc91) Signed-off-by: Belen Barros Pena <belen.barros.pena@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcmode-default: Define one gdb versionKhem Raj2015-03-201-0/+5
| | | | | | | | | | | | | Sometimes we need to override the gdb from third party tool SDKs, this helps out, moreover it also makes it consistent with in OE-Core too to have multiple versions of gdb if we ever needed to Change-Id: Ibe1ae59175984bbc661c243764c81cd99fef54d1 (From OE-Core rev: aa75579aae064f2f9fc70bea093a6e9c8ca9c528) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: use http:// for GNU_MIRROR instead of ftp://Koen Kooi2015-03-161-1/+1
| | | | | | | | | | | | | | | | | | | The past few weeks ftp://ftp.gnu.org has been intermittently giving errors like this: WARNING: Failed to fetch URL ftp://ftp.gnu.org/gnu/emacs/emacs-23.4.tar.gz;name=tarball, attempting MIRRORS if available ERROR: Fetcher failure: Fetch command failed with exit code 4, output: Cannot parse PASV response. accept: Connection timed out Cannot parse PASV response. Error in server response, closing control connection. Which is annoying because binutils lives there. Using http://ftp.gnu.org hasn't given any problems so far. (From OE-Core rev: 25fe8d95298a457e828190412d7148470edc5592) Signed-off-by: Koen Kooi <koen.kooi@linaro.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: bump version as error-report interface changedRoss Burton2015-03-101-1/+1
| | | | | | | | | | The error-report tooling command-line options were changed and anyone doing automated builds and using error-reports needs to know what options to parse. (From OE-Core rev: 99f209a49a4390192b95184ff86bd6f973010111) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: remove PIE flags from flex and gstreamer1.0-plugins-badRoss Burton2015-03-021-0/+2
| | | | | | | | | | | These recipes both fail to build with "relocation R_X86_64_PC32 against undefined hidden symbol `__init_array_start' can not be used when making a shared object" when using PIE. (From OE-Core rev: 37e6e62f0faae3fa16421b051599aea0e03a5825) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/sanity: avoid bblayers version issue when switching between poky and ↵Paul Eggleton2015-02-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | other DISTRO values If you create a build directory with poky, or set DISTRO to "poky" and run bitbake, you'll get a bblayers.conf file with LCONF_VERSION set to 6. If you then set DISTRO to any other value where the new distro config doesn't pull in poky's config, e.g. "nodistro", you would then get a bblayers.conf version error which didn't immediately make sense. (The layer versions have been out-of-step ever since meta-yocto-bsp was split out of meta-yocto several years ago). This is just painful and we'd rather users didn't have to deal with it. Obviously it isn't an OE-Core problem per se, but a simple way to resolve it for everyone is to bump OE-Core's version to 6 with an automatic no-op upgrade. Also ensure that multiple upgrade functions (such as the poky one) have a chance to execute by not breaking out of the loop as we were before. Fixes [YOCTO #6139]. (From OE-Core rev: 2fdeee2fad69445b0d97148826c7b027820be63a) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Python: Upgrade from 2.7.3 to 2.7.9:Alejandro Hernandez2015-02-231-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Based on Paul Eggletons work to partially upgrade to Python 2.7.6 Modified: default-versions.inc: switched to python 2.7.9 generate-manifest-2.7.py: fixed _sysconfigdata python-2.7-manifest.inc: fixed _sysconfigdata python.inc: Updated checksums and source, no LICENSE change just updated some dates python-native_2.7.3 -> python-native_2.7.9 and updated patches python_2.7.3 -> python_2.7.9, and added ac_cv_file__dev_ptmx=no ac_cv_file__dev_ptc=no in EXTRA_OECONF to solve python issue #3754, only needed when cross compiling, also updated patches use_sysroot_ncurses_instead_of_host.patch: New patch to use ncursesw from sysroot instead of hosts, introduced by fix for python issue #15268 Rebased: 01-use-proper-tools-for-cross-build.patch 03-fix-tkinter-detection.patch 05-enable-ctypes-cross-build.patch 06-avoid_usr_lib_termcap_path_in_linking.patch avoid_warning_about_tkinter.patch builddir.patch fix_for_using_different_libdir.patch host_include_contamination.patch multilib.patch nohostlibs.patch search_db_h_in_inc_dirs_and_avoid_warning.patch Deleted (fixed on upstream): 06-ctypes-libffi-fix-configure.patch CVE-2013-4073_py27.patch gcc-4.8-fix-configure-Wformat.patch json-flaw-fix.patch posix_close.patch pypirc-secure.patch python-2.7.3-CVE-2012-2135.patch python-2.7.3-CVE-2013-1752-smtplib-fix.patch python-2.7.3-CVE-2014-1912.patch python-2.7.3-CVE-2014-7185.patch python-2.7.3-berkeley-db-5.3.patch python-fix-build-error-with-Readline-6.3.patch remove-BOM-insection-code.patch remove_sqlite_rpath.patch python2.7.3-nossl3.patch [YOCTO #7059] (From OE-Core rev: d4ad95f0d5f08891637c644e85b09da9c4585059) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* machine/qemu: Switch from ext3 to ext4Richard Purdie2015-02-211-1/+1
| | | | | | | | | | There is no good reason not to use ext4 at this point, it has advantages and few drawbacks. Therefore switch the qemu machines over (and the default runqemu script options). (From OE-Core rev: 430b9ae71b1aa76f8421127d17e0e0723d4818d3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: set a variable to map to the OE Layer Index namePaul Eggleton2015-02-211-0/+2
| | | | | | | | | | | | | | | | | | | Add a variable that allows us to map the OE-Core layer to the name that represents it in the OpenEmbedded layer index. This will be used by bitbake-layers layerindex-fetch so that it knows that for example OE-Core is already fetched and included in the current configuration. Note - it won't be required for us to go around and set this for every layer - we can do the matching based on repo and subdirectory, but OE-Core is somewhat special in that it does sometimes appear in different places, for example in poky. [YOCTO #5348] (From OE-Core rev: d1cf0edd79ec3ba3bd17126183e4cb99aa50ffaf) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add two variables for layer indexChong Lu2015-02-211-0/+6
| | | | | | | | | | | | Add BBLAYERS_LAYERINDEX_URL variable that bitbake-layers can use to find layer index. Add BBLAYERS_FETCH_DIR variable that bitbake-layers can use to specify fetch directory. [YOCTO #5348] (From OE-Core rev: ae585a7d2744222606aeb533815d22ade8e10097) Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tclibc-musl: Use musl for providing virtual/libintl instead of gettextKhem Raj2015-02-211-1/+1
| | | | | | | | | | Lets try to use musl version of libintl and see how far we get Change-Id: I0259049eb6461ab9b579c7f3ad401fefede24621 (From OE-Core rev: 4ed94affbce657db58c5099c8882a8d0292abaf1) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* arch-armv7a.inc, tune-arm920t.inc: Fix PACKAGE_EXTRA_ARCHSMartin Jansa2015-02-212-2/+2
| | | | | | | | | | | | | * each DEFAULTTUNE with thumb enabled should list it's arm variants in PACKAGE_EXTRA_ARCHS, otherwise packages which force arm ISA won't be found in do_rootfs * armv7athf-neon-vfpv4 was missing its own PACKAGE_ARCH and also the arm variant (From OE-Core rev: fd7f3cd9affbfb9ce483a5a1d6054da2365fcb0e) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* feature-arm-thumb.inc: respect ARM_INSTRUCTION_SET when adding thumb suffixMartin Jansa2015-02-211-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * this means that recipes with ARM_INSTRUCTION_SET explicitly changed to arm will be built in feed without thumb suffix, the same does apply for workdir, e.g. after "bitbake glib-2.0" you can see: tmp-glibc/work/armv5e-oe-linux-gnueabi: glib-2.0 glibc glibc-initial tmp-glibc/work/armv5te-oe-linux-gnueabi: acl db gdk-pixbuf kmod .... and tmp-glibc/deploy/ipk: all armv5e armv5te qemuarm * feed config should be ok, because all default DEFAULTTUNEs always include "arm" variants of all supported PACKAGE_ARCHs * for more details see http://lists.openembedded.org/pipermail/openembedded-core/2014-April/091960.html the toolchain path issues were resolved in 1.8 * add ARM_INSTRUCTION_SET = "arm" to glibc-collateral.inc and comment in glibc.inc to fix glibc-locale and glibc-scripts build (From OE-Core rev: 3e760031f91fb87c3e2f62b77a117eb41164f259) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: update to 3.19Bruce Ashfield2015-02-211-1/+1
| | | | | | | | | Updating the libc-headers now that the kernel has released. (From OE-Core rev: b3721560fe523c144690ebfeb203b3735d0f6843) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Upgrade 2.20 -> 2.21Khem Raj2015-02-201-1/+1
| | | | | | | | | | | | | | Drop CVE backports and ppc/fpu detection patch which is not needed anymore Forward port eglibc option groups patch Default to using glibc 2.21 Additional patches needed to appease -Werror option Change-Id: I1873097cec8387ea9e8186a255122938fc28c976 (From OE-Core rev: 6617cc92076764d51f0190786f8d62b8c99ae984) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers: Set the preferred provider for bluez based on versionRichard Purdie2015-02-171-1/+1
| | | | | | | | | | | | | | | bitbake will currently 'selecting bluez4 to satisfy runtime libasound-module-bluez due to PREFERRED_PROVIDER_bluez4 = bluez4' which in the case of bluez5 isn't correct. This slightly unusual construct avoids this. Ultimately this is a bitbake issue that needs fixing in a better way but this means we can merge the bluez5 changes until bitbake gets fixed. (From OE-Core rev: ef41f4b91d65f87850edd6cc56ca37d2ecb56378) Signed-off-by: Cristian Iorga <cristian.iorga@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-20 10:22:39 +0000