summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/meta
Commit message (Collapse)AuthorAgeFilesLines
* uninative-tarball: delete the packagedata taskChen Qi2015-05-151-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) (From OE-Core rev: e94864c1589986fb8a59ee86cae0fd3b430ebf09) Signed-off-by: Chen Qi <Qi.Chen@windriver.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>
* unfs3, unfs-server: Replace all instances of unfs-server with unfs3Jason Wessel2014-01-281-1/+1
| | | | | | | | | | | | | | | Other recipes dependencies and even some comments need to be updated for the removal of unfs-server and the replacement with unfs3. The unfs3 is a complete drop in replacement providing all the prior functionality of NFSv2 but also adding NFSv3. [YOCTO #5639] (From OE-Core rev: d577c56519a448b142da5b43e46d5bd9d3a3b4bd) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Update after toplevel LICENSE file checksum changeRichard Purdie2014-01-024-4/+4
| | | | | | (From OE-Core rev: bbd88aebcabbb19c27a7d752d4a5b8ad9ff9412e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add missing SUMMARY valuesPaul Eggleton2014-01-021-0/+1
| | | | | | | | | | | | These recipes all had a long DESCRIPTION but no SUMMARY; since the SUMMARY is often displayed alone by package managers and the default value ("${PN} version ${PV}") isn't particularly useful, we should always try to set SUMMARY. (From OE-Core rev: db02edd2e9d7645592933cbb25ea0ca4d6561392) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Replace one-line DESCRIPTION with SUMMARYPaul Eggleton2014-01-023-3/+3
| | | | | | | | | | | | | | A lot of our recipes had short one-line DESCRIPTION values and no SUMMARY value set. In this case it's much better to just set SUMMARY since DESCRIPTION is defaulted from SUMMARY anyway and then the SUMMARY is at least useful. I also took the opportunity to fix up a lot of the new SUMMARY values, making them concisely explain the function of the recipe / package where possible. (From OE-Core rev: b8feee3cf21f70ba4ec3b822d2f596d4fc02a292) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* external-sourcery-toolchain: removePaul Eggleton2013-12-122-406/+0
| | | | | | | | | | | | | | | | | As per discussion on the mailing list [1], remove this largely unmaintained external toolchain support in favour of the maintained version in meta-sourcery [2]. Also correct the example and documentation.conf entries for TCMODE to match up with this change. [1] http://lists.openembedded.org/pipermail/openembedded-core/2013-December/087133.html [2] https://github.com/MentorEmbedded/meta-sourcery/ (From OE-Core rev: 7603b15415301679bccbcb89af688c211704a43a) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gmae: remove GMAE toolchain and packagegroupsRoss Burton2013-12-051-7/+0
| | | | | | | | | | | GMAE (GNOME Mobile And Embedded) doesn't really exist anymore and these packages were a subset of it anyway. Remove as they don't give the user anything useful now that you can generate a SDK from an arbitrary image. (From OE-Core rev: c44fa1206c965054e8e4d316969a8e291cfef590) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-scripts/meta-environment: Further cleanup code duplicationRichard Purdie2013-11-061-1/+1
| | | | | | | | | | | | | | There was still duplicated code in toolchain-scripts, this further cleans up the functions to remove it. The now unused includedir parameter is also dropped. The final scripts do end up reordered slightly and the sysroot is parametrised for the IDE scripts which is an improvement but should have no functional difference. (From OE-Core rev: 1dbd65b4d14319e784a66776c1e9943d0179d3ee) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-scripts/meta-environment: Merge toolchain_create_sdk_env_script ↵Richard Purdie2013-11-061-1/+1
| | | | | | | | | | | | and the for_installer variant Having two scripts which do basically the same thing is a nightmare. This merges them together. It also makes the sysroot location a variable in its own right which may be more useful for end users wanting to change sysroot. (From OE-Core rev: 213e0c67e938b802e6bb2246f00b7343a6f77b99) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pigz: Add pigz to buildtools tarballKonrad Scherer2013-10-301-0/+1
| | | | | | | | | | | | | | When using the tar executable in the buildtools, tar will execute gzip. If this happens before zlib-native is built, then the gzip on the host will be used and can fail if the libz in the buildtools is not compatible. Adding pigz to the build tools avoids this host contamination. (From OE-Core rev: af6424e8c2bf3a938fddabc669c0956d68964ed0) Signed-off-by: Konrad Scherer <Konrad.Scherer@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-environment: change package name to include MACHINELaurentiu Palcu2013-09-101-1/+1
| | | | | | | | | | | | | | | | | Currently, the package name contains just the TRANSLATED_TARGET_ARCH. When compiling the toolchain for two machines, belonging to the same architecture (for example: qemuarm and beagleboard), this package gets overwritten and adt-installer repo will contain just one meta-environment package... This leads to situations like installing the toolchain for qemuarm and end up with meta-environment package with beagleboard cpu options. [YOCTO #4783] (From OE-Core rev: 09a2b158818e2ec3c3e3b53b6d14fd3527c32c99) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Add python-pkgutilRichard Purdie2013-08-291-0/+1
| | | | | | | | | This is needed by some recently added automated QA tests so we should add it to the buildtools tarball. (From OE-Core rev: 7d93288117e7054472d8a01dde0b38bc0ff98c27) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: do not export OECORE_NATIVE_SYSROOTChen Qi2013-08-061-2/+5
| | | | | | | | | | | | | | | | | | | | | | | When building a qemu image inside the environment created by the buildtools-tarball, the qemu image cannot be started, as the runqemu script uses the tunctl binary which cannot be found inside the sysroot directory of the buildtools-tarball. The buildtools-tarball is inherently a tool set instead of a fully functional SDK, so leaving the OECORE_NATIVE_SYSROOT variable in the environment will mess things up. However, we do need a line of 'OECORE_NATIVE_SYSROOT=xxx' in the environment setup script so that the SDK can be extracted and relocated correctly. Thus, instead of exporting OECORE_NATIVE_SYSROOT, we use a comment here. [YOCTO #4939] (From OE-Core rev: d4a4c764a844a7e61f866af9361f139684037336) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* external-sourcery: add missing providersSaul Wold2013-07-291-0/+2
| | | | | | | | | | | | | | | | | | | | Addess the issue with multiple .bb providers ERROR: Multiple .bb files are due to be built which each provide virtual/libc (/srv/hdd/releases/dylan/meta/recipes-core/eglibc/eglibc_2.17.bb /srv/hdd/releases/dylan/meta/recipes-core/meta/external-sourcery-toolchain.bb). This usually means one provides something the other doesn't and should. ERROR: Multiple .bb files are due to be built which each provide virtual/arm-none-linux-gnueabi-libc-for-gcc (/srv/hdd/releases/dylan/meta/recipes-core/eglibc/eglibc_2.17.bb /srv/hdd/releases/dylan/meta/recipes-core/meta/external-sourcery-toolchain.bb). This usually means one provides something the other doesn't and should. ERROR: Multiple .bb files are due to be built which each provide virtual/libiconv (/srv/hdd/releases/dylan/meta/recipes-core/eglibc/eglibc_2.17.bb /srv/hdd/releases/dylan/meta/recipes-core/meta/external-sourcery-toolchain.bb). This usually means one provides something the other doesn't and should. Thanks to Kergoth (Chris Larson) and Lpapp (Lazslo) [YOCTO #4908] (From OE-Core rev: 09deeef20ee5a0c12ad4fd89cace6e0fb832d5b1) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: testimage needs the mmap python-moduleSaul Wold2013-07-181-0/+1
| | | | | | | | | | The new testimage class needs the mmap python-module in the buildtools-tarball on machines that use the tarball to provide the correct version of python. (From OE-Core rev: 0b3574481cb8204513001570f5fa3cc8f50ba510) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: add python-gitPaul Eggleton2013-07-021-0/+1
| | | | | | | | | | | | | | python-git is needed by buildhistory-diff and the OE layer index update script, and on machines where buildtools-tarball is necessary given we are providing python we must provide this module as well. Fixes [YOCTO #4747]. (From OE-Core rev: d9bf76b4fafc0ddcb19bf393e5e22678e49367b3) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Add nativesdk-makeMark Hatle2013-06-251-1/+2
| | | | | | | | | | | | Recently it was discovered that many Fedora hosts have a broken version of make 3.82. Add make to the buildtools-tarball, as well ad modify make to support building a special nativesdk version. (From OE-Core rev: ea972fc4ce2268f01be6beeafd27dd949d800f9d) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Change the way the SDK is sanitizedMark Hatle2013-06-251-4/+11
| | | | | | | | | | | | | | | | | The previous method of shrinking down the scale of the environment-setup file would not work properly when the target is configured with multilibs. In addition, the configured machine name and similar settings could leak into the SDK naming. This was resolved by clearing the SDK generated files and generating our own custom files. Note, the name of the environment-setup now is suffixed with the SDK_SYS. (From OE-Core rev: 778cd8d2110ef2db5ff4ae4f0b55c52a8f1ea334) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Add nativesdk-ncurses-terminfo-baseRichard Purdie2013-06-141-0/+1
| | | | | | | | | | | | We've been seeing issues where some TERM values don't work well with the tarball. These show up as escape codes coming from simple python calls such as printing the python version. Adding the terminfo goes part way to addressing the problem, the remainder is ensuring the relocation code correctly searches the right path for it (which will be in a follow on patch). (From OE-Core rev: 697e64c98affc4e0d8aa4828e74331c918b23a0e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: add difflib and pprint python modulesSaul Wold2013-06-111-0/+2
| | | | | | | | | Needed for the unittest part of bitbake-selftest can work correctly. (From OE-Core rev: fe744381e8844ad17dcc6e036650a442dbc9575d) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Add json, unittest and compression python module packagesRichard Purdie2013-06-101-0/+3
| | | | | | | | | We need unittest so bitbake-selftest can work, tarfile from the compression module for opkg-utils and json for webkit builds. (From OE-Core rev: bbcb7329ca4340dbd3d529567dc6b605347e3368) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-external-tarball: Improve DESCRIPTION/SUMMARYRichard Purdie2013-06-071-1/+3
| | | | | | | | Improve the DESCRIPTION for the recipe and add a SUMMMARY. (From OE-Core rev: ecdccd0c19c1d27aee43a3cca8e4467f270d7f9c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-external-tarball: Modernise and renameRichard Purdie2013-06-071-4/+12
| | | | | | | | | | | | | | | | | The external-python-tarball was intended to provide python for those users who didn't have python 2.6. It has been unloved for a while so this refreshes it a bit. Specifically: * Include git and tar since these can have version issues on some systems * Rename to buildtools-tarball to better reflect its purpose * Remove the site-config file from the tarball, its pointless * Prune down the environment file to just cover PATH and OECORE_NATIVE (which is needed to correctly install the tarball) * Add missing grp module (used by do_package) from the unixadmin package (From OE-Core rev: c8de009e96930709efe8f6aa4e65dd04a48081f2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/recipes/lib: Fix various python whitespace issuesRichard Purdie2013-05-091-1/+1
| | | | | | | | | There are some left over tab characters in the python functions. This removes them and resolves python 3 errors. (From OE-Core rev: fafeb381c48291fa65c634c01c244843c8d7fad3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* external-sourcery-toolchain: add SUMMARYPaul Eggleton2013-04-291-0/+1
| | | | | | | | (From OE-Core rev: c12ed47769d7784d0483629dd56b42bf84f50510) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* external-python-tarball: rename output packageKang Kai2013-03-141-1/+1
| | | | | | | | | | | | Update TOOLCHAIN_OUTPUTNAME to rename the output package which is the similiar style to name packages meta-toolchain-*. [YOCTO #3996] (From OE-Core rev: e40c36ff8610ebb9ce16a4d1c14c7cf94f87cd6a) Signed-off-by: Kang Kai <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: Fix ALLOW_EMPTY with no package specifiedRichard Purdie2013-03-051-1/+0
| | | | | | | | | | | There are various usages of ALLOW_EMPTY with no packages specified. This is not recommended syntax, nor is it likely to be supported in the future. This patch improves the references in OE-Core, either removing them if they're pointless (e.g. when PACKAGES="") or specifying which package it applies to. (From OE-Core rev: fe81bd4f600877e63433184cfc2e22c33bb77db6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* external-python-tarball: code refactoringKang Kai2013-02-221-63/+4
| | | | | | | | | | | | | | | | | external-python-tarball only can be built when inherit package_ipk now. Update it to reuse existed populate sdk code that it could be built for rpm and deb too. Remove var DEPENDS, SDK_* and flags of do_populate_sdk because they are already defined in populate_sdk bbclasses. [Yocto 3006] (From OE-Core rev: 57134958a2c6b74de8654600e33acdd265966638) Signed-off-by: Kang Kai <kai.kang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
OpenPOWER on IntegriCloud