summaryrefslogtreecommitdiffstats
path: root/meta/conf/bitbake.conf
Commit message (Collapse)AuthorAgeFilesLines
* bitbake.conf: set READELF for cross compilationJeremy Puhlman2016-09-231-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | In the case of using an external toolchain that supports multilib compilation with a single binary, TARGET_PREFIX is the same for both main and multilib abis. Without READELF exported, python3 assumes it is either the readelf for ${BUILD_SYS}-readelf. Exporting cross readelf fixes the build issue. checking LDLIBRARY... libpython$(LDVERSION).so checking for i586-montavistamllib32-linux-ranlib... x86_64-montavista-linux-ranlib checking for i586-montavistamllib32-linux-ar... x86_64-montavista-linux-ar checking for i586-montavistamllib32-linux-readelf... no checking for readelf... readelf configure: WARNING: using cross tools not prefixed with host triplet (From OE-Core rev: 3442ee423813d547be7899a25ea31efe719e662f) (From OE-Core rev: e24b5fe3f04cbb5953ec82f9e4d040f6600012b3) Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.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>
* bitbake.conf/toolchain-scripts.bbclass: Remove debug prefix mappings in SDKJacob Kroon2016-09-231-4/+4
| | | | | | | | | | | | | | | | CFLAGS/CXXFLAGS in the SDK environment script adds debug-prefix mappings that include staging area/work directories. Remove them since the SDK shouldn't be aware of them. (From OE-Core rev: 7918e73e9c5fe8c8c1c1d341eaa42f2f7d3ddb69) (From OE-Core rev: e52b98077e94e7071e70de28ed95092aad74d3ac) Signed-off-by: Jacob Kroon <jacob.kroon@gmail.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>
* bitbake.conf: don't set CCACHE_DIR to $HOME by defaultRoss Burton2016-06-291-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the user hasn't inherited ccache.bbclass then CCACHE_DIR is set to $HOME. This was to work around a bug (#2554) for some users where if ccache < 3.1.10 (released 2014-10-19) was installed and enabled by default (i.e. /usr/bin/gcc is a symlink to ccache) and ccache.bbclass wasn't being inherited then autogen would fail to build because it sets $HOME to /dev/null during the build and ccache (prior to 3.1.10) would always create CCACHE_DIR even if it was disabled. As the default is $HOME/.ccache, this results in ccache attempting to create /dev/null/.ccache. However there was a mistake in this assignment of CCACHE_DIR - it should be $HOME/.ccache - as ccache will do cleanup inside CCACHE_DIR which will result in it deleting $HOME/tmp. In the future when we can assume that everyone has ccache 3.1.10 onwards this assignment can be deleted, but as of now we still support OpenSUSE 13.2 which ships with 3.1.9 so fix the assignment to be $HOME/.ccache. [ YOCTO #9798 ] (From OE-Core rev: 15eaf9cb1fa19036fe4442905876dae94070b04d) (From OE-Core rev: 8bcfed5a5d8c53a481028ef6e55008670cfbe8dc) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add default for IMAGE_FSTYPES_DEBUGFSRoss Burton2016-06-291-0/+1
| | | | | | | | | | | | | | If debug filesystem generation is enabled but this isn't assigned then the generation code throws exceptions. (From OE-Core rev: 0a1b02fab0e2604cd55ea6f45d764a864599213a) (From OE-Core rev: c622eaff01383b2f18d243d10b2d2dd4393ef6f1) 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>
* bitbake.conf: change APACHE_MIRROR to point at archive.apache.orgRoss Burton2016-06-291-1/+1
| | | | | | | | | | | | | | | | | | The official download servers www.[country].apace.org only host the latest release, so the URL is only valid when the recipe is fully up to date. In the general case this isn't a problem as our mirror list includes archive.apache.org, but the upstream URI checking (the checkuri task) fails as that explicitly doesn't use the mirrors. (From OE-Core rev: ddd003805782e1fcfc3d59d9b0a1277cf3d1fae9) (From OE-Core rev: bc657f9c310a247047d52253f7b62061be5d8404) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add BB_WORKERCONTEXT to HASHBASE_WHITELISTRichard Purdie2016-04-031-1/+2
| | | | | | | | | | | | We never want checksum to vary depending on whether we calculate them in server or worker context, that would make no sense. This was happening in do_rootfs tasks since they reference the BB_WORKERCONTEXT variable. Whitelist the variable to avoid this class of problem. (From OE-Core rev: 664afc12d1aad97c85db6688790c48abfc528c53) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/bitbake.conf package.bbclass: fix dbg package not contain sources while ↵Hongxu Jia2016-03-281-2/+1
| | | | | | | | | | | | | | | | | | | | | | -fdebug-prefix-map used Tweak DEBUG_FLAGS to use "/usr/src/debug/${PN}/${EXTENDPE}${PV}-${PR}" as source target path in DWARF. While use gdb to debug binary, it could work with sources in dbg package. While -fdebug-prefix-map is used for compiling, we do not need invoking debugedit to edit DWARF at do_package time, but list where sources files are. The copydebugsources uses the list to copy sources to dbg package. It works whether -fdebug-prefix-map used or not. [YOCTO #9305] (From OE-Core rev: ecb56a6ae0c870af680da03db9d39703b525fc98) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: rename 'gobject-introspection-data' machine feature to ↵Alexander Kanavin2016-03-281-1/+1
| | | | | | | | | | | | | 'qemu-usermode' The new value is more general and better reflects what having the feature really means. Introspection data, then, is built only if 'gobject-introspection-data' is in DISTRO_FEATURES and 'qemu-usermode' is in MACHINE_FEATURES. (From OE-Core rev: 9927a3d72e2272d8e3dc4785ba02e27802ee1c6c) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: whitelist proxy variables in config hashPaul Eggleton2016-03-251-1/+3
| | | | | | | | | | | | | | | We don't need these variables incorporated in the config hash (i.e. we don't need to reparse if they change). This fixes an issue with the extensible SDK where the cache generated at installation time not to be used afterwards due to the way we're allowing through the proxy variables into the install environment (such that they get set to "" if not set externally). (From OE-Core rev: 3dc7c58b7b3224f3ed2d59d95313e70e4c57d7c4) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add 'gobject-introspection-data' to ↵Alexander Kanavin2016-03-121-2/+2
| | | | | | | | | | | | | | | | | | DISTRO/MACHINE_FEATURES_BACKFILL This means that introspection data will be generated using qemu by default. If this causes trouble (qemu does not always emulate target architectures perfectly), then add MACHINE_FEATURES_BACKFILL_CONSIDERED = "gobject-introspection-data" to machine configuration or DISTRO_FEATURES_BACKFILL_CONSIDERED = "gobject-introspection-data" to distro configuration. (From OE-Core rev: 7eb19aa29f40c10b0ed9e9c384652dbc9d185088) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add libgcc-native to ASSUME_PROVIDEDRichard Purdie2016-03-071-0/+1
| | | | | | | | | Changes to the btrfs-tools recipe means we need to add libgcc-native to ASSUME_PROVIDED. (From OE-Core rev: 448726469761b8cdc4b4acedb664cede994dde12) 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* bitbake.conf: Add filename and lineno to BB_SIGNATURE_EXCLUDE_FLAGSRichard Purdie2015-12-221-1/+1
| | | | | | | | | | | | | | | This is mainly a performance optimisation. Since we added these flags to functions, the system spends a lot of time trying to expand these flags. The values don't really influence checksums and don't need to be included since if the function content changes, that is will be detected regardless and is the key detail we care about. Therefore exclude these from the checksums and gain a signficiant chunk of parsing speed back. (From OE-Core rev: 2a1edfd9cfa16ec334c0758b47677d4fee5e79a8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: Drop now pointless manual -dbg packagingRichard Purdie2015-12-161-7/+1
| | | | | | | | | With the autodebug package generation logic, specifically setting FILES_${PN}-dbg isn't needed in most cases, we can remove them. (From OE-Core rev: 3ab59d49dd7c18e194b58d1248b4b87709b5a738) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mirrors: replace references to archive.apache.orgAlexander Kanavin2015-12-121-1/+1
| | | | | | | | | | | | archive.apache.org does not contain current releases, only historical ones, so upstream checks aren't accurate. It's replaced with official mirrors containing current versions. (From OE-Core rev: e9c85489ae354f52ff5b78f4d7fb6fafd0050522) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: add file-native to ASSUME_PROVIDEDRoss Burton2015-10-271-0/+1
| | | | | | | | | | | | Various key parts of the core classes (for example, do_package and do_populate_sysroot) currently require file. As it's not possible to build a file-native without invoking do_populate_sysroot mark file-native as ASSUME_PROVIDED and expect to use the host's binary. (From OE-Core rev: d92a29bf279d3e96aa6cebf88a8fd94b52fc59eb) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Exclude sstate-outputdirs flag from checksumsRichard Purdie2015-10-011-1/+1
| | | | | | | | | | | | | | | | This was making deploy tasks MACHINE specific since they place output into DEPLOY_DIR_IMAGE which contains MACHINE. On the plus side, this was accidentally ensuring the output was placed for each machine, on the downside it was triggering a rebuild every time for the different checksum. There is a better way to handle this which avoids the rebuild, see the following tweak to do_deploy to mark it as MACHINE specific in a different way. (From OE-Core rev: 59800189690f887e6f3e8c3139fa6a404b76ac71) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: update APACHE_MIRRORRobert Yang2015-09-231-1/+1
| | | | | | | | | | | | From Ross: The http://www.apache.org/dist only keeps latest release, so use http://archive.apache.org/dist, which keeps all the archives. (From OE-Core rev: effc519e5cdc43d6c9411d13ab236c67c74f0ef5) 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.conf: add MIRROR vars to SRC_URI vardepsChristopher Larson2015-09-031-0/+17
| | | | | | | | | Changes to what mirror we happen to fetch from shouldn't cause rebuilds. (From OE-Core rev: 168f3d71bcfc9daa2984c21f35e2a2fdf754c57c) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: set PATCHRESOLVE to noop by defaultChristopher Larson2015-08-301-2/+2
| | | | | | | | | | | | | | | Automatically spawning a devshell, rather than doing so on demand, is questionable default behavior, and is potentially problematic in headless builds. Further, there are problems with the patch resolver today. Default to noop, and the user can always opt-in to use of the patch resolver by setting PATCHRESOLVE to user. (From OE-Core rev: 7964936dd1fb202373e58048c19a91d4b27cdfd6) (From OE-Core rev: 4d8b993851d28909333d04166df592c8adc451aa) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: set USE_NLS based on DISTRO_FEATURESChristopher Larson2015-08-301-1/+1
| | | | | | | | | | | If our libc doesn't support locales, we don't need gettext nls bits enabled. (From OE-Core rev: f1bc8afa6ee584a81fb65bcf77e5ae1a8889f47c) (From OE-Core rev: 8144069cd295fae67a7007a984e285c1a2a320e5) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: unexport SHELLChristopher Larson2015-08-301-0/+5
| | | | | | | | | | | | | The user's shell shouldn't be allowed to affect the build (and it can break the flock command and possibly more, if the user's shell isn't POSIX compliant). (From OE-Core rev: fc5e1cfcc3ab7acfb6e7e12cb2cf7fa4699ae7b3) (From OE-Core rev: 43a2baf26dad4b7b2f0e4c6af3ea4a611cee7ad5) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Define fallback DISTRO_NAMEKhem Raj2015-08-301-10/+10
| | | | | | | | | | | | | | | | | | | | | When using OE-Core only we miss this define and its now used in recipes like os-release, which goes undefined and when booting we see messages like Welcome to ${DISTRO_NAME} nodistro.0! This would change to Welcome to OpenEmbedded nodistro.0! Remove all trailing whitespaces while touching this file (From OE-Core rev: cf2383a63975ac7a51729a313fe0a52b559d2c61) (From OE-Core rev: 394f0d61d1211a0562a3b4d9d78e8984abd3b28f) 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>
* bitbake.conf: Add nonarch_libdir and base systemd vars on itPau Espin Pedrol2015-08-101-1/+4
| | | | | | | (From OE-Core rev: ab26953276c543582fbaf2ad6f0a02d712ed90ea) Signed-off-by: Pau Espin Pedrol <pau.espin@aweurope.be> 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* 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>
* Revert "bitbake.conf: don't remove WARN_QA and ERROR_QA from hashes"Ross Burton2015-02-081-1/+1
| | | | | | | | | | | | | | | It turns out that changing WARN_QA and ERROR_QA results in do_configure's QA postfunc re-executing, so changing a QA test results in a complete rebuild. This is just too much and the lesser evil of needing to do a full rebuild to verify changed QA flags is preferable to an enforced full rebuild. This reverts commit daecfc3438122b5d146a59a5053e57006d55ccc4. (From OE-Core rev: 4c5895da16de6f00148a0755b421f07223083d09) 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-09 09:32:22 +0000