summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Revert "kernel-arch.bbclass: add arm64 support to U-Boot architecture map"Nathan Rossi2015-02-211-1/+0
| | | | | | | | | | | | | | | | This reverts commit 0b891265716c414ade29d587fc1a3c4ea7beadbe. U-Boot does support AArch64, this however was only added to newer versions of U-Boot and at the time of this original commit the U-Boot in OE-Core did not support the 'arm64' architecture. OE-Core now has a newer version of U-Boot for the mkimage recipe and thus supports the 'arm64' architecture. (From OE-Core rev: fd8158134f3d7a7c795c818cc50eb2858a6cae06) Signed-off-by: Nathan Rossi <nathan.rossi@xilinx.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* logrotate: 3.8.8 -> 3.8.9Robert Yang2015-02-214-48/+60
| | | | | | | (From OE-Core rev: 32848c7015f5d70c4245a9b1bb77c21faef8653d) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-gitdb: 0.6.1 -> 0.6.4Robert Yang2015-02-211-2/+2
| | | | | | | (From OE-Core rev: 66be4fc8bd08df1c2807a61eebbae912cf07157d) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-git: 0.3.3 -> 0.3.6Robert Yang2015-02-211-2/+2
| | | | | | | (From OE-Core rev: 8846e5a1896bc2083a326cc542d2cdde83b915da) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* git: 2.2.1 -> 2.3.0Robert Yang2015-02-213-11/+12
| | | | | | | (From OE-Core rev: 92a27c29570541564d65bf43325a333960b40183) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cups: 2.0.1 -> 2.0.2Robert Yang2015-02-214-41/+6
| | | | | | | | | | Removed the patch since upstream has fixed it: 0001-test-ippserver.c-check-avahi-before-use.patch (From OE-Core rev: e1a8de7d55710199d357c88c22f3f1887d562b61) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* quilt: 0.63 -> 0.64Robert Yang2015-02-213-4/+4
| | | | | | | | | | quilt-0.63.inc -> quilt.inc: we don't have multiple quilt-xxx.inc, so use quilt.inc rather than quilt-0.63.inc. (From OE-Core rev: 941be822ee7772b70fe78e6b61278bb8567bc905) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernelshark: Update to version 2.5.3Ben Shelton2015-02-212-37/+11
| | | | | | | | | | | | | | | | | | | | | | | | Update to version 2.5.3 to match trace-cmd. Changes include: - Remove kernelshark-fix-syntax-error-of-shell.patch (the syntax error is no longer present in the new version). - Specify bindir_relative and libdir in EXTRA_OEMAKE as in the trace-cmd recipe so files get installed to the right place. Additionally, remove unnecessary EXTRA_OEMAKE options. - Fix up the do_install steps to remove the plugins directory; that directory now lives under /usr/lib. - Set NO_PYTHON=1 because building the ctracecmd Python module requires swig, which is not available in oe-core. (From OE-Core rev: 2f177644dab083bc5306bce1bf2ff2ef8851c862) Signed-off-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* trace-cmd: Update to version 2.5.3Ben Shelton2015-02-214-101/+6
| | | | | | | | | | | | | | | | | | | | | | | Updating adds new features including the very useful 'profile' option. Changes include: - Remove addldflags.patch (already upstream in the new version). - Remove make-docs-optional.patch (docs are built in a separate target in the new version). - Update SRC_URI, SRCREV, PR, and PV in the .inc file and don't override them in the recipe. - Fix a typo in LIC_FILES_CHECKSUM so 'endline' is properly defined. - Drop PR. (From OE-Core rev: 30eba39bd3b915477c584d8bebd194446497175e) Signed-off-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/parselogs: Add exception for new mips error messageRichard Purdie2015-02-211-0/+1
| | | | | | | | The 3.19 kernel introduces this error, ignore it for now. (From OE-Core rev: 2a0a14275ca00b2d3ca867c82548a41e3bb10986) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: warn when a generated BSP description is usedBruce Ashfield2015-02-211-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | The meta data (in tree or out of tree) that describes a BSP, its patches and configuration is not always available when a new/default or manually configured machine is built. When this happens, the tools generate a skeleton BSP and use a architecture defconfig for the build. If this is by design, the build is typically sane and everything works fine. If an existing BSP description was expected, chances are that the resulting kernel will not be correct. To avoid surprising the user when a default/skeleton BSP is used for the build, we can make it obvious to the user by emitting a warning like the following: WARNING: [kernel]: An auto generated BSP description was used, this normally indicates a misconfiguration. Check that your machine (myqemux86-64) has an associated kernel description. [YOCTO: #3383] (From OE-Core rev: f4a460afc4e2676cbf1daaa1d6723da9e6146526) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: introduce 3.19 versioned recipesBruce Ashfield2015-02-212-0/+60
| | | | | | | | | | | | Introducing the v3.19.x recipes for the validated linux-yocto kernel. Build, boot and sanity testing was performed on qemu for all major architectures. (From OE-Core rev: 329a028bec428e8dc8cf3420c6e462de2898c8aa) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: remove 3.10 and 3.17 recipesBruce Ashfield2015-02-215-146/+0
| | | | | | | | | | | | | In accordance with the kernel release criteria we support the latest mainline kernel + the last LSTI kernel + a development kernel. 3.19 will be introduced as the latest mainline, and 3.14 is the released LTSI kernel, which means that we remove the 3.10 and 3.17 variants. (From OE-Core rev: 19203a95f4b65e0a009a738fb4fc216e985a0835) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: make kernel configuration audit user visibleBruce Ashfield2015-02-213-8/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After a linux-yocto style kernel is configured, a kernel configuration audit is executed to detect common errors or issues with the config. This output used to be visible, but was made less obvious to not alarm users unnecessarily (since some configuration issues are acceptable). There are some classes of configuration issue that are worth being visible, and that is specified configuration values that do not make the final .config. These dropped options can result in any number of runtime failures, so flagging them at build time makes sense. The visibility of auditing is controlled by KCONF_AUDIT_LEVEL: 0: no reporting 1: report options that are specified, but not in the final config 2: report options that are not hardware related, but set by a BSP The default level is 1, with level 2 and above being for BSP development only. If these conditions are detected, warnings will be generated as follows: WARNING: [kernel config]: specified values did not make it into the kernel's final configuration: Value requested for CONFIG_SND_PCSP not in final ".config" Requested value: "CONFIG_SND_PCSP=y" Actual value set: "" or WARNING: [kernel config]: BSP specified non-hw configuration: CONFIG_BLOCK CONFIG_CFG80211_WEXT CONFIG_CORDIC CONFIG_CRC8 CONFIG_EFIVAR_FS CONFIG_EFI_PARTITION CONFIG_NET CONFIG_NETDEVICES CONFIG_PARTITION_ADVANCED CONFIG_WEXT_CORE CONFIG_WEXT_PROC CONFIG_WIRELESS At this point thse are only a warnings, since there needs to be time for layers and configuration fragments to be validated against this new check. [YOCTO: #6943] (From OE-Core rev: ad4d59495194b37bc510e9891bd14c0a2ac30dba) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: update to 3.19Bruce Ashfield2015-02-213-8/+8
| | | | | | | | | Updating the libc-headers now that the kernel has released. (From OE-Core rev: b3721560fe523c144690ebfeb203b3735d0f6843) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toaster: importlayer Remove description input fieldMichael Wood2015-02-203-10/+0
| | | | | | | | | | | | | This wasn't required or working due to a typo and adds ambiguity between the summary and description. The correct method for changing the description or summary is via the layerdetails page. [YOCTO #7190] (Bitbake rev: 605298ff3ce919127003dadef95798472327f943) Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toasterui: remove layer directory in managed modeBelen Barros Pena2015-02-202-5/+13
| | | | | | | | | | | | Removes the layer directory information from the packages built page when in managed mode. [YOCTO #7221] (Bitbake rev: 1eaf60d0fe34f5f43386c6f0e91f0b26c7a62845) Signed-off-by: Belen Barros Pena <belen.barros.pena@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toasterui: style the Toaster version informationBelen Barros Pena2015-02-202-25/+10
| | | | | | | | | | | In debug mode, we show the Toaster version and mode in the top bar. Display them inside a tooltip that appears when you hover over a nice info icon to make them less conspicuous. (Bitbake rev: 8365f19191d0ec5901c79b7afd5005f7a546fe74) Signed-off-by: Belen Barros Pena <belen.barros.pena@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toaster: layerdetails Don't show None type in description/summaryMichael Wood2015-02-201-2/+2
| | | | | | | | | | | | | When the result for the summary or description is None don't output the result as the string version of None, use an empty value so that the "Not set" mechanism works. [YOCTO #7244] (Bitbake rev: 34397e585df0fc04ea53046347856e8cddb8f8e1) Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toaster: landing page when no build moduleDavid Reyna2015-02-202-21/+53
| | | | | | | | | | | | | | Add landing page for managed build pages when build module not installed. Some wording and whitespace changed. [YOCTO #6483] (Bitbake rev: 6618a0a71cc9ea5426238549094ab9e05ae61649) Signed-off-by: David Reyna <David.Reyna@windriver.com> Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toaster: get proper version stringAlexandru DAMIAN2015-02-201-1/+2
| | | | | | | | | | | This patch brings in the toaster tree commit ID in the version string to allow users properly report their toaster version when submitting issues. (Bitbake rev: 5cc87ee0ac3b2bd399e7f009dda9d6de87209a27) Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toasterui: UI query performance improvementsAlexandru DAMIAN2015-02-202-10/+16
| | | | | | | | | | | We reduce the number of queries by using "select_related" to bring in more data in a single query. Improvements in project page refresh, recipes table and tasks table. (Bitbake rev: eefdae12120f879b555ba0a353277a18675eecbc) Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toasterui: fix time estimation in project pageAlexandru Damian2015-02-204-7/+24
| | | | | | | | | | | | | | This patch fixes the time estimation to build completion in project page. Additionally it fixes the Most Recent Builds section used in various pages in managed mode, and proper time to build estimation in all pages. [YOCTO #7004] (Bitbake rev: 5fecfda0e47c2ecba9b7c903c6d258eefa431aa0) Signed-off-by: Alexandru Damian <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toaster: properly detect starting in rolling log fileAlexandru DAMIAN2015-02-201-2/+10
| | | | | | | | | | This patch brings in properly detection of system start in a rolling toaster_ui log file. (Bitbake rev: 6da36cbf5eeb30b8352c22aed3e0ede35705e13c) Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toaster: bitbake cooker log saving and downloadingAlexandru DAMIAN2015-02-2013-43/+335
| | | | | | | | | | | | | | | | | | | | | This patch brings in cooker log saving and proper download links. * toasterui will now write the cooker log file if running in managed mode * the BuildRequest has a new state, REQ_ARCHIVE, indicating that the build is completed, and the artifacts are ready to be grabbed * the runbuild test execution commands will gather needed artifacts, and save them to a storage directory selected during Toaster setup. * the build dashboard, project builds and all builds pages have permanent links for the cooker log [YOCTO #7220] [YOCTO #7206] (Bitbake rev: fad80e36c9da663b000cdf2cb3c75440c6431d84) Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Update to glibc 2.21 release tagDan McGregor2015-02-202-7/+5
| | | | | | | | (From OE-Core rev: 530565c6cb77319f4cc49edeea6fec6be997415d) Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Upgrade 2.20 -> 2.21Khem Raj2015-02-2016-1646/+1087
| | | | | | | | | | | | | | Drop CVE backports and ppc/fpu detection patch which is not needed anymore Forward port eglibc option groups patch Default to using glibc 2.21 Additional patches needed to appease -Werror option Change-Id: I1873097cec8387ea9e8186a255122938fc28c976 (From OE-Core rev: 6617cc92076764d51f0190786f8d62b8c99ae984) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lzo: Upgrade to 2.09 and add ptestSaul Wold2015-02-192-4/+23
| | | | | | | | | lzo_init checksum changed due to date change, not license change (From OE-Core rev: ad016fa7492ba23c751cf33dd1befde7782facfa) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bind: Fix parallel make issueRobert Yang2015-02-192-0/+45
| | | | | | | | | | | | | | | | | | Fixed: unix/os.o: file not recognized: File truncated collect2: error: ld returned 1 exit status This is because os.o was built twice: * The implicity rule (depends on unix/os.o) * The "make all" in unix subdir (depends on unix/os.o) Depend on subdirs which is unix only rather than unix/os.o will fix the problem. (From OE-Core rev: 1af699e1af2552659b90a1fadd8de73d780226ba) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* btrfs-tools: fix for parallel buildRobert Yang2015-02-192-1/+36
| | | | | | | | | | | Fixed: mkfs.c:300:46: error: 'BTRFS_BUILD_VERSION' undeclared (first use in this function) fprintf(stderr, "mkfs.btrfs, part of %s\n", BTRFS_BUILD_VERSION); (From OE-Core rev: 5808c423a2cbea9f2f6a9f78ce5ca09864dc6a75) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* busybox: update to 1.23.1 releaseFathi Boudra2015-02-193-47/+4
| | | | | | | | | | | | | * Bump SRCREV/PV * Drop PR * Update SRC_URI md5sum/sha256sum * Drop 0001-build-system-Specify-nostldlib-when-linking-to-.o-fi.patch - applied upstream and available in 1.23.1 release (From OE-Core rev: 2c59692c4fa4a0a21dee23b8affc3c8e58ff7a11) Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl: disable SSLv3 by defaultBrendan Le Foll2015-02-191-0/+4
| | | | | | | | | | Because of the SSLv3 POODLE vulnerability, it's preferred to simply disable SSLv3 even if patched with the TLS_FALLBACK_SCSV (From OE-Core rev: 4e691d06ffdb4d1fd940996f419308fe53454df7) Signed-off-by: Brendan Le Foll <brendan.le.foll@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packaging: allow globs in CONFFILESChen Qi2015-02-194-21/+64
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Allow globs in CONFFILES. This patch changes the way of CONFFILES handling. After this change, the CONFFILES can take the same form as FILES. That means, we don't have to list a bunch of files for CONFFILES. It will just be expanded like the FILES variable. We don't assume default value for CONFFILES in OE. But distro vendors could provide a default value for CONFFILES in their distro configuration file like below. CONFFILES = "${sysconfdir}" In this way, files under /etc are treated as configuration files by default. Of course, setting CONFFILES in recipes take precedence over the CONFFILES. For example, if the recipe author decides that package A should only treat files under ${sysconfdir}/default/ as config files, he/she can write like this. CONFFILES_A = "${sysconfdir}/default" [YOCTO #5200] (From OE-Core rev: 0d446ef0e5bbca7058eec7259e34f2a1637dfab1) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qt-mobility: Add patch to fix disabling bluez compile issuesRichard Purdie2015-02-192-0/+339
| | | | | | | | | | If you disable bluez but have dbus enabled, the build would fail. This patch fixes the issue so that bluez5 based builds work. (From OE-Core rev: 1324839b2be97c19e0a1fbd6ec8d3357731e5973) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/ptest: Fixed complementary package install detection and added ↵Lucian Musat2015-02-191-3/+6
| | | | | | | | | ptest-runner exit code check (From OE-Core rev: b214c7b901fe0fad081d7a97f9e91cc218c66bd6) Signed-off-by: Lucian Musat <george.l.musat@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* license.bbclass: fix unexpected operator for LICENSE values with spaceMartin Jansa2015-02-171-1/+1
| | | | | | | | | | | * add quotes around pkged_lic so that it works correctly with spaces * fixes following error: run.license_create_manifest.50601: 193: [: GPLv2: unexpected operator (From OE-Core rev: 2bb8b2abb689d91b7b7e28e6bd528747bde94dd2) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: add glibc-2.21 to glibc.patchMartin Jansa2015-02-172-3/+10
| | | | | | | (From OE-Core rev: 68ccb00b024efccb70efffc80a57b819f10a95e0) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* useradd.bbclass: avoid do_rootfs error for debian package backendChen Qi2015-02-171-0/+10
| | | | | | | | | | | | | | | | | | | | | | | If /etc/login.defs is treated as a configuration file, then we would meet errors at do_rootfs time telling us that useradd/groupadd cannot execute correctly. This is because the dpkg handles config file specially, the login.defs is temporarily renamed as login.defs.dpkg-new. How ubuntu deals the user/group adding problem? They do it at postinst of the package. And, the postinst script of a package would possibly do `chown' of its files or directories. The above strategy is not suitable for OE. Because we do chown in do_install and add user/group in preinst scripts of the packages. That's why we need this patch so that do_rootfs don't fail. (From OE-Core rev: d98e5ec575f542b3afaabd96b07ae9a21e1c22f4) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* update-rc.d: use '-f' option in updatercd_postrmChen Qi2015-02-171-2/+2
| | | | | | | | | | | | | | | | | | | | Use '-f' ('--force') option so that while removing packages using deb, we don't fail because of the following error: update-rc.d: $initd/$bn exists during rc.d purge (use -f to force) Using '-f' option would make this a warning but continue to execute. update-rc.d: $initd/$bn exists during rc.d purge (continuing) We need this option because dpkg package backend have special handling for configuration files. And if files under /etc/init.d are treated as configuration files, we will have errors. (From OE-Core rev: ebb2d557bbf410d98040cdaabbddd7e3ee0a9709) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_manager.py: use 'purge' instead of 'remove' in case of debChen Qi2015-02-171-2/+2
| | | | | | | | | | | We need to use 'purge' instead of 'remove' for debian package backend when removing packages at rootfs time. This is because that 'remove' command for 'dpkg' and 'apt-get' does not remove configuration files. (From OE-Core rev: 14e8d826c4a5231ef331d8064d150737fe3ed656) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts: delete dummy help2man scriptPaul Gortmaker2015-02-171-3/+0
| | | | | | | | | | | | | | | | | | | This was added to try and deal with the cross compile issue of help2man ; one can not run an ARM binary "./chmod --help" on an x86-64 host in order to get the help text to create a man page. This has been primarily an issue with the coreutils package. However, we have since fixed coreutils to have useful pre-made manpages and we don't need this script anymore. And if other gnu packages are getting useless truncated "dummy" manpages, we want the build to fail so we can fix those packages in a similar way, vs. having the issue hidden via a help2man that is a no-op. (From OE-Core rev: 3fc812377baf95768cef0b7728a73a4b9e07f2ab) Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* coreutils: import prebuilt manpages from GentooPaul Gortmaker2015-02-171-3/+18
| | | | | | | | | | | | | | | | | | | | As can be seen here: http://lists.gnu.org/archive/html/coreutils/2014-11/msg00001.html other people have run into the headache of trying to cross compile coreutils, with the "help2man" problem (assumes host can run the target binaries with "--help" arg to collect data for manpage.) And since "current wisdom is this is working as intended" we are largely left with no choice but to use the same solution and abandon trying to generate the man pages at build time. So here we import prebuilt manpages. (From OE-Core rev: 1c0bdebbe362dc47b3b6f521ba15ccf0de15e5b5) Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* coreutils: don't generate useless dummy stub manpagesPaul Gortmaker2015-02-174-55/+28
| | | | | | | | | | | | | | | | | | | | | | | | | We had a couple patches to 1) deal with missing perl and 2) deal with the perl-less "dummy" help2man fallout, but in the end, they achieve no purpose whatsoever, since they just populate the doc RPM with manpages like this one: NAME chmod - a GNU coreutils 8.22 program DESCRIPTION OOOPS! Due to the lack of perl on the build system, we were unable to create a proper manual page for chmod. As the above serves no purpose whatsoever, and since the concept of running the binaries to capture the "--help" text output is completely broken for cross compiles, lets just decouple man page generation from the building of coreutils entirely so it paves the way for importing pre-generated manpages. (From OE-Core rev: cb2519466b4d28217ae955370077bc4a8f9b6dce) Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* utils.bbclass: fix create_cmdline_wrapperJavier Viguera2015-02-171-2/+2
| | | | | | | | | | | | | | | | | | | Similar to commit 4569d74 for create_wrapper function, this commit fixes hardcoded absolute build paths in create_cmdline_wrapper. Otherwise we end up with incorrect paths in users of this function. For example the 'file' wrapper in current released toolchain: exec -a /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-arm/build/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-file/5.18-r0/image//opt/poky/1.7.1/sysroots/x86_64-pokysdk-linux/usr/bin/file `dirname $realpath`/file.real --magic-file /opt/poky/1.7.1/sysroots/x86_64-pokysdk-linux/usr/share/misc/magic.mgc "$@" (From OE-Core rev: 49ab89eb9f83388e99069a4b53bdc4cba22bb6f3) Signed-off-by: Javier Viguera <javier.viguera@digi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Review edits to the AUTOREV variable.Scott Rifenbark2015-02-171-6/+8
| | | | | | | | | | | Fixes [YOCTO #7306] Some review updates to have better wording. (From yocto-docs rev: 6f2d10c87128934958295111d10e038689fd94d3) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updates to AUTOREV and SRCREV variable descriptionsScott Rifenbark2015-02-171-7/+33
| | | | | | | | | | | | | | | | | | | Fixes [YOCTO #7306] Added an example for when the user tries to inherit the most recent version of software through use of the SRCREV variable. When using SRCREV = "${AUTOREV}" PV does not always get ${SRCPV}, which it need in order to fetch the latest software. I added a clarifying example to explain this situation. This commit also has a small change to fix a broken link to EXTERNAL_TOOLCHAIN. We do not documentat that variable so I removed the link. (From yocto-docs rev: 82f66a7193d0e40ffd65547223d4d9b10fdcf9bd) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toaster-manual: 2nd draft for review.Scott Rifenbark2015-02-173-290/+374
| | | | | | | | | | | Fixes [YOCTO #6901] This is the 2nd review draft of the manual. (From yocto-docs rev: 9f541e4421e0e74e59e3b3da1896b6c1254daf08) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* adt-manual, ref-manual: Detail on using an external toolchain.Scott Rifenbark2015-02-172-16/+61
| | | | | | | | | | | | | | | | | | | Fixes [YOCTO #4907] I created a new section in the toolchain chapter of the adt-manual called "optionally Using an External Toolchain". This provides some fundamental information for the user that wants to use an external toolchain. Additionally, it references Mentor Graphics Sourcery toolchain as an example. In the ref-manual, I updated the TCMODE variable description to better integrate the MGC Sourcery toolchain as the overriding example. (From yocto-docs rev: 51e9c3b88f7e5a16da2aa101589b0f2612fff11d) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added 'debug-tweaks' fragmentation.Scott Rifenbark2015-02-172-5/+30
| | | | | | | | | | | | | | | The image feature 'debug-tweaks' has been fragmented into three separate areas of functionality that deals with handling empty passwords and post-installation logging. I updated the list of image features appropriately and the description of 'debug-tweaks' in the EXTRA_IMAGE_FEATURES variable. Fixes [YOCTO #5344] (From yocto-docs rev: ce0ab20472a75049298287cd05109f6e091b80bd) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updates to some variables per review comments.Scott Rifenbark2015-02-171-4/+30
| | | | | | | | | | | | | | | Updates to the following: BUILD_ARCH SOURCE_MIRROR_FETCH TARGET_PREFIX SDK_PREFIX SDK_SYS (I added this one new). (From yocto-docs rev: ad5f9b56dc912783b415b30604456bd5071f9721) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>