summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools
AgeCommit message (Collapse)AuthorFiles
2012-09-24binutils-2.22: Disable recent gold backports from 2.22 branchKhem Raj2
This patch has been causing some regressions on gold. e.g. systemd based images segfault and uclibc based images dont boot. There has been few other reports on the mailing list. Considering this lets withdraw this patch. Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-24qemu-native: fix build on hosts without libX11 installedMartin Jansa1
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-24autotools: Remove special handling for autoconf* and automake*Phil Blundell4
For reasons that are now shrouded in obscurity, autotools.bbclass has long contained a special heuristic to avoid attempting to run autoreconf when building autoconf or automake themselves. However, the wildcard test against PN which is used there is problematic when trying to build another package whose name happens to start with "autoconf", and in any case it is silly to do this test at runtime for every package. The individual recipes for autoconf and automake can just as easily suppress the behaviour that they don't want by providing a custom do_configure() method which just runs configure. Signed-off-by: Phil Blundell <pb@pbcl.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-24adt-installer: add sudo when relocating symlinksLaurentiu Palcu1
This is needed if installation is done in a directory that needs root privileges. Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-21gcc: Use 4.7.2 release tarballKhem Raj4
This avoids the SVN or git fetcher issues for gcc and the tar is mirrored around the world so it will not be slow Fixes [YOCTO #2908] Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-21bitbake.conf/gcc-common.inc: Fix STAMPCLEAN expressionRichard Purdie1
The globs used for STAMPCLEAN were too greedy matching gcc-cross-initial stamps for gcc-cross for example. This patch resolves that problem making the assumption that PV starts with something numeric. This assumption should hold in most cases and has a better failure case that the current situation. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-21SDK: relocate symlinks tooLaurentiu Palcu1
The directory usr/libexec/ in the SDK sysroot contains the default symlinks to the toolchain binaries and these, too, need to point to the correct toolchain path. [YOCTO #3090] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-21adt-installer: ensure directory exists before copying/removingLaurentiu Palcu1
If the installation is done in a directory which already contains a valid installation, opkg will not install anything and the moving the contents of /install/dir/opt/poky/1.2 (for example) to /install/dir will throw some errors. However, the install directory will not be affected. This patch will ensure that the /install/dir/opt/poky/1.2 exists. Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-21SDK: fix installation into symlinked directoriesLaurentiu Palcu2
The SDK installation scripts should not canonicalize symlinked directories because the entire relocation would be done to the directory to which the symlink points. Instead, if the installation is a symlink, use that path to relocate the binaries. For example, if we have the following symlink: /opt/sdk -> ~/my/test/sdk the binaries will be relocated to /opt/sdk not ~/my/test/sdk as it is done now. [YOCTO #3102] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-21adt-installer: fix package installation issueLaurentiu Palcu1
When the cross canadian toolchains are installed, for different architectures, they might contain common files. This leads to installation failures since the opkg, by default, does not overwrite files. This issue happens, for example, for binutils packages (that contain the same locale files) or gdb (which installs some syscalls xml files). The locale files could be removed from the binutils cross-canadian package but we cannot do the same for the syscalls GDB files which are used by GDB to display user friendly names for the syscall numbers. Hence, the best solution is to force opkg to overwrite these files. [YOCTO #3109] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-21intltool: include intltool.m4 and add missing rdependsConstantin Musca2
- include /usr/share/aclocal/intltool.m4 into the intltool package (the files from intltool-dev must be included into the main package, as intltool is a development tool) - add missing rdepends: gettext-dev, libxml-parser-perl [YOCTO #2597] Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-21opkg svn: respect to the arch priorityRobert Yang2
This is for fixing the problem: 1) bitbake core-image-sato-sdk with MACHINE=qemux86 2) bitbake core-image-sato with with MACHINE=crownbay The qemux86's PACKAGE_ARCH is i586, the crownbay's is core2, but several i586 packages will be installed into crownbay's rootfs though there are core2 packages. For example, there are: xserver-xorg*_1.11.2-r7_i586.ipk xserver-xorg*_1.9.3-r1_core2.ipk The crownbay.conf says: PREFERRED_VERSION_xserver-xorg ?= "1.9.3" What the crownbay's image needs is xserver-xorg*_1.9.3-r1_core2.ipk, but the xserver-xorg*_1.11.2-r7_i586.ipk will be installed, this is incorrect. This is caused by opkg's selecting mechanism: when more than one candidate is found, it will use the higher version one and ignore the arch priority. we have several conf files which set the PREFERRED_VERSION_pkg = "..." , but there is no such a mechanism which can let us tell the opkg to install the preferred version. When the preferred version is higher, this is OK, but if the preferred version is lower, there would be problems: 1) Most of the packages are core2 in the image, but several of them are i586, though we have built the core2 ones, this seems strange. 2) What's worse is that the image may not work since the preferred version pkg is not installed. We have set the arch priority clearly in the opkg.conf, I think that respect to the arch priority is reasonable during the image generation. Add the "--select-higher-version" option to let the user have another choice, the default is no. [YOCTO #2575] Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-21gdb: Upgrade 7.4 -> 7.5Khem Raj8
This is a simple upgrade. Dropping the unneeded patches and adding --disable-werror to configure since thats is what one of the patch was doing which was dropped. Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-21opkg-nogpg: drop SRCREVMartin Jansa1
* use SRCREV from opkg_svn.bb, because with 596 patches we have won't apply Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-21opkg: add patch to fix SIGSEGV when printing status fileMartin Jansa2
* it was triggered by c02364f36e228835ea5d7fd4e1d347fd451f8544 when new package had 2 entries in Provides and old version just 1 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-21opkg: replace local patches with git patches submitted upstreamMartin Jansa8
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-20opkg 0.1.8: remove it since it doesn't workRobert Yang3
Remove opkg_0.1.8.bb and the related files since it doesn't work: - It doesn't support the "--force_postinstall" option which is used by package_ipk.bbclass. - It still doesn't work after remove the "--force_postinstall" option, it can't install the packages in complementary_pkgs.txt. [YOCTO #3136] Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-20rpm 5.4.9: DEPENDS on bison-nativeRobert Yang1
The rpm should depend on bison-native, otherwise errors when "bitbake rpm-native" in a fresh build: | make[4]: Entering directory `/path/to/rpm-native-5.4.9-r46/rpm-5.4.9/syck/lib' | bison -d -t -v -p syck -o gram.c gram.y | make[4]: bison: Command not found Basically, both the rpm-native and rpm should depend on bison-native, but don't need depend on bison, but it seems that it isn't necessary to add another depend line: DEPENDS_virtclass-native = "libpcre-native ... bison-native" So just add it to the DEPENDS. [YOCTO #3123] Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-20bitbake.conf/gcc: Add clean masks for stamp filesRichard Purdie1
This takes advantage of new bitbake functionality to clean up stale stamp files when creating new stamp files. [YOCTO #2961] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-18recipes: bump PR to rebuild after libffi5 -> libffi6Martin Jansa4
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-14opkg: Fix package dependency issue for preinstsRichard Purdie2
When processing dependencies, we need to look for both the SW_INSTALL and SW_UNKNOWN states. If we don't do this, dependencies can be missed and preinst scripts can run before dependencies are all installed. This leads to package installation errors for packages like dbus-1 and associated user permission errors. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-14binutils-2.22: Backport PR fixes from 2.22 branchKhem Raj15
These are fixes mainly cherrypicks for mips/ppc/x86 mainly fixing PRs in ld and gold Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-14pseudo_1.4.1.bb: update to pseudo 1.4.1, fixing 32-bit host problemsPeter Seebach3
There were a number of cases where pseudo used plain old stat() to get dev/inode data for files; on 32-bit hosts, this could fail if the files were over 2GB, causing pseudo to prevent removing of large files. This is fixed in 1.4.1. Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-14git: define NO_PYTHON=1 to stop git requiring python as a dependancyJack Mitchell1
Git requires python by default as an included script to link git to perforce is written in Python. Define NO_PYTHON to stop the script being included and thus remove the dependancy on Python. Signed-off-by: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-14valgrind_3.7.0.bb: fix missing leading space on _appendMatthew McClintock1
Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-12valgrind: fix debug info reading error when do memcheck on ppc targetsZhenhua Luo2
following is the error message: --2263-- WARNING: Serious error when reading debug info --2263-- When reading debug info from /lib/ld-2.13.so: --2263-- Can't make sense of .got section mapping --2263-- WARNING: Serious error when reading debug info --2263-- When reading debug info from /home/root/lzh: --2263-- Can't make sense of .data section mapping --2263-- WARNING: Serious error when reading debug info --2263-- When reading debug info from /usr/lib/valgrind/vgpreload_core-ppc32-linux.so: --2263-- Can't make sense of .data section mapping --2263-- WARNING: Serious error when reading debug info --2263-- When reading debug info from /usr/lib/valgrind/vgpreload_memcheck-ppc32-linux.so: --2263-- Can't make sense of .data section mapping --2263-- WARNING: Serious error when reading debug info --2263-- When reading debug info from /lib/libc-2.13.so: --2263-- Can't make sense of .data section mapping Signed-off-by: Zhenhua Luo <b19537@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-12nativesdk-qemu: fix SDK relocation issueLaurentiu Palcu2
User mode emulation binaries are linked using a local linker script. The nativesdk ones were not used and the resulting binaries did not have the interp section resized. Hence, those binaries could not be relocated. [YOCTO #3083] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-12gcc-4.7: Backport libgcc fixes to appease the new build sequenceKhem Raj3
This makes the libgcc builds identical when done with gcc-cross-initial or final gcc-cross. Since eglibc only sees gcc-cross-initial it is important that the final libgcc that appears on root file system is same as the one against which eglibc was built. Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-12gcc-4.7: Fix build for armv4/EABI and ppc/OsKhem Raj3
arm patch is a forward port from OE/classic ppc patch should help in building images with Os Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-12perl-native: PROVIDE libmodule-build-perl-native for consistency with ↵Phil Blundell1
non-native perl This module is, apparently, included in the standard perl distribution since 5.10.1 or so. The regular perl recipe has had this PROVIDES for a while but it seems to have been overlooked in the native version. Signed-off-by: Phil Blundell <pb@pbcl.net> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-10qemu-git: Move to tip of git past 1.2 releaseKhem Raj2
There are a lot of armv7 and sh4 fixes that its worth moving to latest version. The patch forward porting can happen later. Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-10qemu: Update from 0.15 to 1.2Khem Raj15
Forward port the patches which were not applied upstream Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-10perl: package modules Pod-Html and Tie-Hash-NamedCaptureKang Kai1
Package modules Pod-Html and Tie-Hash-NamedCapture. Without module Tie::Hash::NameCapture.pm, call "use English;" will fail. Module Pod::Html is required by LSB perl test 4.1 case all/tst_perlModPresent.pl 1. [Yocto #3031] Signed-off-by: Kang Kai <kai.kang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-10autoconf: use --warning=cross only if supportedConstantin Musca2
Adapt autoconf to pass --warning=cross to automake only if supported. [YOCTO #842] Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-10kconfig-frontends: Create symlinks for conf and mconfKhem Raj1
eglibc calls out mconf and conf directly so lets create symlinks to point to their kconfig- counterparts Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-07rsync: Add md5sum and sha256sum for the rsync_2.6.9Martin Ertsaas1
rsync_2.6.9 is the only rsync recipe in openembedded without GPLv3 license, but it lacked the checksums for the fetcher. Signed-off-by: Martin Ertsaas <mertsas@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-06gcc-cross-initial: Reinstate limits.h generation fixRichard Purdie1
The removal of gcc-cross-intermediate inadvertently reintroduced a problem with the limits.h file being incorrectly/inconsistently generated. http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=b0faebd1f07e1616004bd19664395932e7c2c48f reverted part of: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=c8815d2f21849deb9359706f54dc71490773415e This reintroduces the protected sysroot ensuring the limits.h file is always correctly generated. To reproduce the bug, build gcc-cross, then rebuild gcc-cross-initial and it will reference the limits.h file from gcc-cross in the sysroot. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-05adt-installer: Allow changing YOCTOADT_REPOElizabeth Flanagan2
YOCTOADT_REPO within adt-installer.conf was hardcoded to http://adtrepo.yoctoproject.org/${SDK_VERSION} This allows it to be overriden in local.conf by setting ADTREPO = "http://adtrepo.yoctoproject.org/${SDK_VERSION}" I'm also fixing a bad rm in do_populate_adt. The file name that is being rm'd is wrong. Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-05python-pygtk: Upgrade to 2.24Saul Wold2
This is needed for the build appliance and Hob also Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-04packagegroup-*: add RREPLACES/RCONFLICTSPaul Eggleton1
These are needed to support upgrading from task-* to packagegroup-* within existing target images at runtime. Note: these settings will very likely be moved out to a separate inc file at some point in the future. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-03qemu-config: turn into distcc-config and a package groupPaul Eggleton3
* Create a new packagegroup-core-device-devel which pulls in everything that qemu-config used to, with the exception of anjuta-remote-run - this is unlikely to be widely used * Move the remainder of qemu-config to distcc-config and allow DISTCC_HOSTS to be configured via a variable of the same name * Use SUMMARY instead of DESCRIPTION for single-line description since DESCRIPTION is defaulted from SUMMARY if not set Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-03qemu-config: split out export of root via NFS to its own recipePaul Eggleton2
This need not be specific to qemu machines, allow it to be used elsewhere in isolation. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-03qemu-config: split out anjuta-remote-runPaul Eggleton2
Given that support for Anjuta is unlikely to be needed by everyone and is by no means specific to qemu, split it out to a separate recipe. The following changes were made in the process: Also depend on dbus instead of dbus-x11 since dbus-launch is now back in he main dbus package Part of the fix for [YOCTO #1690]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-03automake: upgrade to 1.12.3Constantin Musca1
Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-02elfutils: Fix build on uclibcKhem Raj1
It depends on libintl so add virtual/libintl to DEPENDS simplify the overridden statements Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-02dpkg: upgrade to 1.16.8Constantin Musca14
autofoo.patch: removed - the patch is not used check_version: adapted to the new version - adapt the linux-wrs kernel version, which has character '_' - remove the first-char-digit-check (as the 1.15.8.5 version does) dpkg-deb-avoid-fflush.patch: removed - the patch is included in the new version fix-timestamps.patch: added - the lutimes function doesn't work properly for all systems ignore_extra_fields.patch: adapted to the new version nochroot.patch: removed - the patch is not used noman.patch: adapted to the new version noupdalt.patch: removed - the patch is not used perllibdir.patch: removed - in the new version PERL_LIBDIR will be set only if empty preinst.patch: adapted to new version removed-tar-no-timestamp.patch: added - the busybox-1.19.4 tar utility doesn't support --warning=no-timestamp Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
2012-08-31perl: Fix various nativesdk build issuesRichard Purdie1
The config.sh lists -fstack-protector but this isn't in LDFLAGS. This can result in perl compilation failures due to the mismatch. Adding the flag to LDFLAGS solves makes all the flags consistent and avoids build failures from missing symbols. It was also found that the path substitutions made by the sed statement can conflict with each other and you can end up with $prefix$prefix type expressions in config.sh-X which can break the build in unusual ways. This patch anchors the expressions to ensure only true matches are replaced. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-08-31nativesdk: Switch to using nativesdk as a prefix, not a suffixRichard Purdie17
As discussed on the mailing lists, using a suffix to package names is hard and has lead to many recipes having to do PKGSUFFIX games. Its looking extremely hard to scale nativesdk much further without hacking many recipes. By comparison, using a prefix like multilib does works much better and doesn't involve "hacking" as many recipes. This change converts nativesdk to use a prefix using the existing multilib infrastructure. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-08-29intltool: Add Upstream-Status and Signed-off-by to remove-xml-check.patchFlorin Sarbu1
Signed-off-by: Florin Sarbu <florin.sarbu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-08-28runqemu-export-rootfs and friends: don't put pseudo db in target fsPeter Seebach1
In a few places, we have scripts which use <rootfs>/var/pseudo for the pseudo state directory controlling a given filesystem. This seems possibly risky because it means that stuff running under qemu or whatnot could wipe out the data being used to handle that rootfs. Move this to: <rootfs>/../$(basename_rootfs).pseudo_state to avoid problems. This also solves at least one case (not directly hit by yocto's tree) wherein you could end up trying to remove a rootfs while pseudo was using a database inside that rootfs, and thus the remove would fail. Signed-off-by: Peter Seebach <peter.seebach@windriver.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-23 11:18:26 +0000