summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFiles
2011-08-15cairo: only use x11 if selected in DISTRO_FEATURESPhil Blundell1
This makes it possible to build cairo-using apps without X11. Signed-off-by: Phil Blundell <philb@gnu.org>
2011-08-15libx11: skip self if x11 not in DISTRO_FEATURESPhil Blundell1
This stops (most) x11 packages leaking into a non-x11 distro by mistake. Signed-off-by: Phil Blundell <philb@gnu.org>
2011-08-15pixman: remove spurious dependency on libx11Phil Blundell1
Nothing in pixman actually uses libx11, so no need to DEPEND on it. Signed-off-by: Phil Blundell <philb@gnu.org>
2011-08-15intltool: Use nativeperl binary for PERL instead of 'perl'Khem Raj3
License is GPLv2 change it. Defining PERL for native intltool is not needed anymore Signed-off-by: Khem Raj <raj.khem@gmail.com>
2011-08-15qt4: delete unpackaged uic3 to avoid unpackaged file warningPaul Eggleton1
All the other utilities get deleted as they should not be packaged, delete this one as well. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2011-08-15qt4: package QML plugins and correct their install directoryPaul Eggleton3
QML components from Qt were installed to ${prefix} before and never got packaged. This is now fixed and QML components are now installed into ${libdir}/${QT_DIR_NAME}/imports and packaged into qt4-*-qml-plugins package. Additionally qmlviewer and the examples/demos are now dependent upon these plugins as needed. Originally based on OE commit 4adf97be8c5b5f71ad92095a19968af534baa9e2 by Simon Busch <morphis@gravedo.de> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2011-08-15qt4-native: restore build of uic3, qdbuscpp2xml and qdbusxml2cppPaul Eggleton1
These tools are required to build some external utilities (such as those found in KDE). We avoid building qdbus and qdbusviewer as these are not required. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2011-08-15qt4: replace qt4-tools-native with qt4-nativePaul Eggleton2
Installs native versions of the Qt libraries in addition to the tools, allowing compilation of external native tools that require Qt libs. PROVIDES qt4-tools-native so it should be a drop-in replacement. Developed with reference to the corresponding qt4-native changes in OE. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2011-08-15eglibc: Modify ldd script according to multilib config.Lianhao Lu4
Bug fixing [YOCTO #1236]. 1. Collect all the values for RTLDLIST for the current multilib configuration to modify the ldd scripts. 2. Collect all the values for KNOWN_INTERPRETER_NAMES for the current multilib configuration. Set the correct ld.so names for ldconfig to deal with the multilib configuration.
2011-08-15utils.bbclass/multilib.class: Added misc supporting functions.Lianhao Lu4
1. Added variable MULTILIB_VARIANTS to store all the instance variants for multilib extend. 2. Added function all_multilib_tune_values to collect the variable values for all multilib instance. 3. multilib bbclass handler will save the orignal value of all variables defined in MULTILIB_SAVE_VARNAME. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
2011-08-15valgrind: supporting on Linux kernel 3.xLin Tong2
The old valgrind package do not support for Linux kernel 3.x, only for kernel 2.4 and 2.6. Now adding the configuration to the configure.in file to support Linux kernel 3.0. This commit fixes the problem in valgrind [YOCTO #1129] Signed-off-by: Lin Tong <tong.lin@intel.com>
2011-08-15bluez4: Added new recipe 4.96 and removed 4.82 versionNoor Ahsan5
* Added new recipe 4.96 and removed 4.82 version and its files. Signed-off-by: Noor Ahsan <noor_ahsan@mentor.com>
2011-08-12rt-tests: use an explicit commit IDDarren Hart1
Using a tag, like v0.73, forces network access to resolve a commit ID. Use the corresponding commit ID in the recipe. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-08-12tune-ppce5500: Add a set of tune files for PowerPC e5500 coreKumar Gala2
The PPC e5500 is a 64-bit core so we add both a 32 and 64-bit set of tune files to allow for: * pure 32-bit build * pure 64-bit build * 32-bit base, 64-bit multilib * 64-bit base, 32-bit multilib Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
2011-08-12tune-ppc: Update to pass glibc configure option to get cpu specific supportKumar Gala2
We need --with-cpu based to glibc to get proper support on 603e & e500mc to pickup proper math libs to deal with sqrt. These core do not implement the fsqrt[s] instructions that the normal PPC math libs utilize. This causes use to not set AVAILTUNES specifically to the sub-arch only as we arent generically compatiable. Signed-off-by: Kumar Gala <galak@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-08-12recipes-rt: add a README documenting the contents of recipes-rtDarren Hart1
Document the non-obvious bits of using the recipes-rt recipes. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-08-12Move meta-rt recipes to oe-core (meta)Darren Hart6
Keeping the rt recipes in their own layer has led to maintenance issues, particularly with the linux-yocto-rt recipes. As these kernel types are part of the same linux-yocto source repository, it seems reasonable to include the rt kernel recipes alongside the standard recipes. A new recipes-rt directory for the other recipes provides adequate separation and eliminates the need for a separate layer. As there is no meta-rt/conf/layer.conf to force the kernel, users must now specify the rt kernel in their local.conf or in the machine.conf: PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt" The merging of the rt recipes into the core also eliminates complications with multiple layer dependencies for new BSP layers. Having to either separate RT BSPs from standard BSPs or force users to add meta-rt to bblayers even when not building an RT BSP (because the RT BSPs in the same layer would fail to parse without it) was sub-optimal at best. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-08-12meta-rt: default KMACHINE and SRCREV_machine to avoid parsing errorsDarren Hart1
Without a default KMACHINE and SRCREV_machine the git URL will fail to expand to something usable and we get a parsing error. This approach was also used in the non-rt version of this recipe. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-08-12meta-rt: add an -rt-sdk imageDarren Hart1
Add images including the SDK without the addition of the grapical environment or packages. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-08-12meta-rt: rename minimal-rt images to -rt, drop live imageDarren Hart1
Remove "minimal" from the image recipe names for -rt. Additional recipes types will be added (-rt-sdk for example) and there is no need to keep so many image type descriptors. Drop the -live image as it is now obsolete. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-08-12meta-rt: remove atom-pc support from the main layerDarren Hart1
meta-rt resides in oe-core, as such it should only support the qemu* machines. BSP layers should add support for specific hardware platforms. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-08-12meta-rt: add linux-yocto-rt_3.0 recipeDarren Hart1
Add the initial linux-yocto-rt_3.0 recipe. qemumips and qemuppc doesn't work quite yet, so they have been omitted from COMPATIBLE_MACHINE. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-08-12meta-rt: canonicalize directory structureDarren Hart3
Use the more standard recipes-*/*/*.bb layout. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-08-12meta-rt: rt-tests v0.73 instead of AUTOREVDarren Hart1
AUTOREV is handy is a development aid, but it really shouldn't be used as a default as it breaks the consistency and repeatability of a build. It also causes additional fetches which may not be desired or expected. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-08-12meta-rt: refresh linux-yocto-rt recipeDarren Hart2
Rename the recipe to match the linux-yocto recipe renames using the kernel version in the PV portion of the filename. Add the SRCREVs to the recipe as was done with the core linux-yocto recipes. Add qemux86 as it is also present in the linux-yocto-2.6.34.git repository. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-08-12package_rpm: Fix attemptonly and suggest packagesMark Hatle1
[YOCTO #1325] [YOCTO #1366] Packages that were in the PACKAGE_ATTEMPTONLY and SUGGESTS were not being properly found, which was causing image creation failures. In PACKAGE_ATTEMPTONLY, when an item was not found, it caused an error. This should have been a note, followed by skipping the package. The SUGGESTS processing was simply broken. It was using a non-existant function, due to an apparently typo. In addition to the above, the MLPREFIX processing was not being done properly, preventing multilib packages from working in this with PACKAGE_ATTEMPTONLY. (SUGGESTS doesn't need this as the names are munged when creating the packages.) Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2011-08-12xcb-proto: update based on changes to python.m4 in automakeKumar Gala5
1. We dont need the aclocal patch as this will be handled by automake 2. We need to update xcb-proto.pc.in to know about ${libdir} since we'll end up with something like: pythondir=${libdir}/python2.6/site-packages Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
2011-08-12automake: Update for python.m4 to respect libdirKumar Gala3
As we tweak libdir we need python libs that utilize configure to respect it setting. By updating the python.m4 template, when we regen automake files they will than respect the setting of libdir which is standard for any autotools based recipe. Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
2011-08-12init-install.sh: Fix make partition and make file system issuesMei Lei1
[YOCTO #1151] Change the offset from the beginning of the disk to aligne the blocks. In this script, we use mkfs.ext3 to create file system after partition, but we use mkpartfs to create file system repeatly, and get some warnings about choose another specific tools to create file system for reliability. So use mkpart instead of mkpartfs and only use mkfs.ext3 to create file system. Signed-off-by: Mei Lei <lei.mei@intel.com>
2011-08-12package_rpm.bbclass: Update the platform config and --targetMark Hatle1
When constructing the /etc/rpm/platform file, we need to ensure that the any, all, and noarch platforms will allow any "linux" variant to be installable, not just matching variants.. i.e. arm-oe-linux-gnueabi should be able to install noarch-oe-linux Also ensure that we pass the full canonical arch via the --target= parameter. This allows us to define the proper platform settings for all packages. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2011-08-12rpm: Fix the canonical arch --target processing and cleanupMark Hatle7
[YOCTO #1352] Fix the canonical arch --target processor to work with the way OE handles the GNU canonical arch. Also cleanup a number of files that are no longer used, and refactor the no-loop patch into the "no-loopmsg" patch. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2011-08-12linux-yocto: update SRCREVs for preempt-rt support + build fixesBruce Ashfield1
Updating the SRCREVs for linux-yocto to pickup a series of changes that were made to support the build/boot of preempt-rt on 3.0.x. 7782fc6 routerstationpro: remove CONFIG_PREEMPT* definitions b51300c meta/rt: sugarbay preempt-rt support 735711e meta/rt: common-pc[-64] preempt-rt no branch fix 53026bf meta/rt: jasperforest preempt-rt support 99bc260 meta/rt: fri2 preempt-rt support e746ab8 meta/rt: fishriver preempt-rt support fa1b73f meta/rt: emenlow preempt-rt support 1f686ab meta/rt: crownbay preempt-rt support 64a5069 meta/rt: arm-versatile-926ejs preempt-rt support 7f827a1 meta/rt: mti-malta32-be preempt-rt support 930a983 meta/rt: qemu-ppc32 preempt-rt support 367fc55 meta-rt: rsp preempt-rt support b8a62ea meta/rt: mpc8315 preempt-rt support b5f9daa meta/rt: beagleboard preempt-rt support 1e6e9eb meta/rt: use CONFIG_PREEMPT_RT_FULL for 3.0 kernels eb5a06b boot: move -Os patch to standard branch c692a23 meta/rt: remove explicit patch references 8a2ac6b meta/rt: updating to rt8 76b3679 meta: atom-pc update definition to re-use preempt-rt Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-08-12cross: also empty PACKAGES_DYNAMICChris Larson1
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2011-08-12package: allow setting a section for locale packagesChris Larson1
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2011-08-12package: include SECTION in the pkgdataChris Larson1
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2011-08-12sanity: shift the required utils into a variableChris Larson1
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2011-08-12nativesdk: inherit relocatableChris Larson1
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2011-08-12insane: add linux-gnu to the platform dataChris Larson1
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2011-08-12busybox: don't strip the main binaryChris Larson2
With this, we get a useful busybox-dbg package. Signed-off-by: Chris Larson <chris_larson@mentor.com>
2011-08-12local.conf.sample: Cleanup and improveRichard Purdie3
local.conf is the first thing anyone new to the project sees. Over time it has built up a ton cruft and isn't even accurate in places. This patch: * Moves things to local.conf.sample.extended if a new user is unlikely to need to immediately care about the options * Reorders the file to be more intuitive to a new user * Moves certain default values to default-distrovars.inc in cases where most users wouldn't want to change the value * Adds large blocks of text to explain what an option does. There have been too many cases of a user not realising what some of these settings do and how they can use them to their advantage (like DL_DIR for example). Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-08-11gnome-doc-utils: respect python-dir setting EXTRA_OECONFKumar Gala2
Don't just assign but append to EXTRA_OECONF so we maintain python-dir setting fo EXTRA_OECONF. This fixes issue if libdir is set to something like '/usr/lib64'. Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
2011-08-11Magic file path should be given for rpmbuildjani.uusi-rantala@nokia.com1
From d54b975506c392cfb59dbb3caf313ac061b6fa01 Mon Sep 17 00:00:00 2001 From: Jani Uusi-Rantala <jani.uusi-rantala@nokia.com> Date: Thu, 11 Aug 2011 18:37:56 +0300 Subject: [PATCH] Magic file path should be given for rpmbuild in _rpmfc_magic_path define so that build system default file is not used by accident. Not doing this caused many packages to fail building in several systems. Fixes [YOCTO #1358] Signed-off-by: Jani Uusi-Rantala <jani.uusi-rantala@nokia.com>
2011-08-11scripts/runqemu: Make it run on ubuntu 11.10Khem Raj1
location of libGL has moved in ubuntu 11.10 so we look for it in the new locations Signed-off-by: Khem Raj <raj.khem@gmail.com>
2011-08-11chkconfig: remove link for update-alternatives to disambiguateXiaofeng Yan1
[YOCTO #936] "update-alternatives" installed: one in /usr/sbin from chkconfig \ (symlinked to "alternatives"), and the other in /usr/bin \ from update-alternatives-cworth. It appears for whatever reason that the one from chkconfig is run \ during postinst processing but if you run the script from the command \ line it gets the other one. this is due to differences in the PATH environment variable. The following is the sequence to call scripts after kernel booting inittab -->rcS -->./S40networking(PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin) -->S98configure(call rpm-postinstall) #"/usr/sbin" is found prior to "/usr/bin", so update-alternatives from chkconfig is run in this script -->rc5.d -->profile(profile:4:PATH="/usr/local/bin:/usr/bin:/bin" profile:15: PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin) #"/usr/bin/" is found prior to "/usr/sbin", so update-alternatives from update-alternatives-cworth is run in this script So I remove the symlink (update-alternatives linked to chkconfig). The one from update-alternatives-cworth is left alone. Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com>
2011-08-11scripts/combo-layer: a simple way to script the combo-layer confLeandro Dorileo1
This small patch introduces a a very simple and basic way to script the combo-layer conf file. With that a combo can be shared with no need to change its config - associated to the use of environment variables for example. *Similar* to bitbake it considers every value starting with @ to be a python script. So local_repo could be easily configured as: [bitbake] local_repo = @os.getenv("LOCAL_REPO_DIR") + "/bitbake" or any more sophisticated python syntax. This version updates the config file description so users can be aware of. Signed-off-by: Leandro Dorileo <ldorileo@gmail.com>
2011-08-11sstate: Add level 2 debug so its possible to see what sstate is doingRichard Purdie1
Currently its hard to figure out if/when sstate is checking for possible packages to speed up builds. This patch adds level 2 debug output which better indicates what files are being searched for an why. [YOCTO #1259] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-08-11gcc: Various fixups to ensure consistent gcc buildsRichard Purdie18
We ensure that: * the shared work directory contains PR and ensure PR values are consistent across gcc builds * the regexp to handle library directories is in a specific task and run once This avoids breakage that was seen in incremental builds after commit be1f70d68b6b75772ebab8bdff683ddd7c42b0cd where the interpretor could become corrupted. This was due to the sed expression corrupting the source directory. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-08-10eglibc: force GLIBC_EXTRA_OECONF to not be uset for nativesdkKumar Gala3
Don't use GLIBC_EXTRA_OECONF for the nativesdk builds. Easiest solution is to just override it settings. Otherwise we might pickup configure options ment for the target build. Signed-off-by: Kumar Gala <galak@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-08-10oe.terminal: improve how we spawn screenChris Larson1
- Name the screen session 'devshell', to avoid confusion if running bitbake itself under a screen session. - Display a warning message when spawning screen, so it's clear to the user that screen has been run (otherwise do_devshell just appears to hang). Signed-off-by: Chris Larson <chris_larson@mentor.com>
2011-08-10Rework how the devshell functionsChris Larson3
In the new implementation, each known terminal is defined as a class in oe.terminal, as a subclass of bb.process.Popen. terminal.bbclass wraps this functionality, providing the metadata pieces. It obeys the OE_TERMINAL variable, which is a 'choice' typed variable. This variable may be 'auto', 'none', or any of the names of the defined terminals. When using 'auto', or requesting an unsupported terminal, we attempt to spawn them in priority order until we get one that's available on this system (and in the case of the X terminals, has DISPLAY defined). The 'none' value is used when we're doing things like automated builds, and want to ensure that no terminal is *ever* spawned, under any circumstances. Current available terminals: gnome konsole xterm rxvt screen Signed-off-by: Chris Larson <chris_larson@mentor.com>