aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2013-07-23binutils: fix build with recent texinfo (5.1)dannyEric Bénard
Signed-off-by: Eric Bénard <eric@eukrea.com>
2013-07-23eglibc: fix build with recent texinfo (5.1)Eric Bénard
Signed-off-by: Eric Bénard <eric@eukrea.com>
2013-07-23gcc: add patch to disable texinfo when texinfo is 5.0 or newerMartin Jansa
* this is needed only for 4.7 series, newer works fine with texinfo-5* [YOCTO #3947] Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-25classes/package_rpm: avoid bash being pulled in unnecessarilyPaul Eggleton
The initial installation step for base-passwd, base-files and shadow will pull in bash if any of these packages depend on /bin/sh and a bash package has been built, which is undesirable if you are using busybox; so force the early installation of one or the other depending on which is going to be installed in the second step. Note: this fix is not needed for 1.4 (dylan) and newer, since there we use smart to construct the root filesystem without this initial step. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2013-06-14site/common: deactivate a python cross-compilation runtime checkLukas Bulwahn
In configure there is a runtime check to determine buggy getaddrinfo and as we are cross-compiling this check goes wrong. If ipv6 is enabled in python, the failed test is reported as fatal error with the message Fatal: You must get working getaddrinfo() function. Setting ac_cv_buggy_getaddrinfo=no deactivates the runtime check and allows to compile python with ipv6 enabled. This commit was cherry-picked from commit 66db85262bef08802af30964b415bff349cfba69 into the danny branch. The original commit was in turn derived from the commit 700b75e7661062aa93cf81205b78c8bf7609922d in the Classic OpenEmbedded Development Tree. Fixes: bug #4557 Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Dimas Abreu Dutra <dimasadutra@gmail.com>
2013-05-29grub-efi-native: fix build on modern distributions without gets()Koen Kooi
O irony: the grub2/gnulib nag macro that says "don't use gets, use fgets" breaks the build if you're using a recent (e)glibc release that has gets removed. Fedora already #if 0's the check in grub, so I stole their patch. (From OE-Core rev: 261e377b08388a288ee521a3629877b89e18e42b) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-16Revert "initramfs-live-install*: fix the "install" boot option"Ross Burton
This patch causes install to fail because /etc/mtab doesn't exist, so revert it for now until the root problem is fixed. [ YOCTO #4501 ] This reverts commit 2f5d41f94c53aaf606de66891c37de0dbd86f54b. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-09powertop: inherit gettextRoss Burton
powertop uses gettext during config time and at build time to generate the messages, so really should inherit gettext. [YOCTO #4470] Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-08qemu-native: fix DSO linkingTrevor Woerner
I noticed this issue trying to build using the Danny branch on what is currently the most recent openSuSE (12.3). It appears to be similar to the fedora DSO linking issue: https://fedoraproject.org/wiki/UnderstandingDSOLinkChange. Upstream-status: Inappropriate [OE Specific] Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2013-05-08qemux86: disable paravirt guest in linux 3.4, causes test failuresRoss Burton
The shutdown sanity test that we previously saw on qemux86-64 in 2.6.37 have started to re-appear reproducably on qemux86 in 3.4 in the Danny series. Until this can be root-caused and fixed in the kernel, disable paravirtualisation across all kernels and all qemu machines. [ YOCTO #4196 ] Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Conflicts: meta/recipes-kernel/linux/linux-yocto_3.4.bb
2013-05-07sanity.bbclass: Ensure tmpdir exists when running the checkRichard Purdie
This avoids tracebacks from bitbake if the directory doesn't already exist. [YOCTO #3640] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-03udev-extraconf: Add -o silent to auto mount for mount.util-linuxSaul Wold
This will silence some of the noisy output from mount.util-linux and the kernel when trying to automount filesystems or devices. Busybox does not accept the silent option, it uses a loud option instead. [YOCTO #3935] Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-30ncurses.inc: Fix display corruption and add fallback for sstate compiled pathsJason Wessel
CQID: WIND00402979 Display corruption was occurring on 64 bit hosts using menuconfig for the kernel and busybox with the ncurses-native or ncurses-nativesdk because the configure arguments were not sufficient vs the expected use from the upstream source. Also changed in this commit is to provide a fallback to the hard compiled paths for the terminfo and termcap. Eventually this needs to be fixed another way if we want a truly portable SDK because any SDK that is relocated or native binaries pulled out of the sstate can end up referencing terminfo files that no longer are in the same location. Because the host system has terminfo files that ncurses will happily use we might as well have a fall back to buy some time for a better fix, vs having thing just not work occasionally when using sstate. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-30lib/oe/classextend.py: avoid extending any kernel packagePaul Eggleton
For multilib and other uses of classextend, we don't want any dependencies on kernel packages to be extended since there should only be one kernel variant. Fixes [YOCTO #2918] (where kernel-dev was being extended.) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-30classextend.py: use explode_dep_versions2 in order to preserve versions tooConstantin Musca
Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-04-30multilib: skip packages that provide virtual/kernelBruce Ashfield
Rather than keying on recipes that inherit kernel.bbclass, we should be checking for providers of virtual/kernel when skipping kernel recipes in multlib builds. Not all providers of virtual/kernel inherit kernel.bbclass (notably linux-dummy), so checking on the provider is a more complete check. We need to be sure to check for inheritance of module-base as well, this allows for packages that provides modules to avoid the multilib renaming. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-30lib/oe/classextend: Ensure we don't extend expressions more than onceRichard Purdie
We could end up with MLPREFIX being prepended to variables like PACKAGE_DYNAMIC. This patch avoids the problem and unbreaks builds. [YOCTO #3389] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-29multilib/clsextend: Improve handling of regexps in PACKAGES_DYNAMICRichard Purdie
Now that PACKAGES_DYNAMIC is more standardised, starting with ^ anchors, the variable manipulations performed by clsextend for multilib don't work. This patch at least improves it to hack around the problem and enable mulitlib builds to work again. If this code doesn't do the right thing, the recipe is free to override the variable with the correct multilib case. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-29perl: fix CVE-2013-1667Ross Burton
From http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-1667: "The rehash mechanism in Perl 5.8.2 through 5.16.x allows context-dependent attackers to cause a denial of service (memory consumption and crash) via a crafted hash key." Patch taken from upstream git. Signed-off-by: Ross Burton <ross.burton@intel.com>
2013-04-29perl: fix CVE-2012-6329Ross Burton
From http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-6329: "The _compile function in Maketext.pm in the Locale::Maketext implementation in Perl before 5.17.7 does not properly handle backslashes and fully qualified method names during compilation of bracket notation, which allows context-dependent attackers to execute arbitrary commands via crafted input to an application." Patches taken from upstream git. Signed-off-by: Ross Burton <ross.burton@intel.com>
2013-04-29openssh: fix CVE-2010-5107Ross Burton
From http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-5107: "The default configuration of OpenSSH through 6.1 enforces a fixed time limit between establishing a TCP connection and completing a login, which makes it easier for remote attackers to cause a denial of service (connection-slot exhaustion) by periodically making many new TCP connections." Integrate patches from upstream to enable "random early drop" by default./ Signed-off-by: Ross Burton <ross.burton@intel.com>
2013-04-29gnupg: integrate fix for CVE-2012-6085Ross Burton
From http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-6085: "The read_block function in g10/import.c in GnuPG 1.4.x before 1.4.13 and 2.0.x through 2.0.19, when importing a key, allows remote attackers to corrupt the public keyring database or cause a denial of service (application crash) via a crafted length field of an OpenPGP packet." Patch taken from upstream git, which is identical in both branches. Signed-off-by: Ross Burton <ross.burton@intel.com>
2013-04-23qemuimagetest/scenario: Move dmesg to end of test runRichard Purdie
The dmesg test detects segfaults. This is useful information to have and if one occurs in one of the earlier tests, this can aid debugging. Move the dmesg test to the end of the list of tests so we gain the extra debug info in those cases. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23qemuimage-tests/sanity/boot: Increase timeoutRichard Purdie
As we've increased the parallelisation on the build servers, we've started to see core-image-minimal sanity test boot failures where the network never comes up. We don't see those failures for core-image-sato, its always minimal. Looking at the results, it can take ~100 seconds for the network to come up, even on the sato images if the machine has a high load. The timeout for the boot test is only 120 seconds compared to 400 on every other test. This change makes the timeout equal for all the tests at 400 seconds in the hope that the load on the autobuilder is causing the sanity tests to run slowly and hence triggering the false negatives. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23sanity/connman: when connman test fails, dump syslogRoss Burton
Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23qemuimage-testlib: add function to fetch the remote syslogRoss Burton
Add a new function to scp from the target, and another to fetch /var/log/messages and dump it to the console. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23qemuimage-testlib: silence some key warningsRoss Burton
Set StrictHostKeyChecking to no to silence the fingerprint warnings, and instead of creating a temporary file for the known hosts and then deleting it just use /dev/null. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23connman_test.sh: show all processes when dumping psRoss Burton
We know the grep failed because the error case is being executed, so don't do the grep again when attempting to help diagnose the problem, as seeing the full process list might be useful. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23qemuimage-testlib-pythonhelper: Fix process mixupsRichard Purdie
runqemu-internal runs "ldd qemu-system xxx" and the detection code was returning this as the PID of qemu. This patch improves the detection code to avoid this problem, fixing certain race type failures on the autobuilder. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23scripts/qemuimage-testlib: Dump extra info if the network doesn't come upRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23qemuimage-testlib: Fix quoting issueRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23qemuimage-testlib: Use ww option to ps to ensure command output isn't truncatedRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23qemuimage-testlib: Increase qemu startup timeoutsRichard Purdie
We are seeing timeouts on the autobuilder where qemu does start but the script doesn't appear to be able to detect it in time. This patch increases the timeouts since there seems little harm in doing so. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23initramfs-live-install*: fix the "install" boot optionNitin A Kamble
The install boot option was giving the following error when one tried to install the live image on a permanent storage of a BSP. cat: write error Invalid argument Installation image failed sh: can't access tty: job control turned off Further digging into the issue, found out that the install script was trying to do this: cat /proc/mounts > /etc/mtab And in the base-files recipe the /etc/mtab is made soft link to /proc/mounts. So the cat command was failing to write on /etc/mtab. As the contents of the /proc/mounts is already reflected in the /etc/mtab file due to the symlink-ing, there is no need for this step to recreate /etc/mtab in the install script. So just removing this unnecessary step, which solves the install issue of the live images. Fixes this bug: [YOCTO #4229] Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23libproxy: add dependency on glib-2.0Alexandru DAMIAN
libproxy uses glib-2.0, but the depends is missing Fixes intermittent build errors. Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23bluez4: add readline dependencyAlexandru DAMIAN
bluez4 uses readline to be build, but the dependency is not listed This is listed in the configuration log. So we add it. Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23linux-dtb: fix whitespace in bash functionsChase Maupin
* Fix the whitespace in the base functions to use TAB instead of spaces. This is to address feedback from: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Chase Maupin <Chase.Maupin@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23linux-dtb: Add simple DTB symlinks for devicetreeChase Maupin
* This is similar to the symlinks provided for the kernel image in the /boot directory of a file system. The goal is to have simply named symlinks in /boot that mirror the device tree name in the kernel sources. This is so that programs like U-Boot can easily find the default device tree binary in the /boot directory and use that when booting the kernel. * Use update-alternatives to handle proper creation and removal of the symlinks. Signed-off-by: Chase Maupin <Chase.Maupin@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23kernel bbclass: return to original directory in do_deployChase Maupin
* During the base kernel_do_deploy function the directory is changed to DEPLOYDIR in order to do some cleanup and symlinking. However, the directory is not changed back to the original starting directory ${S} at the end. For append functions this means that the starting directory is not ${S} as expected but instead ${DEPLOYDIR}. For functions like the do_deploy_append in recipes-kernel/linux/linux-dtb.inc there is an assumption that you are still in the source directory and not the DEPLOYDIR. Without this change the .dtb files are not copied because the check for the existence of ${DTS_FILE} which is a relative path from the ${S} directory fails. This means that the .dtb files are not copied into the deploy directory and subsequently the deploy/images directory. In the log.do_deploy file you will see lines like: Warning: arch/arm/boot/dts/xxxxx.dts is not available! Signed-off-by: Chase Maupin <Chase.Maupin@ti.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-04-23relocate_sdk.py: allow relocate_sdk.py to work with python 2.4.xJason Wessel
Avoid the chicken / egg problem of an SDK that provides a working python but requires that version of python to extract itself. The RHEL 5.x systems and some other enterprise Linux systems ship with python 2.4.x as the default python. We need to at least be able to extract work executables even if we never use the the host provided python again. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23relocate_sdk.py: Fix corruption of sdk binariesJason Wessel
There are two cases of corruption that the relocate_sdk.py was not correctly dealing with. 1) SDK Extras should be left alone Extra external binaries included in an SDK that were linked against the host's version of /usr/lib/ld-so.so should not get a relocation applied. In the case that was discovered these were LSB compliant binaries that already worked on many hosts. 2) If the interp section is too small generate an error In the case of the qemu user code, it was using its own .ld file to link the executables which overrides the default in the nativesdk binutils. This generated host executables which had a interp section that was too small to relocate. Now the relocate_sdk.py will print an error and continue on such that the error can be fixed by a developer without having to do the difficult task of debugging why it is crashing or not loading correctly. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-23populate_sdk_base.bbclass:fix toolchain relocation issuesHongxu Jia
When run "autoreconf" in toolchain, there is an error if the host's perl's version is not the same as the one in the SDK, the error says that the executable perl mismatches the perl lib's version. This is because most of the autotools' scripts use the "#!/usr/bin/perl -w" which is host perl, but the gnu-configize uses "#! /usr/bin/env perl" which invokes the perl wrapper in the SDK, and the wrapper will set the PERL5LIB to the SDK which causes the mismatch. We can make all the perl scripts to use the host perl or the SDK perl to fix this problem. Cherry-pick commit aeb53bd78991af9fbb60d64176ec864cfc2ddbb9 [YOCTO #3984] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
2013-04-23perl_5.14.2.bb:fix toolchain relocation issuesHongxu Jia
1, Use create_wrapper to create perl wrapper in the SDK. 2, Add perl.real to perl-nativesdk package. Cherry-pick commit 820a64bfb7b27e3aaa3b8c0228c4ed70b64c03d1 [YOCTO #3984] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
2013-04-23populate_sdk_base: tarball installer: SDK overwrite warningHongxu Jia
This patch contains two fixes: * if the user wants to install the SDK in a directory that already contains a SDK for the same architecture, a warning will be shown; * when the symbolic links are relocated use -n option. Otherwise, symbolic links to existing directories will be created in the directory itself; Cherry-pick commit b751ec137d0228b40a90e9e32b24f5cb5732225b [YOCTO #3401] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
2013-04-23nativesdk-ncurses 5.9: fix files were installed but not shippedHongxu Jia
There is an warning: $ bitbake nativesdk-ncurses WARNING: QA Issue: nativesdk-ncurses: Files/directories were installed but not shipped /opt/poky/1.3+snapshot/sysroots/i686-pokysdk-linux/usr/bin/clear.ncurses /opt/poky/1.3+snapshot/sysroots/i686-pokysdk-linux/usr/bin/reset.ncurses NOTE: Tasks Summary: Attempted 533 tasks of which 521 didn't need to be rerun and all succeeded. And there is no clear or reset tool in the SDK. This is caused by: ALTERNATIVE_ncurses-tools = "clear reset" It creates clear.ncurses and reset.ncurses which are used for avoiding the conflicts with the target busybox, but SDK doesn't need them since there is no nativesdk-busybox (then no conflicts), so: ALTERNATIVE_ncurses-tools_class-target = "clear reset" will fix the problem. Cherry-pick commit dfc39d7bd5a9ad803d7c44b21811881515f7de02 [YOCTO #3325] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
2013-04-23automake_1.12.3.bb: update dependenciesHongxu Jia
Remove the RDEPENDS for nativesdk because the nativesdk-automake also needs perl modules. Add dependencies perl-module-thread-queue and perl-module-threads. Remove redundant dependencies that they are already required by autoconf and autoconf is required by automake. In this removed list, "-->" present "required by": perl-module-cwd --> perl-module-file-path --> autoconf perl-module-dynaloader --> perl-module-xsloader --> perl-module-fcntl --> perl-module-file-stat --> autoconf perl-module-exporter-heavy --> perl-module-exporter --> autoconf perl-module-constant --> autoconf perl-module-errno --> autoconf perl-module-file-basename --> autoconf perl-module-file-compare --> autoconf perl-module-file-copy --> autoconf perl-module-file-glob --> autoconf perl-module-file-spec-unix --> perl-module-file-spec --> perl-module-io-file --> autoconf perl-module-file-stat --> autoconf perl-module-getopt-long --> autoconf perl-module-io --> perl-module-IO-handle --> perl-module-IO-seekable --> perl-module-io-file --> autoconf perl-module-io-file --> autoconf perl-module-posix --> autoconf Bump up PR. Cherry-pick commit d93898b2c530681362e42d1b0477fa593a625046 Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
2013-04-23perl_5.14.2.bb:fix errors if configure is reattemptedHongxu Jia
If configure of perl is reattempted it currently fails as it tries to edit files outside ${S}. Chaging from ${WORKDIR} to ${S} avoids this issue and allows rebuilds to work. Cherry-pick commit f2f0a1aa489f9e6e4414fa758d3dd09a950a106c Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
2013-04-23generate-sh.patch:fix autoreconf run failed on gmae-toolchainHongxu Jia
The perl shared libraries did not have RPATHs set and that made autoreconf fail when using the SDK. The LDDLFLAGS environment variable was already exported in the recipe but was not used when generating the config.sh. Cherry-pick commit df1a1dcb6d95a4aa558019530445373537c4efdd [YOCTO #3338] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
2013-04-23perl_5.14.2.bb:fix autoreconf run failed on gmae-toolchainHongxu Jia
File warnings/register.pm has been moved to package perl, update RPROVIDES_perl to provides perl-module-warnings-register for backward compatibility. Update populate_package script for: 1 Way to deal directory 'Module/' is not right, it creates packages whose names end with '-pm'. Update to drop these packages. 2 Deal directory 'auto/' to put same name module file(.pm) and library file(.so) into one package. That because .pm file requires the same name .so file at runtime. Cherry-pick commit dd65b82d24afcf3982f6fb93a6503c71fdf40dbf [Yocto #3338] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
2013-04-23perl_5.14.2.bb:Fix support strict/vars/config/warnings modulesHongxu Jia
With the move of the strict/vars/config/warnings modules to the main perl recipe, we need to RPROVIDE those modules to ensure that package dependencies on those modules continue to work correctly. Cherry-pick commit 072a6d352f55bbe481b04db02aa6d9cde7d90057 Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>