summaryrefslogtreecommitdiffstats
path: root/meta/conf
Commit message (Collapse)AuthorAgeFilesLines
...
* layer.conf: Whitelist cantarell-fonts fontconfig dependencyRichard Purdie2016-03-021-0/+1
| | | | | | | | | fontconfig is a stable API dependency and allarch fonts are desirable. This matches the other fonts. (From OE-Core rev: 93ca16b2f822e4bd8681d65464563f5456c613ea) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-cortexa9.inc: add vfpv3 tunesRichard Tollerton2016-02-281-0/+15
| | | | | | | | | | | | | Define tunnings to enable 32 register VFPv3 for cortexa9 processor cores More details: http://www.arm.com/products/processors/technologies/vector-floating-point.php (From OE-Core rev: d9635cc96ad1ddeb944bba375b5b55149867966c) Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> 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>
* adt-installer: Drop since its replaced by the extensible SDKRichard Purdie2016-02-283-3/+1
| | | | | | | | | | | | | | The extensible SDK replaces adt-installer so this can be removed now, all future effort in this direction will be placed onto that. This includes a layer version change so the autobuilder knows when to stop building adt-installer. [YOCTO #6404] (From OE-Core rev: c413164c03bdce38f41e63ad2a27dc6108521b9a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity: Improve configuration upgrade capabilities (support meta-yocto -> ↵Richard Purdie2016-02-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | poky transition) Right now, only one configuration file can be processed (conf/bblayers.conf) and it can only have one version number. This is a cause of immense friction between OE-Core and Poky since if one needs a version change, it shouldn't be forced on the other. We'd like to rename the meta-yocto layer (within the meta-yocto repository) to meta-poky. To do this, we need to correct the bblayers.conf file and that means changing the sanity version. After the pain this caused the last time, Paul made me promise never to have them out of sync between OE-Core and Poky, equally, having every distro changing config update OE-Core isn't scalable either. This patch changes the sanity upgrade method to list a more generic format: <config file>:<current version variable name>:<required version variable name>:<upgrade function> This in theory allows us to support upgrades to any of the core configuration files, and allow layers to extend them as needed. Files with the same name can be handled in different layers by setting a unique version name variable in the file itself. The upgrade code is only called if the version variable is set. To allow us to make the poky name change and use a new configuration file name, one last version bump is included for poky to handle the transition. (From OE-Core rev: 10fd24271e771ed12e36edcff0007caa1a4e67e4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add findutils-native to ASSUME_PROVIDEDRoss Burton2016-02-261-0/+1
| | | | | | | | | | | | It's possible for findutils-native to get built. There's no point in this as this is part of the expected host platform but this can introduce races or even bugs (4.5.19 appears to have a leaking fd bug, resulting in asserts) so add it to ASSUME_PROVIDED so it definitely won't get built. (From OE-Core rev: b753dae334641480cb4a232ce240f9f56be5568f) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: Disable ssp when compiling uclibcKhem Raj2016-02-221-0/+4
| | | | | | | (From OE-Core rev: 208fbdbff17f19a23944a62f1b9ff380f1bc8ac8) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Upgrade to 2.23Khem Raj2016-02-211-2/+2
| | | | | | | | | | | Drop kconfig and options-group support Forward port cross-localedef support Assume ssp support in libc when building gcc-initial (From OE-Core rev: 9c3d461c4d54d684b38ec4c038a1c3c2fb9923f0) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* no-static-libs: remove eglinfoRoss Burton2016-02-211-3/+2
| | | | | | | | | | waf.bbclass disables no-static-libs for all waf recipes, so we don't need to have it explicitly disabled here now. (From OE-Core rev: 6eb64cdd5296c42a46f3485bca403814eec55b2c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-scripts.bbclass: add three other path to PATH in env.shJun Zhang2016-02-211-0/+3
| | | | | | | | | in sdk,there are some utils in sysroot/host-os/bin, sysroot/host-os/sbin/,sysroot/host-os/usr/bin need to use, so add these three paths to PATH in env.sh. (From OE-Core rev: 1116572916443109176c0df32efc275eceeb706a) Signed-off-by: Jun Zhang <jun.zhang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* no-static-libs.inc: Add libcap-nativeRichard Purdie2016-02-181-0/+1
| | | | | | | | We need to disable static flags for libcap-native as well. (From OE-Core rev: b1fa25a238d118f433759102b13896094394ceeb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: use target path as compile dir in debugging infoHongxu Jia2016-02-181-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In debugging information, it uses target paths rather than build ones as compile dir. ... -fdebug-prefix-map=old=new When compiling files in directory old, record debugging information describing them as in new instead. ... Compile without this fix: objdump -g git/test.o ... The Directory Table (offset 0x1b): | 1 /buildarea/raid0/hjia/build-20160119-yocto-buildpath/tmp/sysroots/x86_64-linux/usr/lib/ i686-pokymllib32-linux.lib32-gcc-cross-initial-i686/gcc/i686-pokymllib32-linux/5.3.0/include | 2 /buildarea/raid0/hjia/build-20160119-yocto-buildpath/tmp/sysroots/lib32-qemux86-64/usr/include/bits | 3 /buildarea/raid0/hjia/build-20160119-yocto-buildpath/tmp/sysroots/lib32-qemux86-64/usr/include ... Compile with this fix: objdump -g git/test.o ... The Directory Table (offset 0x1b): | 1 /usr/lib/i686-pokymllib32-linux.lib32-gcc-cross-initial-i686/gcc/i686-pokymllib32-linux/ 5.3.0/include | 2 /usr/include/bits | 3 /usr/include ... [YOCTO #7058] (From OE-Core rev: 0fe42caad8f7c142741a28b09458f4e2fdf289ff) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Add gstreamer1.0-meta-base to SIGGEN_EXCLUDERECIPES_ABISAFERichard Purdie2016-02-161-0/+1
| | | | | | | | | | This recipe and its packages are by design like a packagegroup and can be safely depended not to change names upon despite it being machine specific. (From OE-Core rev: e3d879c5c222bc27b2e78cdb097aab9820f2c68b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/no-static-libs: add explicit rule for libicalRoss Burton2016-02-161-0/+2
| | | | | | | | | | cmake doesn't have a standard for disabling static libraries so libical needs an explicit statement. (From OE-Core rev: 1a14bc0cc7f1a56833cca7baf12ed5a979854a7b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: Add SECURITY_CFLAGS to TARGET_CC_ARCH for binutilsKhem Raj2016-02-161-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | libtool decides to filter out -fstack-protector-strong on its own and its documented here https://www.gnu.org/software/libtool/manual/html_node/Stripped-link-flags.html this causes linking errors when linking libbfd.so since objects (.o) are compiled using -fstack-protector-strong so they are expecting to link with libssp but the option goes missing in linker flags. With this patch the security flags are hoisted upto CC itself and libtool thankfully does not touch CC. Adding to CC also means that we can now remove it from LDFLAGS since when gcc driver is used to do linking then we have LD = CC and this option makes to linker cmdline Since CC is used without CFLAGS in configure tests, some tests fail complaining that -Olevel is not used while using _FORTIFY_SOURCE therefore added SELECTED_OPTIMIZATION to TARGET_CC_ARCH as well (From OE-Core rev: 9349f28531619a4ff15c382dacc460d61e3ec7af) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Remove unhelpful default value for EXTRA_OEMAKEMike Crowe2016-02-151-1/+1
| | | | | | | | | | | | | | | Setting EXTRA_OEMAKE to "-e MAKEFLAGS=" by default is a historical accident and many classes (e.g. autotools.bbclass, module.bbclass) and recipes have to override this default in order to work with sensible build systems. Now that openssl and pciutils have been fixed to set EXTRA_OEMAKE explicitly it is possible to set EXTRA_OEMAKE = "". (From OE-Core rev: aeb653861a0ec39ea7a014c0622980edcbf653fa) Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/distro/include: Add no-static-libs.incRichard Purdie2016-02-151-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Static libraries are old technology. We've left them around since in previous tests, they only added around 5% to the overall build time. With new and interesting uses of OE, they're becoming more problematic. For example, sstate becomes much larger with static libs enabled which increases the size of eSDK and increases the time taken for sstate operations. Since the static libs contain all the debugging symbols, they're also pretty huge. This patch adds a common include file which allows the user or distro to disable the static libraries in the majority of cases. There are some libs where we do need the static lib, a good example being pseudo-native which uses sqlite3-native static libs. These are left enabled by the include file, as are recipes where --disable-static doesn't work, or isn't supported. This list can likely be reduced over time as individual corner cases are addressed. Maintaining this list in a common location is more desireable than everyone doing it themselves. Poky will switch to using this, OE-Core will need to discuss that as its default. (From OE-Core rev: 773c9e18071d71454473dd81aff911104a2e9bc6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu.inc: Add rng-tools to qemu imagesSaul Wold2016-02-151-0/+2
| | | | | | | | | | | | | | This patch adds rng-tools to MACHINE_EXTRA_RRECOMMENDS so that can be used to provide the additional entropy to prevent hangs in getrandom() for qemu images [YOCTO #8681] [YOCTO #8816] (From OE-Core rev: cb512c0c189f5a1196da233042113a708243daa0) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity: Bump minimum version to 1.29.0Richard Purdie2016-02-121-1/+1
| | | | | | | | | This requires the python expansion changes and allow SRCPV to work correctly without errors. (From OE-Core rev: 40efff29ad458937222c3dbeba070c525103907c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: remove unused ALLOWED_FLAGSRoss Burton2016-02-111-3/+0
| | | | | | | | | This variable hasn't been used for a *long* time, remove it from bitbake.conf. (From OE-Core rev: 91c1235a1614a0b097f0a9efdd13436412a35387) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/conf/layer.conf: adapt to more flexible initramfs-framework RDEPENDSPatrick Ohly2016-02-111-1/+1
| | | | | | | | | | | | | initramfs-framework now RDEPENDS on ${VIRTUAL-RUNTIME_base-utils}, which can be busybox or some alternative like toybox. Making the SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS exception flexible, too, ensures that distros using toybox still pass the selftests. (From OE-Core rev: d17dae0b292ad2c0539712c048bf8cace96dac41) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-corei7.inc: tell qemu to emulate a matching processorRoss Burton2016-02-111-0/+4
| | | | | | | | | | | | | | | | | | | | | If tune-corei7 is in use then the target binaries may contain instructions that qemu-x86-64 can't execute by default, resulting in errors on rootfs construction: NOTE: Running intercept scripts: NOTE: > Executing update_font_cache intercept ... qemu: uncaught target signal 4 (Illegal instruction) - core dumped In this case the instruction is popcnt, part of SSE4.2, so tell Qemu to emulate the CPU that the tune targets (in this case, Nehalem). Also pass check=false as the Nehalem machine supports VME but user-space qemu doesn't, which produces a warning unless CPUID checking is disabled. [ YOCTO #8888 ] (From OE-Core rev: fef106b9b97ec48bad2b9a084357b884f653d6c8) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/base: Improve handling of SRCPVRichard Purdie2016-02-101-1/+2
| | | | | | | | | | | | | | If SRCPV is set, it can be expanded when SRC_URI doesn't support it leading to errors. Avoid doing this by setting it only when it makes sense. This patch depends on the bitbake python expansion patch series. [YCOTO #7772] (From OE-Core rev: ce64da2b80f99c82d96513d8dfb5e572757b0cda) 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>
* 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>
* gtk-theme-torturer: remove from oe-coreRoss Burton2016-02-061-1/+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>
* bitbake.conf/native/nativesdk: Set PKG_CONFIG_SYSTEM_ at top levelRichard Purdie2016-02-061-0/+2
| | | | | | | | | | | | | | 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>
* meta: add ASSUME_PROVIDED dependency on wget-native for http fetchesRoss Burton2016-02-041-0/+1
| | | | | | | | | | For clarity and consistency, add a dependency on wget-native for any URIs that will be fetched using the wget fetcher, and add wget-native to ASSUME_PROVIDED. (From OE-Core rev: 91583704383aef3d4742630380fd3f1d38c4b00a) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation.conf: align the documentation for DEBUG_OPTIMIZATION and ↵Pascal Bach2016-02-041-2/+2
| | | | | | | | | FULL_OPTIMIZATION with bitbake.conf (From OE-Core rev: 2218490b075b077683f17b643ab211c7716d0dfc) Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* machine/include: drop tune-cortexm*.inc and tune-cortexr4.incAndre McCurdy2016-02-023-41/+0
| | | | | | | | | | | | | | The Cortex M1, M3 and R4 CPU tuning files are poorly tested (if at all). They have no obvious users either inside or outside oe-core. Until OE officially gains support for CPUs without an MMU, these tuning files are probably better maintained outside of oe-core (e.g. in a separate meta-nommu layer). (From OE-Core rev: 7a1445c55de904115b950c8e50432a9f11f02208) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Upgrade to 2.26Khem Raj2016-02-011-1/+1
| | | | | | | (From OE-Core rev: 86ade2cc2553c942d9526c5323a11ae151653505) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc, qemuppc: Explicitly disable forcing SPE flagsKhem Raj2016-01-312-1/+3
| | | | | | | | | | | | | | | | | | | | | G4 does not have SPE, so we make that explicit in the tune files and since we emulate G4 when building Qemu, we ensure it for qemuppc as well. GCC config for powerpc-linux is made to include SPE by default which is equivalent if the tripet was powerpc-linux*spe, this forces gcc to configure assembler to enable -mspe by default, when we do that then the kernel fails to compile with binutils 2.26, since newer assembler is smart to detect the tlbia instructions are not compatible with SPE and hence the kernel build breaks rightly. We configure the kernel for G4 as well where it enables tlbia instrucitons rightly so because it thinks its being configured for power4. So we keep the options but do not force -mspe down to assembler as default. (From OE-Core rev: 7a51776a830167e43cbd185505f62f328704e271) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: stop exporting PATCH_GET = "0"Andre McCurdy2016-01-301-10/+0
| | | | | | | | | | | | | | | | Exporting PATCH_GET = "0" has been redundant since patch 2.6.0 was released in 2009: http://git.savannah.gnu.org/cgit/patch.git/commit/?id=b008dece18e6b94b8a13ea44a253855bf407ed01 Host distros which shipped with patch 2.5.x (e.g. Centos 5) are no longer supported, so this export can be retired from bitbake.conf. (From OE-Core rev: e9638fe60d24325e85dacc0c1551f671daed5c06) 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>
* libc-package.bbclass: add LOCALE_UTF8_IS_DEFAULTRichard Tollerton2016-01-302-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | python hard-codes the encoding of many locales; for instance, en_US is always assumed to be ISO-8859-1, regardless of the actual encoding of the en_US locale on the system. cf https://hg.python.org/cpython/file/7841e9b614eb/Lib/locale.py#l1049, getdefaultlocale(), etc. This code appears to date back to python 2.0. The source of this hard-coding is Xorg's locale.alias but is ultimately justified by glibc's SUPPORTED. This causes problems on OE, because any locale lacking an explicit encoding suffix (e.g. en_US) is UTF-8. It has been this way from the beginning (svn r1). That is not a bug, per se -- no specification prohibits this AFAIK. But it seems to be at odds with virtually every other glibc-based distribution in existence. To avoid needlessly aggravating hidden bugs that nobody else might hit, it makes sense to disable this behavior such that locales are named precisely as specified by SUPPORTED. I suppose that reasonable minds may disagree on whether or not the current behavior is prudent; at the very least, this is likely to break IMAGE_LINGUAS settings. So let's create a new distro variable LOCALE_UTF8_IS_DEFAULT to allow either behavior. Set it to 0 and all your locales get named exactly like they are in SUPPORTED. Leave it at 1 to preserve current OE locale naming conventions. (From OE-Core rev: fcde0c43f7b57ec6f8201226ad98e6e46708d288) 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>
* documentation.conf: Update the help for BBMASKPeter Kjellerstedt2016-01-291-1/+1
| | | | | | | | | | | Since it is now possible to concatenate multiple regular expressions into BBMASK, there is no longer any real reason to limit it to be specified only in local.conf. (From OE-Core rev: 629043e3ec798543a31c3c2f9fa7ca5fa8248228) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image.bbclass: check INITRAMFS_MAXSIZERobert Yang2016-01-261-0/+6
| | | | | | | | | | | | | | | | | | | | | | | Usually, the initramfs' maxsize can be 1/2 of ram size since modern kernel uses tmpfs as initramfs by dafault, and tmpfs allocates 1/2 of ram by default at boot time, which will be used to locate the initramfs. Set INITRAMFS_MAXSIZE to 131072K (128M) by default (ram 256M), the initramfs is small usually, for example, core-image-minimal-initramfs is about 21M (uncompressed, 17M * 1.3) by default, but if the user add a lot pkgs to initramfs, we can error and stop to let the user know ealier rather than fail to boot (e.g., OOM-killer) at boot time. Please see the bug for more info: https://bugzilla.yoctoproject.org/show_bug.cgi?id=5963 [YOCTO #5963] (From OE-Core rev: 155ba626b46bf71acde6c24402fce1682da53b90) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: set default libexecdir to $prefix/libexecRoss Burton2016-01-241-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | The use of $libdir/$BPN as libexecdir is contrary to all other mainstream distributions (which either use $prefix/libexec or $libdir), and the GNU Coding Standards[1] which suggests $prefix/libexec and notes that any package-specific nesting should be done by the package itself. Finally, having libexecdir change between recipes makes it very difficult for different recipes to invoke binaries that have been installed into libexecdir. The File System Hierarchy[2] now recognises the use of $prefix/libexec/, giving distributions the choice of $prefix/lib or $prefix/libexec without breaking FHS. Change bitbake.conf to use $prefix/libexec for libexecdir, so that the binaries are separated from the libraries. This should avoid complications with multilib configurations. [1] https://www.gnu.org/prep/standards/html_node/Directory-Variables.html [2] http://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html [ YOCTO #6398 ] (From OE-Core rev: e7270e331560546d3805cd66ed14afcbc96b6d89) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: update to 4.4Bruce Ashfield2016-01-241-1/+1
| | | | | | | | | | Updating the lib-headers to match the 4.4 LTSI kernel version. (From OE-Core rev: 046b1f4cf439e36c8e8a4904f8e8014a9ea733e2) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Remove horrible variable expansion hacksRichard Purdie2016-01-241-4/+6
| | | | | | | | | | | We used to need these hacks to make things work. Rework the variables to remove the horrible hacks and make things slightly less ugly. This does mean PE and PRAUTO are given default empty values but this is preferred to the other ugliness. (From OE-Core rev: f37af830448794d3941aca9ab4b2bfa9d8358694) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: Upgrade 2.7.9 > 2.7.11Alejandro Hernandez2016-01-201-2/+2
| | | | | | | | | | | | | - no license change, just dates Rebased: - check-if-target-is-64b-not-host.patch - add-CROSSPYTHONPATH-for-PYTHON_FOR_BUILD.patch (From OE-Core rev: 9ed4ef038a4a8140accfa97b2eb6b75f8bed3693) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags.inc: remove obsolete workarounds for curlAndre McCurdy2016-01-191-4/+0
| | | | | | | | | | | | | | | | | | | | | | The curl configure script contains sanity checks for unexpected options being passed via CFLAGS, LDFLAGS, etc. environment variables. These sanity checks catch -Dxxx options in CFLAGS, which clashes with OE's approach of using CFLAGS to pass -D_FORTIFY_SOURCE (curl's configure script suggests, quite correctly, that -Dxxx options should be passed via CPPFLAGS instead). These sanity checks previously generated fatal errors, but have been downgraded to warnings since curl v7.32. Therefore the workaround of avoiding -D_FORTIFY_SOURCE for curl is obsolete and can be removed. https://github.com/bagder/curl/commit/5d3cbde72ece7d83c280492957a26e26ab4e5cca (From OE-Core rev: d0dfd7bf9b2d6fb269f4d9b62263fd7ccc805fde) 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.conf: rename python-native-runtimeEd Bartosh2016-01-181-1/+1
| | | | | | | | | | | | | | The code in native.bbclass adds -native suffix to the package names that don't have it. Renamed python-native-runtime -> hostpython-runtime-native to avoid mangling it and to conform with the naming convetion for native packages. (From OE-Core rev: 8a474057d86b3ebf6271656d6b9adf384ea9ad6d) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcmode-default.inc: Fix preferred provider nativesdk-sdk_prefix-libc-initialMark Hatle2016-01-151-1/+1
| | | | | | | | | | | Similar to the libc-for-gcc preferred provider, we also need a libc-initial version. Layers such as meta-mingw need the ability to override these values in order to generate an SDK that works on non Linux environments. (From OE-Core rev: ea4b19ad2e4d259c41c9e09ecb70bc8043509a4f) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb: upgrade to 7.10.1Richard Purdie2016-01-151-1/+1
| | | | | | | | | The PPC inferior patch was dropped since an equivalent fix was merged upstream. (From OE-Core rev: 564c56207edd9a7dcef3ea966580e11a1548115c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: rename perl-native-runtimeEd Bartosh2016-01-111-1/+1
| | | | | | | | | | | | | | | | The code in native.bbclass adds -native suffix to the package names that don't have it. perl-native-runtime becomes perl-native-runtime-native because of this. Renamed perl-native-runtime -> hostperl-runtime-native to avoid mangling it and to conform with the naming convetion for native packages. (From OE-Core rev: f4dade8e765a8c7bfd131728b9e0a34631e24950) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: remove 'stamp-base'Chen Qi2016-01-111-1/+1
| | | | | | | | | | | | Remove 'stamp-base' from this file as this flag is no longer used. [YOCTO #8468] (From OE-Core rev: be6070e54f8fe3b530dce66623287403a50ac8a1) 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>
* bitbake.conf: add virtual/libiconv-native to ASSUME_PROVIDEDRoss Burton2016-01-111-0/+1
| | | | | | | | | | | It's possible for a native recipe to have virtual/libiconv-native as a build dependency, but as we expect that the host provides that add it to ASSUME_PROVIDED. (From OE-Core rev: a5e6f5939c0ee4280eabd7cfc01131052040bc81) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* x11vnc: remove all references to moved packageIoan-Adrian Ratiu2016-01-071-1/+0
| | | | | | | | | | | | Together with the move to meta-oe, all references to x11vnc should be removed from oe-core. There are three of these: a distro alias, a packagegroup rdepends and a runtime test. (From OE-Core rev: cfd1e4bcd66a9a542007115647cadb8480330fab) 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>
* tune-*: use mcpu instead of mtune for ARM tunesMartin Jansa2016-01-0717-17/+17
| | | | | | | | | | | | | | | | | | | | * since: commit cffda9a821a3b83a8529d643c567859e091c6846 Author: Martin Jansa <Martin.Jansa@gmail.com> Date: Tue Sep 11 17:05:45 2012 +0000 arch-arm: define different ARMPKGARCH when different CCARGS are used we don't need to worry about e.g. cortexa7 device upgrading binary package from armv7a feed which would be built with -mcpu=cortexa15, so we can use -mcpu instead of -mtune, because we won't share the binary feed with MACHINEs built with different tune. (From OE-Core rev: f7bb2d4cf18ca8d2a90b4b3b5c6c48dad106ca28) 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>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-21 16:45:32 +0000