summaryrefslogtreecommitdiffstats
path: root/meta/conf/bitbake.conf
Commit message (Collapse)AuthorAgeFilesLines
* bitbake.conf: Add comm to HOSTTOOLSNiko Mauno2018-03-301-1/+1
| | | | | | | | | | | | | | | | | This mitigates following issues during u-boot do_compile() step -- otherwise, if comm is not available, they are quietly ignored: .../scripts/check-config.sh: line 33: comm: command not found .../scripts/check-config.sh: line 39: comm: command not found Since 'comm' is provided by coreutils package, adding it to HOSTTOOLS was considered a lower impact fix compared to adding coreutils-native buildtime dependency to u-boot recipe. (From OE-Core rev: 8c370ab4352581c19c45d476a97c2c3b45a56fdb) Signed-off-by: Niko Mauno <niko.mauno@vaisala.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add tools required by testimage to HOSTTOOLS conditionallyChen Qi2018-03-041-1/+1
| | | | | | | | | | | | | | | | | Add tools required by testimage to HOSTTOOLS only when testimage is inherited. These tools, as described in the comment, are only required by the testimage task. So this change should not have negtive effect. This would also solve build error on hosts which miss some tool such as scp. Cherry-picked from rocko 8ca61a5464743ff85b6d26886112750d6ddd13e0 (From OE-Core rev: 189d8282e82381d65c8cc9efe1896f628e9632bd) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add ssh to HOSTTOOLS_NONFATALChen Qi2018-03-041-1/+1
| | | | | | | | | | | | | | | We changed to make tools required by testimage to be included conditionally. This resulted in users who use ssh for git fetching having failures. Add ssh to HOSTTOOLS_NONFATAL to make things work for the above situation. [YOCTO #12227] (From OE-Core rev: 9be68b7fd09f9925c22797b0c99a3db7d460c223) 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 bzr to HOSTTOOLS_NONFATALMartin Jansa2017-09-131-0/+3
| | | | | | | | | | | | | | | | | | * it's used by bzr fetcher: meta/conf/bitbake.conf:FETCHCMD_bzr = "/usr/bin/env bzr" and when it isn't available in PATH do_fetch tasks fail with: /usr/bin/env: ‘bzr’: No such file or directory * it was also added in: https://patchwork.openembedded.org/patch/140107/ but this change wasn't merged (nor rejected AFAIS) * cherry-picked from master c7ba7e9e7a7ca2caf453106112dc5a3c855b21d3 (From OE-Core rev: 92f73702d95e9c6ae72de667f225c9d24afe5c0a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "bitbake.conf: Add sdl-config to HOSTTOOLS if using host SDL"Richard Purdie2017-06-271-3/+0
| | | | | | | | This clearly wasn't tested as the correct variable is ASSUME_PROVIDED. This reverts commit 91cee064332969207334cd1ee5c31d02610281fc. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add sdl-config to HOSTTOOLS if using host SDLJonathan Liu2017-06-141-0/+3
| | | | | | | | | | | If ASSUME_PROVIDES contains libsdl-native, we need to add sdl-config to HOSTTOOLS to allow access to the host sdl-config. (From OE-Core rev: ed5a602d3eb418beb2f9731fda96415ed16efff2) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* DEBIAN_MIRROR: switch from ftp to httpMaxin B. John2017-05-111-2/+2
| | | | | | | | | | | | | | All public-facing debian.org FTP services will be shut down on November 1, 2017 The mirrors should just be accessed using HTTP instead. https://www.debian.org/News/2017/20170425 Fixes [YOCTO #11413] (From OE-Core rev: c2cdc4d9155d7a3b9cba60fa9cbb448cf64c62bd) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add COMPONENTS_DIR for ${STAGING_DIR}-componentsPeter Kjellerstedt2017-05-111-1/+2
| | | | | | | | | | The path to where to install and find the sysroot components is used in many places. This warrants it to get its own variable. (From OE-Core rev: 70a84b525470f72339568409daf84845904e4cab) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add HOSTTOOLS_DIR for ${TMPDIR}/hosttoolsPeter Kjellerstedt2017-05-011-0/+3
| | | | | | | | | | | The path to where to install and find the tools copied from the host environment is already used in a couple of places. This warrants it to get its own variable. (From OE-Core rev: 8164c466943ffedff399009bf5547dba4f06d6c8) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add python2 to HOSTTOOLSDiego Rondini2017-04-291-1/+1
| | | | | | | | | | | Add python2 to HOSTTOOLS as, according to https://www.python.org/dev/peps/pep-0394/, the command "python2" should be the one used in scripts that are not yet ported to Python 3. (From OE-Core rev: b85e41eeef3fddc2c15439cf78b8cc8542b5bc22) Signed-off-by: Diego Rondini <diego.rondini@kynetics.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add pr to list of hosttoolsKhem Raj2017-04-291-1/+1
| | | | | | | | | | pr is used by gstreamer1.0-libav during configure (From OE-Core rev: cb6c02bd8c65ea033a939011cbba21ad0442acf0) 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 sha256sum to HOSTTOOLSRichard Leitner2017-04-201-3/+3
| | | | | | | | | | | | | icedtea-native from meta-java needs sha256sum for checksum validation. Therefore add sha256sum to HOSTTOOLS (as md5sum is already in there). Without it the icedtea-native build will fail during configuration at current master. (From OE-Core rev: d0d3abdf9e2dec57f3849813faa5e7e3d34b83a4) Signed-off-by: Richard Leitner <richard.leitner@skidata.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* native/nativesdk: Use fixed DISTRO_FEATURESJussi Kukkonen2017-04-121-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There seems to be little advantage to letting distro features affect native builds. There is a significant disadvantage: a change to DISTRO_FEATURES will trigger a lot of unnecessary native tasks. In a test like this: $ bitbake core-image-minimal # append " systemd" to DISTRO_FEATURES $ bitbake core-image-minimal The latter build takes 44 minutes (28%) of cpu-time less with this patch (skipping 135 native tasks). Sadly wall clock time was not affected as glibc remains the bottleneck. Set native distro features to DISTRO_FEATURES_NATIVE appended with an intersection of DISTRO_FEATURES and DISTRO_FEATURES_FILTER_NATIVE. Current default values (baitbake.conf) are * DISTRO_FEATURES_FILTER_NATIVE ?= "api-documentation" (as gtk-doc-native has much less dependencies when built without it) * DISTRO_FEATURES_NATIVE ?= "x11" (to enable native UIs even if target does not containe them) Do the variable setting in native_virtclass_handler() because otherwise it could still be overridden by appends and the feature backfilling. Shuffle the early returns so DISTRO_FEATURES gets set as long as the packagename ends with "-native". Add similar variables for nativesdk. To make nativesdk work we need to enable the locale options so nativesdk-glibc-locales can build and to avoid the init manager check in the nativesdk case so add those fixes. (From OE-Core rev: 731744d5538e315702be828e6f2bd556309dee07) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Drop MULTIMACH_HOST_SYSRichard Purdie2017-03-311-1/+0
| | | | | | | | | There are no users of this left after recipe specfic sysroots was implemented, drop the variable as it no longer makes sense or is useful. (From OE-Core rev: a2fbf85f68b685c32049fb48aed0248369911c49) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add DEPLOY_DIR to BB_HASHBASE_WHITELISTRichard Purdie2017-03-311-1/+1
| | | | | | | | | | | Users should be able to locally choose DEPLOY_DIR without impacting the reuse of sstate, this change allows that. [YOCTO #11110] (From OE-Core rev: 460f6ca573667dfcbd66f5efcaebf686f1442b36) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add aws to HOSTTOOLS_NONFATALElizabeth 'pidge' Flanagan2017-03-301-1/+1
| | | | | | | | | | This adds aws to HOSTTOOLS_NONFATAL in order to get the s3 fetcher working again. (From OE-Core rev: 6d6d0737a29bbf3dcd231bfefe13784ed16dd55a) Signed-off-by: Elizabeth 'pidge' Flanagan <pidge@toganlabs.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: sort HOSTTOOLS and remove duplicatesAndre McCurdy2017-03-281-10/+10
| | | | | | | | | Cleanup only, no functional changes. (From OE-Core rev: 23dd96a3a175cecde258dc6d8263fbe7b308b58e) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: remove vi from HOSTTOOLS listbrian avery2017-03-221-1/+1
| | | | | | | | | | | | Having changes the sdk test to cpio from cvs, we no longer require an editor to be present. This patch removes vi from the list of required tools. (From OE-Core rev: cca2ccb6d77a433e9d7c535344c4fc1e04589bc0) Signed-off-by: brian avery <brian.avery@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add sudo to HOSTTOOLS_NONFATALEd Bartosh2017-03-221-1/+1
| | | | | | | | | | | | | runqemu is using sudo to configure tap networking. Without sudo in HOSTTOOLS_NONFATAL it may cause bitbake -c testimage to fail with this error: runqemu - INFO - Setting up tap interface under sudo /bin/sh: sudo: command not found (From OE-Core rev: 716e0524cfbcac2eb272be1014280833b74bc5c4) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add few more binaries to HOSTTOOLS_NONFATALMartin Jansa2017-03-171-0/+3
| | | | | | | | | | | | | | | | | * add: join nl size yes zcat join - netcf - http://errors.yoctoproject.org/Errors/Details/135208/ join - fontforge - http://errors.yoctoproject.org/Errors/Details/135209/ nl - dash - http://errors.yoctoproject.org/Errors/Details/135215/ nl - klibc - http://errors.yoctoproject.org/Errors/Details/135198/ size - iptraf - http://errors.yoctoproject.org/Errors/Details/135204/ yes - libnet-ssleay-perl - http://errors.yoctoproject.org/Errors/Details/135197/ zcat - scsirastools - http://errors.yoctoproject.org/Errors/Details/135205/ (From OE-Core rev: 83dfb69b37c2465d09eb9544d487f1674b06f9c0) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Drop pip3 from HOSTTOOLS_NONFATALRichard Purdie2017-03-161-1/+1
| | | | | | | | | Now that pip3-native is used by build-appliance, we should no longer need this host tool. (From OE-Core rev: 096f943d4b7a7cf5d4c3d45f34be5ddcd2475790) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: whitelist socat as non-fatal host toolMikko Ylinen2017-03-161-1/+1
| | | | | | | | | | | | | oe-git-proxy depends on socat host tool but it's not whitelisted and triggers a 'binary not in PATH' error. Whitelist socat but make it a HOSTTOOLS_NONFATAL since it's not a hard dependency. (From OE-Core rev: 97f979ee61a06349139ccc47feaf051bdbcf0e16) Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add nc to HOSTTOOLS_NONFATALRichard Purdie2017-03-141-1/+1
| | | | | | | | | This is used by some of our proxy scripts but isn't required for all builds so add to HOSTTOOLS_NONFATAL. (From OE-Core rev: 4837b8cc3248c07f77a91745b80e6129ec3dfa1f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base/bitbake.conf: Filter contents of PATH to only allow whitelisted toolsRichard Purdie2017-03-111-0/+18
| | | | | | | | | | | | | | | | | | | | | | We currently have a determinism problem in that the host tools present in PATH can influence the build. In particular, the presence of pkg-config on the build host can mask missing pkgconfig class dependencies. This adds in a new HOSTTOOLS variable and then uses it to set up a directory of symlinks to the whitelisted host tools. This directory is placed as PATH instead of the usual /usr/bin:/bin and so on. This should improve determinism of builds and avoid the issues which have been particularly obvious since the introduction of recipe specific sysroots. If users find there is a tool missing, they can extend HOSTTOOLS from a global class or global conf file. Right now the settings should be enough to build everything in OE-Core. (From OE-Core rev: fa764a403da34bb0ca9fa3767a9e9dba8d685965) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: replace USE_LDCONFIG with new "ldconfig" distro featureAndre McCurdy2017-03-041-1/+1
| | | | | | | | | | | | | | | | | | | | | USE_LDCONFIG could previously be set to 0 by distros which do not require ldconfig or ld.so.conf on the target. Since more and more recipes may need to respect that option, replace the ad-hoc variable with a distro feature. Distros which previously set: USE_LDCONFIG = "0" Should now instead use: DISTRO_FEATURES_BACKFILL_CONSIDERED_append = " ldconfig" (From OE-Core rev: a905df2dd8f43a2febffa64a39b6e508510326a0) 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: fix ineffective include conf/target/${TARGET_SYS}.confAndre McCurdy2017-03-011-1/+1
| | | | | | | | | | | | | | | TARGET_SYS is defined in terms of TARGET_ARCH, so it's not valid until after TUNE_ARCH has been set by the machine config. The original order of includes resulted in an attempt to include non-existent files such as: conf/target/INVALID-oe-linux.conf (From OE-Core rev: b33e644da0d8b6edb97257b16430b545c289883a) 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: Point KERNELORG_MIRROR to cdn.kernel.orgDominic Sacré2017-02-231-1/+1
| | | | | | | | | | | | | | | Use cdn.kernel.org to distribute the server load and improve download speeds. Leave www.kernel.org in MIRRORS as a fallback. See https://www.kernel.org/introducing-fastly-cdn.html (From OE-Core rev: 7c81b680a3cc4602c9c153398103d5477d7fd894) (From OE-Core rev: 4f09ec0e7b51cc599d6a46d41f77d6fb07a6d445) Signed-off-by: Dominic Sacré <dominic.sacre@gmx.de> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Exclude extend_recipe_sysroot function from sstate checksumsRichard Purdie2017-01-231-1/+1
| | | | | | | | | | | | The extend_recipe_sysroot itself is excluded from the task hashes. This is because it only ever acts upon the contents of the task dependencies and hence those checksums accurately relfect what its doing. It does mean sysroots don't repopulate if this function changes but there are other easy ways to achieve that if needed. (From OE-Core rev: cec305150801d43d58e3758e020e714d2e90e10b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Switch to Recipe Specific SysrootsRichard Purdie2017-01-231-10/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch is comparatively large and invasive. It does only do one thing, switching the system to build using recipe specific sysroots and where changes could be isolated from it, that has been done. With the current single sysroot approach, its possible for software to find things which aren't in their dependencies. This leads to a determinism problem and is a growing issue in several of the market segments where OE makes sense. The way to solve this problem for OE is to have seperate sysroots for each recipe and these will only contain the dependencies for that recipe. Its worth noting that this is not task specific sysroots and that OE's dependencies do vary enormously by task. This did result in some implementation challenges. There is nothing stopping the implementation of task specific sysroots at some later point based on this work but that as deemed a bridge too far right now. Implementation details: * Rather than installing the sysroot artefacts into a combined sysroots, they are now placed in TMPDIR/sysroot-components/PACKAGE_ARCH/PN. * WORKDIR/recipe-sysroot and WORKDIR/recipe-sysroot-native are built by hardlinking in files from the sysroot-component trees. These new directories are known as RECIPE_SYSROOT and RECIPE_SYSROOT_NATIVE. * This construction is primarily done by a new do_prepare_recipe_sysroot task which runs before do_configure and consists of a call to the extend_recipe_sysroot function. * Other tasks need things in the sysroot before/after this, e.g. do_patch needs quilt-native and do_package_write_deb needs dpkg-native. The code therefore inspects the dependencies for each task and adds extend_recipe_sysroot as a prefunc if it has populate_sysroot dependencies. * We have to do a search/replace 'fixme' operation on the files installed into the sysroot to change hardcoded paths into the correct ones. We create a fixmepath file in the component directory which lists the files which need this operation. * Some files have "postinstall" commands which need to run against them, e.g. gdk-pixbuf each time a new loader is added. These are handled by adding files in bindir with the name prefixed by "postinst-" and are run in each sysroot as its created if they're present. This did mean most sstate postinstalls have to be rewritten but there shouldn't be many of them. * Since a recipe can have multiple tasks and these tasks can run against each other at the same time we have to have a lock when we perform write operations against the sysroot. We also have to maintain manifests of what we install against a task checksum of the dependency. If the checksum changes, we remove its files and then add the new ones. * The autotools logic for filtering the view of m4 files is no longer needed (and was the model for the way extend_recipe_sysroot works). * For autotools, we used to build a combined m4 macros directory which had both the native and target m4 files. We can no longer do this so we use the target sysroot as the default and add the native sysroot as an extra backup include path. If we don't do this, we'd have to build target pkg-config before we could built anything using pkg-config for example (ditto gettext). Such dependencies would be painful so we haven't required that. * PKDDATA_DIR was moved out the sysroot and works as before using sstate to build a hybrid copy for each machine. The paths therefore changed, the behaviour did not. * The ccache class had to be reworked to function with rss. * The TCBOOTSTRAP sysroot for compiler bootstrap is no longer needed but the -initial data does have to be filtered out from the main recipe sysroots. Putting "-initial" in a normal recipe name therefore remains a bad idea. * The logic in insane needed tweaks to deal with the new path layout, as did the debug source file extraction code in package.bbclass. * The logic in sstate.bbclass had to be rewritten since it previously only performed search and replace on extracted sstate and we now need this to happen even if the compiled path was "correct". This in theory could cause a mild performance issue but since the sysroot data was the main data that needed this and we'd have to do it there regardless with rss, I've opted just to change the way the class for everything. The built output used to build the sstate output is now retained and installed rather than deleted. * The search and replace logic used in sstate objects also seemed weak/incorrect and didn't hold up against testing. This has been rewritten too. There are some assumptions made about paths, we save the 'proper' search and replace operations to fixmepath.cmd but then ignore this. What is here works but is a little hardcoded and an area for future improvement. * In order to work with eSDK we need a way to build something that looks like the old style sysroot. "bitbake build-sysroots" will construct such a sysroot based on everything in the components directory that matches the current MACHINE. It will allow transition of external tools and can built target or native variants or both. It also supports a clean task. I'd suggest not relying on this for anything other than transitional purposes though. To see XXX in that sysroot, you'd have to have built that in a previous bitbake invocation. * pseudo is run out of its components directory. This is fine as its statically linked. * The hacks for wayland to see allarch dependencies in the multilib case are no longer needed and can be dropped. * wic needed more extensive changes to work with rss and the fixes are in a separate commit series * Various oe-selftest tweaks were needed since tests did assume the location to binaries and the combined sysroot in several cases. * Most missing dependencies this work found have been sent out as separate patches as they were found but a few tweaks are still included here. * A late addition is that extend_recipe_sysroot became multilib aware and able to populate multilib sysroots. I had hoped not to have to add that complexity but the meta-environment recipe forced my hand. That implementation can probably be neater but this is on the list of things to cleanup later at this point. In summary, the impact people will likely see after this change: * Recipes may fail with missing dependencies, particularly native tools like gettext-native, glib-2.0-native and libxml2.0-native. Some hosts have these installed and will mask these errors * Any recipe/class using SSTATEPOSTINSTFUNCS will need that code rewriting into a postinst * There was a separate patch series dealing with roots postinst native dependency issues. Any postinst which expects native tools at rootfs time will need to mark that dependency with PACKAGE_WRITE_DEPS. There could well be other issues. This has been tested repeatedly against our autobuilders and oe-selftest and issues found have been fixed. We believe at least OE-Core is in good shape but that doesn't mean we've found all the issues. Also, the logging is a bit chatty at the moment. It does help if something goes wrong and goes to the task logfiles, not the console so I've intentionally left this like that for now. We can turn it down easily enough in due course. (From OE-Core rev: 809746f56df4b91af014bf6a3f28997d6698ac78) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: require conf/multiconfig/${BB_CURRENT_MC}.confJuro Bystricky2017-01-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Presently there is no check to verify the existence of configuration files as listed in BBMULTICONFIG. For example, BBMULTICONFIG = "foobar" in local.conf does not trigger an error or even a warning when there is no conf/multiconfig/foobar.conf. The missing file is silently ignored. This patch changes the inclusion of all multiconfig configuration files as a non-optional requirement. If the file is missing, we get an error such as: ERROR: ParseError at /data/master-multi/poky/meta/conf/bitbake.conf:704: Could not include required file conf/multiconfig/foobar.conf Although the "default" configuration is not listed in BBMULTICONFIG, this change also requires the file multiconfig/default.conf to exist. The "default" (non-multiconfig) configuration is normally configured via local.conf, so although this file is required, it can/should be empty. This patch creates an empty file default.conf in meta/conf/multiconfig. [YOCTO#10917] (From OE-Core rev: ca46c09d38b766b69f485f1e82fc78f2a5e6a4c8) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/scripts: Various getVar/getVarFlag expansion parameter fixesRichard Purdie2017-01-091-1/+1
| | | | | | | | | | | | | | | | | There were a few straggling expansion parameter removals left for getVar/getVarFlag where the odd whitespace meant they were missed on previous passes. There were also some plain broken ussages such as: d.getVar('ALTERNATIVE_TARGET', old_name, True) path = d.getVar('PATH', d, True) d.getVar('IMAGE_ROOTFS', 'True') which I've corrected (they happend to work by luck). (From OE-Core rev: 688f7a64917a5ce5cbe12f8e5da4d47e265d240f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add inclusion of BB_CURRENT_MC.conf after local.confRichard Purdie2016-12-221-0/+1
| | | | | | | | | | | | | People are strugling with multiconfig as the up front inclusion of the configuration file doesn't do what people expect. The only way to meet user expectations is to include the file immediately after local.conf. We add BB_CURRENT_MC to bitbake so that the metadata can determine when to include the extra configuration. (From OE-Core rev: a6a3894fb2cb2097d2404b8b8cb2b85df595cfa9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: remove True option to getVar callsJoshua Lock2016-12-161-15/+15
| | | | | | | | | | | | | getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?\(( ?[^,()]*), True\) (From OE-Core rev: 7c552996597faaee2fbee185b250c0ee30ea3b5f) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Reduce duplication in MIPS variantsZubair Lutfullah Kakakhel2016-11-151-10/+1
| | | | | | | | | | | Reduce duplication in MIPS variants now that the MACHINEOVERRIDES variable is defined (From OE-Core rev: 4499bca90887a0a7e7943403372654bf9e902b17) Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/nativesdk: set SDK_OLDEST_KERNEL appropriatelyPaul Eggleton2016-11-061-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | SDK_OLDEST_KERNEL currently only controls the check on SDK installation, however as with OLDEST_KERNEL it should be controlling the OLDEST_KERNEL value for building glibc used in the SDK. Thus, set it in nativesdk.bbclass. This means we need to move the default to bitbake.conf so that it can be seen in both places. Also set a more reasonable default for SDK_OLDEST_KERNEL for x86/x86-64 as glibc 2.24 still supports back to 2.6.32 there and there are still people wanting to build SDKs that will install on older distros (e.g. CentOS 6). However it's not possible to set this with overrides since there aren't any for the SDK_ARCH, however we can instead set the variable from conf files in conf/machine-sdk especially as there is now a soft default for SDKMACHINE. Fixes [YOCTO #10561]. (From OE-Core rev: 42d5781e31c5bf76b5b7e27abed4f6f3fd65bf40) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add mipsisa{32, 64}r6{el, } supportZubair Lutfullah Kakakhel2016-10-071-0/+5
| | | | | | | | | Add support for MIPS Release 6 ISA (From OE-Core rev: 582374542b8374fc5d7894387de2ba746afcd036) Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add eudev's udevdir to FILES_${PN}Robert Yang2016-09-241-1/+2
| | | | | | | | | | | | | * The eudev's udevdir can be ${base_libdir}/udev or ${libdir}/udev, it doesn't have to be hardcoded to /lib/udev, so add them FILES_${PN}. * Use /lib/udev rather than /lib/udev/rules.d for FILES_${PN} since there might be files in /lib/udev except subdir rules.d (From OE-Core rev: e1b81a80760fc79612254804e429cab5228b1ab6) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add a lazy default for SDKMACHINERoss Burton2016-09-231-1/+1
| | | | | | | | | | | | | If the user doesn't set SDKMACHINE in their local.conf then uninative and buildtools will fail in obscure ways, so ensure that a default value is set. Also as SDK_ARCH will be overritten then loading the machine-sdk configuration file, don't bother assigning it. (From OE-Core rev: 6bd507ef36578ba7bee6ef8b3f8f6465afca4e20) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add BBSERVER to HASHBASE_WHITELISTEd Bartosh2016-09-141-1/+1
| | | | | | | | | | | | | | | | Using BBSERVER variable in checksum calculations causes unnecessary rebuilds when running memres bitbake. Whitelisted BBSERVER variable to prevent this unwanted behaviour. [YOCTO #10201] (From OE-Core rev: c9d949053cc0de1d8fbf8be2fa7c2cc30383ea51) 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: set READELF for cross compilationJeremy Puhlman2016-08-041-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) 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>
* bitbake.conf/toolchain-scripts.bbclass: Remove debug prefix mappings in SDKJacob Kroon2016-08-041-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) 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>
* bitbake.conf: use ${prefix} to define exec_prefixRoss Burton2016-07-201-1/+1
| | | | | | | | | | This was simply changing prefix will relocate everything which is generally the intention, whilst still allowing the variables to be set independently. (From OE-Core rev: 2676ee77bacde03e75c2ceccfdc4c28a684569e6) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/sstate: add a mode to error if sstate package unavailablePaul Eggleton2016-07-081-1/+2
| | | | | | | | | | | | | | If BB_SETSCENE_ENFORCE is set to "1" and an sstate package fails to download outside of the whitelist specified by BB_SETSCENE_ENFORCE_WHITELIST, then fail immediately so you can tell that the problem was caused by failing to restore the task from sstate. Part of the implementation of [YOCTO #9367]. (From OE-Core rev: 9e711b54487c3141d7264b8cf0d74f9465020190) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: whitelist progress varflagPaul Eggleton2016-07-081-1/+2
| | | | | | | | | | We don't want the value of this varflag in any signatures since it's only there for the purpose of aiding display of task execution. (From OE-Core rev: 1f33659a92b2d4b1514984183384fbdcf72ddb99) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Drop BUILDSDK_LDFLAGS rpath, rpath-linkRichard Purdie2016-07-011-6/+1
| | | | | | | | | | | | | | The SDK used to work differently and didn't include its own libc/loader. In that case, these options were needed to correctly handle the different library locations. With the modern relocatable SDK, we don't need these options any more as the default paths in the dynamic loader are good enough. They just given potential for errors so drop them. (From OE-Core rev: 35f24931072bc60df50abe2fa3955dde5096f272) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: don't set CCACHE_DIR to $HOME by defaultRoss Burton2016-06-231-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) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnupg.org-hosted recipes: Change SRC_URI to https siteJussi Kukkonen2016-05-301-0/+2
| | | | | | | | | | | | | | | | | | | https version seems more reliable and in an informal test fetching all gnupg recipes now takes <20% of the time it used to. Define GNUPG_MIRROR in bitbake.conf so future tweaks to this are easier. Replace some slower mirrors with the official ftp site and another from gnupg.org mirror list. Set UPSTREAM_CHECK_URI in all recipes that need it to "https://gnupg.org/download/index.html" as the directory listings are not up-to-date. (From OE-Core rev: dfc9178e2f2b6873ca497d981e308e00d15280b5) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/toolchain-shar-extract: Use en_US.UTF-8 as localeRichard Purdie2016-05-211-1/+1
| | | | | | | | | | | | | | | | | | Under python 3, if we spawn python processes, we need to have a UTF-8 locale, else python's file access methods will use ascii. You can't change that mode once the interpreter is started so we have to ensure a locale is set. Ideally we'd use C.UTF-8 since OE already forces the C locale but not all distros support that and we need to set something so en_US.UTF-8 seems as standard we we can get. This matches the change in bitbake revision 8902c29638411d312e6fc4a197707e5742652e15 Also set this into the environment used when installing SDKs since python can be run and we need to ensure we use a standardised locale which is available from things like buildtools-tarball. (From OE-Core rev: 833d4c0fe804a1f7524b3d4b75cbcdd65c31ddac) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel: moves KERNEL_SRC_PATH to bitbake.confMing Liu2016-05-191-0/+4
| | | | | | | | | | "/usr/src/kernel" is being hard-coded in multiple recipes so far, move its definition to bitbake.conf. (From OE-Core rev: eb9f900527e02ca08a1de14b4ac773f513bb1ee4) Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Oldest kernel for nios2 is 3.19Marek Vasut2016-05-131-0/+2
| | | | | | | | | | | | | The oldest kernel version for nios2 is 3.19.0, set it so, otherwise qemu-nios2 -r ${OLDEST_KERNEL} fails with "FATAL: kernel too old" message from glibc. (From OE-Core rev: 6ea7e6a04441028acec7dc12a6860a1ae85b15f2) Signed-off-by: Marek Vasut <marex@denx.de> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Khem Raj <raj.khem@gmail.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-15 19:29:50 +0000