summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/meta
Commit message (Collapse)AuthorAgeFilesLines
* signing-keys: Use SYSROOT_DIRS to add dirs to stage in sysrootPeter Kjellerstedt2016-05-131-4/+2
| | | | | | (From OE-Core rev: 4a37960e504d6c0bbd0f4c088bef8f3a99beab6a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Drop unneeded LIC_FILES_CHKSUM valuesPaul Eggleton2016-05-111-1/+0
| | | | | | | | | | With the changes to insane.bbclass we don't need LIC_FILES_CHKSUM to be set for recipes that don't actually pull in any source. (From OE-Core rev: fc14e794c53f94158a5e6d6a8644656875639d0c) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-world-pkgdata: add LIC_FILES_CHKSUMRobert Yang2016-05-061-0/+2
| | | | | | | | | | Fixed: ERROR: meta-world-pkgdata-1.0-r0 do_populate_lic: QA Issue: meta-world-pkgdata: Recipe file does not have license file information (LIC_FILES_CHKSUM) [license-checksum] (From OE-Core rev: 6e0ce5ada01da34ad619b2a918097b543b089437) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: set INHIBIT_DEFAULT_DEPSRobert Yang2016-04-191-0/+3
| | | | | | | | | | The recipe doesn't need any default deps. (From OE-Core rev: 25f904b4f0f5a049ffabc7b3613d5902099d4ae0) 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>
* buildtools-tarball: fix perl being included when building with ipkPaul Eggleton2016-04-182-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to some logic within opkg, a package with the name matching a dependency will always win over a package with that name in RPROVIDES - even if there is an RCONFLICTS (which is silently ignored), higher feed priority and version. The end result is that buildtools gets perl installed instead of the nativesdk-buildtools-perl-dummy package and that perl (with missing dependencies) gets used in preference to the host one, which is precisely what we were trying to avoid. This is almost certainly a bug in opkg, especially as the other package's dependencies aren't properly installed under these circumstances either. However, specifying RREPLACES works around this, and with no apparent side-effects is probably the safest solution for now. At the same time I noticed that in prepending to SDK_PACKAGE_ARCHS we were actually ending up with a low priority for the dummy package feed rather than a high one, so change to append it instead. This has no effect on the packages that get installed at the moment, but should be done in case the package manager behaviour changes to factor in the feed priority in future. Fixes [YOCTO #9469]. (From OE-Core rev: b18134ddaf949b4f001a1613ab876aed6324040a) 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>
* buildtools-tarball.bb: fix unexpected operatorRobert Yang2016-04-181-1/+1
| | | | | | | | | | | | | Fixed: run.create_sdk_files.45747: 131: [: =: unexpected operator The SDKMACHINE is not set by default. (From OE-Core rev: 528388c3cef027d436fc794c73d57a247521c238) 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>
* buildtools-tarball.bb: set TOOLCHAIN_NEED_CONFIGSITE_CACHE to nullRobert Yang2016-04-141-0/+3
| | | | | | | | | | | | buildtools-tarball doesn't need config site, set TOOLCHAIN_NEED_CONFIGSITE_CACHE to null so that no target recipes will be built when bitbake buildtools-tarball. (From OE-Core rev: 1c187fd7f722b01e0284e4d368f6f9366e9c2f0b) 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>
* buildtools-tarball: Add texinfo (for makeinfo)Richard Purdie2016-04-051-0/+1
| | | | | | | | | | | | | | | Initially I was reluctant to do this however makeinfo is a dependency of the buildsystem and only adds around 400kb to the buildtools-tarball so it likely makes sense to add it. This allows people to use the project on older environments. Need to enable nativesdk-texinfo but this seems straightforward. [YOCTO #8990] (From OE-Core rev: 5e290201e13a685818ff03ad9cd6679977e560d1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* signing-keys: create ipk packageIoan-Adrian Ratiu2016-03-111-1/+14
| | | | | | | | | | Store the ascii armored pubkey generated using gpg_sign.export_pubkey() in its own package. (From OE-Core rev: 9dab5725dace0c54f4c5ed892d18e2d41cca71b5) Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: Add glibc-gconv-iso8859-1 for guileRichard Purdie2016-03-071-0/+3
| | | | | | (From OE-Core rev: a8181c2d3a9e51569d77ab2ad9950b27a1113294) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: respect SDKMACHINE when buildingRoss Burton2016-02-281-4/+6
| | | | | | | | | | | | | So that a single machine can build multiple architectures for the uninative-tarball respect SDK_ARCH instead of BUILD_ARCH. This means a x86-64 host can build a i686 uninative-tarball by setting SDKMACHINE=i686. (From OE-Core rev: 11b0e7e1cb29fd1fbe06bdb5606a55b92ecdcc89) 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-281-1/+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>
* signing-keys: Make signing keys the only publisher of keysRandy Witt2016-02-261-18/+43
| | | | | | | | | | | | | Previously the keys were put into the os-release package. The package indexing code was also deploying the keys rather than only using the keys. This change makes signing-keys.bb the only publisher of the keys and also uses standard tasks that already have sstate. (From OE-Core rev: 1e38068ac38dfd067655dfd41464e28439179306) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sign_rpm.bbclass: do not store key details in signer instanceMarkus Lehtonen2016-02-191-10/+6
| | | | | | | | | | | | | Refactor the LocalSigner class. Do not store keyid or passphrase file in the signer object as they are only needed for some of the methods. For example, the newly added verify() method does not need any key parameters and export_pubkey only uses keyid. (From OE-Core rev: e2412294b6b1d3a80ee97a0706613349edc51d33) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-buildtools-perl-dummy.bb: Fix variable expansion in python codeAníbal Limón2016-02-111-2/+2
| | | | | | | | | | | | | Since python expansion of bb data variables is disable in order to provide a standard interface usage for expand variables this variables aren't expanded now so change to call d.expand('${VAR}'). This API expansion change was causing to install perl in nativesdk. (From OE-Core rev: cb7a3f997d7278eb6e31ea79ad933a7ab1717977) Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/lib: new module for handling GPG signingMarkus Lehtonen2016-01-261-14/+12
| | | | | | | | | | | | | | | | | Add a new Python module (oe.gpg_sign) for handling GPG signing operations, i.e. currently package and package feed signing. The purpose is to be able to more easily support various signing backends and to be able to centralise signing functionality into one place (e.g. package signing and sstate signing). Currently, only local signing with gpg is implemented. [YOCTO #8755] (From OE-Core rev: 9b3dc1bd4b8336423a3f8f7db0ab5fa6fa0e7257) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_ext: add option to bring in pkgdata for worldPaul Eggleton2016-01-241-0/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a variable SDK_INCLUDE_PKGDATA which you can set to "1" to include pkgdata for all recipes in the world target. There are a couple of uses for this: 1) If you use "devtool add" to add a recipe that builds something which depends on anything in world, the dependency can then be correctly mapped to the recipe providing it and that recipe can be added to DEPENDS, since we have the pkg-config and shared library dependency data within pkgdata. 2) You'll be able to search for these recipes and any files they package for the target with "devtool search" since that also uses pkgdata This of course assumes you've tailored world through EXCLUDE_FROM_WORLD to only include recipes you'd want built in your distro, but I think that's a reasonable assumption; failing that there is a WORLD_PKGDATA_EXCLUDE variable that you can set to exclude any recipes you don't want. Note that this patch relies on functionality implemented in a recent BitBake patch and will not work without it. Implements [YOCTO #8600]. (From OE-Core rev: 67149ea097d6fab7496b43e85a40853f40bd527e) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-buildtools-perl-dummy: Bump PRRichard Purdie2015-12-181-0/+2
| | | | | | | | | | Recent changes to this recipe caused automated PR increments to break, regressing package feeds. The only way to recover is to bump PR, so do this centrally to fix anyone affected. (From OE-Core rev: dacdb499d31cb2e80cca33cba9d599c8ee983dc4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball.bb: 32bit tools need pseudo 32bit libraryJuro Bystricky2015-12-121-0/+6
| | | | | | | | | | | | | | | | | | "pseudo" does not build 32 bit library by default on 64 bit host, but the 32 bit library is needed when using 32 bit development tools (buildtools-tarball) running on a 64 bit host. Building of the library can be forced if the environment variable NO32LIBS is set to "0". Hence for 32 bit buildtools we export the environment variable NO32LIBS="0" and NO32LIBS is also added into BB_ENV_EXTRAWHITE (if not already there). [YOCTO#8581] (From OE-Core rev: 1c20e66428df10000741c25dddb7a2b1fd55ba42) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-buildtools-perl-dummy: properly set PACKAGE_ARCHPaul Eggleton2015-12-111-2/+0
| | | | | | | | | | | | | | | Turns out I did a silly thing in OE-Core revision 9b1831cf4a2940dca1d23f14dff460ff5a50a520 and forgot to remove the explicit setting of PACKAGE_ARCH outside of the anonymous python function; the original bug was apparently fixed but the functionality of allarch.bbclass was being disabled because it was able to see that PACKAGE_ARCH was not set to "all" - which was what I was trying to ensure. (From OE-Core rev: a25ab5449825315d4f51b31a634fe6cd8f908526) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-buildtools-perl-dummy: fix rebuilding when SDKMACHINE changesPaul Eggleton2015-12-011-2/+9
| | | | | | | | | | | | | | | | | | | This recipe produces an empty dummy package (in order to satisfy dependencies on perl so we don't have perl within buildtools-tarball). Because we were inheriting nativesdk here the recipe was being rebuilt, but having forced PACKAGE_ARCH to a particular value the packages for each architecture were stepping on eachother. Since the packages are empty they can in fact be allarch (even though they won't actually go into the "all" package feed). It turns out that nheriting nativesdk wasn't actually necessary either, so drop that. Fixes [YOCTO #8509]. (From OE-Core rev: 9b1831cf4a2940dca1d23f14dff460ff5a50a520) 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>
* Add 850 codepage to uninative-tarballRandy Witt2015-10-271-0/+1
| | | | | | | (From OE-Core rev: 6211c8060d408134dfa6c00b23b517c439e4c1e7) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package signing: automatically export public keysMarkus Lehtonen2015-10-271-0/+45
| | | | | | | | | | | | Automatically export public key(s) of the signing key(s) from the gpg keyring. Adds a new simple recipe that does the actual task of exporting the keys. This patch makes the RPM_GPG_PUBKEY and PACKAGE_FEED_GPG PUBKEY settings obsolete. (From OE-Core rev: 23b30c34581948e1ea02c25cbf7b9194d7e49fb8) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-ide-support: No need to mark as nostamp anymoreRichard Purdie2015-10-011-1/+0
| | | | | | | | | With the modern checksum infrastructure, this is no longer needed (much in the same way images no longer need this). (From OE-Core rev: 30e83bbc3f90b4cd4caf8ad7ca847267ae50cf7e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Add inherit toolchain-scriptsRichard Purdie2015-07-121-0/+1
| | | | | | | | | The core class used to have this inherit but its being phased out, add the inherit directly where we need it instead. (From OE-Core rev: bdd546a8a492d386afdcc24e9540b0b88e9cd230) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-environment: Ensure we append to the default ↵Richard Purdie2015-06-231-1/+1
| | | | | | | | | | | | TOOLCHAIN_NEED_CONFIGSITE_CACHE The toolchain-scripts class was changed to assign to the variable using ??= which allows users to override it. We therefore need to _append instead of += to have the change take effect as intended. (From OE-Core rev: d589777a4d423b1f0c9953900bd79772d15ee4af) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: delete the packagedata taskChen Qi2015-04-241-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This task is meaningless for uninative-tarball as the package task has been deleted. Besides, sometimes it would cause problems. To reproduce, use the following command. bitbake uninative-tarball -c cleansstate && bitbake uninative-tarball && bitbake uninative-tarball -c clean && bitbake uninative-tarball The error is something like below. File: 'sstate.bbclass', lineno: 33, function: sstate_installpkg 0029: bb.build.exec_func(f, d) 0030: 0031: for state in ss['dirs']: 0032: prepdir(state[1]) *** 0033: os.rename(sstateinst + state[0], state[1]) 0034: sstate_install(ss, d) 0035: 0036: for plain in ss['plaindirs']: 0037: workdir = d.getVar('WORKDIR', True) Exception: OSError: [Errno 2] No such file or directory [YOCTO #7597] (From OE-Core rev: 8f905077aaed3dbeeed04787add1cf725fa87bdc) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_base: Show title in SDK installerPaul Eggleton2015-04-241-0/+2
| | | | | | | | | | | | Show a friendly title when running the SDK installer, so the user knows what SDK they are installing. The title is controlled by the SDK_INSTALLER_TITLE variable and includes the distro name and SDK version by default. (From OE-Core rev: 0af913887f4c0a79c6b950bd5d57c06333520a14) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: fix dependency on patchelfTyler Hall2015-03-251-1/+2
| | | | | | | | | | | | | | | | | DEPENDS doesn't actually add the dependency on patchelf-native to the populate_sdk task. SDK_DEPENDS does this, but move the append to after inheriting the base class so it does not get overwritten. Without this, uninative-tarball fails to build in a clean workspace on a system without patchelf. [YOCTO #7467] (From OE-Core rev: 0631c2b52432ddf86292351d605b65941d2a8be2) Signed-off-by: Tyler Hall <tylerwhall@gmail.com> Acked-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-pexpect: Adds this module to buildtools, since it is needed by some ↵Alejandro Hernandez2015-03-221-0/+1
| | | | | | | | | | | of the automated runtime test code. [YOCTO 7279] (From OE-Core rev: 5c183f69b65478a98982e544728d00269efe3e22) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_ext: add extensible SDKRandy Witt2015-02-241-0/+12
| | | | | | | | | | | | | | | | | | | | This bbclass will create an SDK with a copy of bitbake and the metadata and sstate for the target specified for the task. The idea is to let "system" developers both work on applications and then test adding them to an image without having to switch between workspaces or having to download separate items. Rather than running bitbake directly however, the primary way of running builds within the extensible SDK is to use the "devtool" command. The rest of the build system is fixed via locked shared state signatures, and thus only the recipes you have added get built. (From OE-Core rev: bf81d6bb7f6df5405b8f2148e2a22e0030c12757) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: Actually use bzip2 for compression.Randy Witt2015-02-241-1/+1
| | | | | | | | | | uninative.bbclass uses -xjf for decompression so actually run the data through bzip2. (From OE-Core rev: 84665b4e894a949591d812f1cdc1745a376bf95f) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cross-canadian/meta-environment: Allow modification of TARGET_OS to be optionalRichard Purdie2015-01-161-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are some cases we want the manipulation cross-canadian performance on TARGET_OS, there are also cases like meta-environment where we do not want this manipulation. We did try and use immediate expansion to avoid this problem and it works in the non multilib case. If we have a multilib that used an extension, like for example: require conf/multilib.conf MULTILIBS = "multilib:lib32 multilib:lib64" DEFAULTTUNE = "mips32r2" DEFAULTTUNE_virtclass-multilib-lib32 = "mips64-n32" DEFAULTTUNE_virtclass-multilib-lib64 = "mips64" then the n32 extension case will be misconfigured. It turns out saving an unexpanded variable is hard. The best I could come up with was: SAVEDTOS := "${@d.getVar('TARGET_OS', False).replace("{", "*")}" and then localdata.setVar("TARGET_OS", d.getVar("SAVEDOS", False).replace('*','{')) which is rather evil, I'd challenge someone to come up with a nicer way of making it work though! Rather than the above madness, we modify cross-canadian to make the problamtic code conditional. This fixes the original issue (where a linux-gnuspe target was seeing 'linux') of http://cgit.openembedded.org/openembedded-core/commit/?id=0038634ee6e2b6035c023a2702547f20f67c103a but also fixes the multilib one. (From OE-Core rev: 85ff3d6491c54aa712ed238c561742cda4f4ba07) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-environment: don't mark tasks as nostampPaul Eggleton2014-12-211-2/+0
| | | | | | | | | | | | | With siggen being changed to alter the signature of nostamp tasks on the fly, having these tasks as nostamp results in the SDK being rebuilt every time, which is not desirable. In any case this is just legacy from the days before we used signatures to take care of ensuring these tasks get re-run when they need to be. (From OE-Core rev: e9a211321b4570282d0d65a0bb519e05a3d477bb) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: restore missing git toolsPaul Eggleton2014-12-192-0/+23
| | | | | | | | | | | | | | | | | | | | | | Since the split out of git-perltools, some git tools (such as "git am", "git send-email" and "git-submodule") have no longer been part of the buildtools. We need these, so add them back in. However, adding git-perltools to buildtools triggers perl itself being brought into buildtools as well, and we don't want that; but we also don't want to have to hack the git recipe or indeed anything else that starts depending on perl. Thus, add a dummy package which gets installed in its place, in a separate package architecture that is only enabled for buildtools to ensure it doesn't start appearing in place of nativesdk-perl anywhere else. Fixes [YOCTO #7033]. (From OE-Core rev: 5b051d65e797624cca3a81fc6f5c924925f3493e) 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>
* meta-environment: Fix config-site with a multilib configMark Hatle2014-11-121-0/+1
| | | | | | | | | | | | | | | | | | | | [YOCTO #6951] The TOOLCHAIN_CONFIGSITE_SYSROOTCACHE value was defaulting to the nativesdk path and not the associated target path. Set the value in toolchain-scripts to the target path. Be sure to set the MLPREFIX within the meta-environment script as multilibs are processed. Update the config_site file name to use -BPN- not PN. Otherwise the environment processing can't find the correct filename. (From OE-Core rev: 1f05aaa4944ddac6c2b3ba440effdf1eaf732656) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: package all of PythonRoss Burton2014-11-051-24/+1
| | | | | | | | | | | Instead of cherry-picking pieces of Python to put into the buildtools tarball, ship all of it. We can't predict what bits of Python will be needed in the future. (From OE-Core rev: 745dfbc869fd593d1b92e2bc9c01d589ab21ade3) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-environment: Deal with machines which change TARGET_OSRichard Purdie2014-10-061-1/+4
| | | | | | | | | | Some machines change TARGET_OS, cross-canadian resets this which is not what we want in this specific case. This fixes spe toolchains for example. (From OE-Core rev: 0038634ee6e2b6035c023a2702547f20f67c103a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: Update eglibc -> glibcRichard Purdie2014-10-021-1/+1
| | | | | | (From OE-Core rev: 2b85b3f33af5157cd4b6f8a6dc737015c85018c3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-environment: Set libdir correctly to fix PKGCONFIG entriesRichard Purdie2014-10-021-0/+1
| | | | | | | | | | Currently libdir is coming from cross-canadian which is incorrect. We need to reset this to target_libdir so that the toolchains contain the correct value. (From OE-Core rev: 41f8f32c8da705ead464ee69bc5a1e120b137693) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-environment: Two critical fixes to unbreak toolchainsRichard Purdie2014-09-301-2/+2
| | | | | | | | | | | | | | | Firstly, when multilib builds were being used, the same output files were used in each case, being overwritten each time due to the fact that REAL_MULTIMACH_TARGET_SYS has been expanded. Instead of immediate expansion, just use assignment. This overrides the problematic define in toolchain-scripts.bbclass but allows the multilib code to work. Secondly, the target sysroot was being defined incorrectly which this patch fixes. This was breaking the toolchains. (From OE-Core rev: 17229152453a8633b2cd63b429f98cc7c192f300) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative: Add uninative - a way of reusing native/cross over multiple distrosRichard Purdie2014-09-231-0/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These patches are the start of a new idea, a way of allowing a single set of cross/native sstate to work over mutliple distros, even old ones. The assumption is that our own C library is basically up to date. We build and share a small tarball (~2MB) of a prebuilt copy of this along with a patchelf binary (which sadly is C++ based so libstdc++ is in there). This tarball can be generated from our usual SDK generation process through the supplied recipe, uninative-tarball. At the start of the build, if its not been extracted into the sysroot, this tarball is extracted there and configured for the specified path. When we install binaries from a "uninative" sstate feed, we change the dynamic loader to point at this dynamic loader and C librbary. This works exactly the same way as our relocatable SDK does. The only real difference is a switch to use patchelf, so even if the interpreter section is too small, it can still adjust the binary. Right now this implements a working proof of concept. If you build the tarball and place it at the head of the tree (in COREBASE), you can run a build from sstate and successfully build packages and construct images. There is some improvement needed, its hardcoded for x86_64 right now, its trivial to add 32 bit support too. The tarball isn't fetched right now, there is just a harcoded path assumption and there is no error handling. I haven't figured out the best delivery mechanism for that yet. BuildStarted is probably not the right event to hook on either. I've merged this to illustrate how with a small change, we might make the native/cross sstate much more reusable and hence improve the accessibility of lower overhead builds. With this change, its possible the Yocto Project may be able to support a configured sstate mirror out the box. This also has positive implications for our developer workflow/SDK improvements. (From OE-Core rev: e66c96ae9c7ba21ebd04a4807390f0031238a85a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_base/meta-environment: Remove overlap from the twoRichard Purdie2014-09-221-7/+28
| | | | | | | | | | | | | | | | | | | | Currently we have the horrible situation where meta-environment packages the toolchain environment files and they get included in the SDK but are broken, then, the SDK code overwrites them with good versions. This is suboptimal. This change fixes the code in meta-environment to create working files and adds in the multilib support from populate_sdk_base, then we remove the code in that base bbclass and rely on the packages being installed if/as/when needed. This removes the duplication and the broken versions of the files, hopefully making all well. [YOCTO #6608] [YOCTO #6613] (From OE-Core rev: 063355e5965439c7b3253d692d7ab0ed1189d123) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-environment: Fix TARGET_OS problem for ppcRichard Purdie2014-09-221-1/+2
| | | | | | | | | | | | | | | | Due to the use of the cross-canadian inherit, TARGET_OS can be reset to values other than the correct one, leading to generation of the wrong files. By expanding REAL_MULTIMACH_TARGET_SYS before the inherit, the correct OS value is preserved and we generate the right environment files. [YOCTO #6608] [YOCTO #6613] (From OE-Core rev: ae265973c96ff4b8b5580436647fc361490e134c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: export GIT_SSL_CAINFOFahad Usman2014-08-291-0/+2
| | | | | | | | | | export GIT_SSL_CAINFO so git can find the certs (From OE-Core rev: 260ea7b85ecacf2fcd4d09fa2f602d3e4368ef69) Signed-off-by: Fahad Usman <fahad.usman@gmail.com> Signed-off-by: Christopher Larson <kergoth@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: include nativesdk-ca-certificatesFahad Usman2014-08-291-0/+1
| | | | | | | | | | | | | nativesdk-ca-certificates is needed in order to support oe/yocto builds with buildtools-tarball on old hosts, as we provide libcurl, and that needs to be able to find the certs, and there's no standard path or bundle path, so we can't rely on the host. (From OE-Core rev: 057954bcc4baf9194968169591537cd7584f8bcb) Signed-off-by: Fahad Usman <fahad.usman@gmail.com> Signed-off-by: Christopher Larson <kergoth@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Remove remnants of deleted "do_package_write" task.Robert P. J. Day2014-08-112-2/+0
| | | | | | | | | | As the do_package_write() task is listed as deleted, remove the few remaining references. (From OE-Core rev: 201d572ab5c57cda1b332356a3b7711bc346696e) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Add wget to buildtools-tarballTudor Florea2014-07-211-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | GNU Wget cannot be upgrated to a newer that 1.12 version on supported Centos distro. GNU Wget 1.12 and earlier uses a server-provided filename instead of the original URL to determine the destination filename of a download. This means the files downloaded when fetching cannot be properly used: $ wget http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.4.2/source/eventlog_0.2.13.tar.gz $ ls eventlog_0.2.13.tar.gz?AWSAccessKeyId=AKIAICTJ5MANGPMOH7JA&Expires=1400838672&Signature=TjakOBpOvHtEKKDgF14iVinWpY0= This in turn lead to build errors like: WARNING: Failed to fetch URL http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.4.2/source/eventlog_0.2.13.tar.gz, attempting MIRRORS if available ERROR: Fetcher failure for URL: 'http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.4.2/source/eventlog_0.2.13.tar.gz&#39;. The fetch command returned success for url http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.4.2/source/eventlog_0.2.13.tar.gz but /path/to/downloads/eventlog_0.2.13.tar.gz doesn't exist?! ERROR: Function failed: Fetcher failure for URL: 'http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.4.2/source/eventlog_0.2.13.tar.gz&#39;. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /path/to/tmp/work/ppce500v2-enea-linux-gnuspe/eventlog/0.2.13-r0/temp/log.do_fetch.28302 ERROR: Task 4 (/path/to/poky/meta-openembedded/meta-oe/recipes-support/eventlog/eventlog_0.2.13.bb, do_fetch) failed with exit code '1' [YOCTO #6549] (From OE-Core rev: 16dcc820af60f1a875c9b3b13b545a78124ddd7f) Signed-off-by: Tudor Florea <tudor.florea@enea.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils/gcc/gdb: Add TARGET_ARCH to PN for all cross recipesRichard Purdie2014-04-301-1/+1
| | | | | | | | | This allows them to co-exist together in the native sysroot, with one set of cross tools per target architecture. (From OE-Core rev: a2c5509520d5c3e082f55844e6545d0309565f8f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package-index.bb: use the new python indexing routinesLaurentiu Palcu2014-02-141-4/+3
| | | | | | | (From OE-Core rev: 1ee44591a8475121ea949cd2d8518a6dac965a19) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@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-10 01:35:36 +0000