linux/poky.git/meta/classes/libc-package.bbclass, branch python3

meta: python3 megapatch

2016-05-16T22:32:39+00:00

This needs splutting into smaller units, WIP atm. (From OE-Core rev: 21529228a7dca96a6a1b44ed9380c523efdeeb3e) Signed-off-by: Richard Purdie

libc-package.bbclass: add LOCALE_UTF8_IS_DEFAULT

2016-01-30T11:36:57+00:00

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 Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

libc-package: Fix localedef multilib dependency issues

2015-10-20T09:12:01+00:00

Building nativesdk-glibc-locale results in many messages like: QA Issue: nativesdk-locale-base-en-sg rdepends on localedef, but it isn't a build dependency? [build-deps] It should depend on ${MLPREFIX}localedef, not just localedef to fix these warnings. (From OE-Core rev: 80e2dfbfef2d40c3ab074142deac73317f89e3a2) Signed-off-by: Richard Purdie

libc-package: don't abuse B to change directory

2015-07-16T14:09:21+00:00

Currently if exec_func() isn't told what directories to create and change to, it uses B. This is not obvious and may be changed in the future. Instead, pass -C to oe_runmake. (From OE-Core rev: c4a1989f3550e81f188b5789af2c4c18560c3656) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

meta: Add explict getVar param for (non) expansion

2015-06-23T10:57:25+00:00

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

libc-package.bbclass: add aarch64 target to locale_arch_options

2014-12-23T10:18:17+00:00

Add aarch64 target to locale_arch_options in libc-package.bbclass to support Arm V8. (From OE-Core rev: 0d7a92f887bcbe44083a8c0f3f66d195d8bd023e) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie

qemu/libc-package: Fix qemu option handling

2014-12-05T18:01:08+00:00

The 'overrides' here are PACKAGE_ARCH based and hence not overrides as such and the _append wasn't working in many cases. This adjusts the code to use PACKAGE_ARCH as the accessor and ensures the variables work as expected. This fixes various segfaults and ensures postinsts run at build time rather than on the target system. The bug was introduced in http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=7efad8a1b56df6ee07c12ad360c0493d7b1d6d23. (From OE-Core rev: 219e793907406eabf632e784e3a11ab9acb77cfb) Signed-off-by: Richard Purdie Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

Globally replace oe.utils.contains to bb.utils.contains

2014-04-25T16:19:19+00:00

BitBake has the exact same code as oe.utils.contains so there's no reason to duplicate it. We now rely on the bb.utils.contains code for metadata. (From OE-Core rev: 93499ebc46547f5bf6dcecd5a786ead9f726de28) Signed-off-by: Otavio Salvador Signed-off-by: Richard Purdie

classes/recipes: More optimal DISTRO_FEATURES references

2013-12-05T14:24:43+00:00

Using the contains function results in more optimal sstate checksums resulting in better cache reuse as we as more consistent code. (From OE-Core rev: 9c93526756e7cbbff027c88eb972f877bcb1f057) Signed-off-by: Richard Purdie

classes: add aarch64_be target

2013-10-14T15:55:32+00:00

Add big endian ARMv8 target to OE infrastructure (From OE-Core rev: 570ae1afecc88b12a11e62a4341069c125d18403) Signed-off-by: Victor Kamensky Signed-off-by: Koen Kooi Signed-off-by: Richard Purdie