This reverts commit 37b9d140b5d55af4f77baab0c0b0343d8b5e8b6c since it caused
QA issues for several people. The ncurses location needs to be explicitly
specificed.
(From OE-Core rev: 87f02bdf4b9c0687f466de5c0bc81f510f389fc3)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is an update of the linux-yocto 3.0 and 3.2 SRCREVs to bring
in the following updates:
- v3.0.23 stable update
- v3.2.9 stable update
- 3.0/3.2: fri2 updates (pch + configuration changes) from Darren Hart
- 3.0: pvr merge from Kishore Bodke
- linux-yocto/rt: update to 3.0.23-rt38
- linux-yocto/rt: update to 3.2.9-rt15
These have been built for all qemu targets, and built for the appropriate
hardware platforms.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The --with-libncurses-prefix configure option was added before
this recipe had ncurses in DEPENDS, so it should be safe to
remove it.
(From OE-Core rev: 37b9d140b5d55af4f77baab0c0b0343d8b5e8b6c)
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The previous approach to moving the ncurses libraries to
base_libdir was too aggressive, and it broke curses support
in python.
Instead, move only libncurses, libncursesw, and libtinfo to
base_libdir and leave the remaining libraries in libdir.
Also delete ${libdir}/terminfo as it never gets packaged to
avoid a QA warning.
This fixes [YOCTO #2070] and is a partial fix for [YOCTO #1937].
(From OE-Core rev: ccd370ab147b78de7a5bd74818f755f4d3ca6d81)
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This method allows you to convert an absolute symlink into a
relative one.
(From OE-Core rev: 71062c1e0fb45a4b4e58ea5d217706aa2b402d88)
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Coming from OE-classic it was surprising that python-native now
requires 'libdir' to be exported. Otherwise autoconf would fail
to detect python libraries. This happend using a customized
environment setup script to use OE's compiler and libs without
bitbake.
* Use STAGING_LIBDIR instead of libdir.
* While at it, remove redundant 'and' statments.
(From OE-Core rev: 2edc929c47ac90eabad74e3726912fb3a57aaecd)
Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Python auto-detects libbz2 and there's no way to
force-disable it, so just enable it.
* Adds bz2 support to python-compression.
(From OE-Core rev: 744ff417fc0b4ef3096cf5f687f7e3bda20c694e)
Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* If plat-linux2/DLFCN.py was present, python was broken in our
image, i.e. it was unable to load many modules. This was due
to changed RTLD_* constants in dlfcn.h
* Python includes a script, plat-linux2/regen, to regenerate
the py source codes in this directory.
* Do what plat-linux2/regen would do, but use files from
STAGING_INCDIR.
(From OE-Core rev: 3bb9d027fff925a40c4dea9109df9464a76853b7)
Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Fixes many problems with linux2 vs. linux3. At least:
- Detected version was from build-host instead of target-host.
- linuxaudiodev and ossaudiodev were disabled for linux3.
- Files were missing in /usr/lib/python2.7/plat-linux3.
* Imported from upstream HG rev c816479f6aaf
* Bugtracker URL: http://bugs.python.org/issue12326
(From OE-Core rev: accb2b728ab10cae20be59253a56ac6410b8de10)
Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* The previous copy command preserved the original
owner and permission bits.
* The new command uses root:root and applies OE's
umask.
(From OE-Core rev: 710e565beadcf4ea965af688fd08b9b1f274ad57)
Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux auto-detects libudev for lsblk, so
disable it, because it's not listed in DEPENDS.
(From OE-Core rev: f831d4713a24dd56bf09276fb3b293d9c2b508cb)
Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* do_split_packages and package_do_split_locales dynamically add
packages in order of appearance of os.walk() or os.listdir().
This order varies between multiple build hosts (and probably
also between successive builds).
* Sort the list of dynamically added packages, to get a consistent
and reproducible order.
* This reduces the diffs in buildhistory and improves
comparability between builds.
(From OE-Core rev: 76f46391239d3e123cfde900c52ca12ac73fd84f)
Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the case of self-hosted-image.bb, IMAGE_FSTYPES = "vmdk", so the
variables alltypes and subimages don't contain ext3, and .rootfs.ext3
won't be created, and finally the generated .hddimg and .vmdk don't have
an actual rootfs -- the size of the .vmdk file is only about 9MB.
[YOCTO #2067]
(From OE-Core rev: 39f14c66d5df226689238810b759f502644deb5c)
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Both files contain -L../../WebCore/release -L../../JavaScriptCore/release -lwebcore -ljscore
* These paths and libs don't get installed.
* When building a shared lib with libtool, that links
with libQtWebKit, libtool adds these unneeded parameters
to the linker command-line, thus linking fails.
(From OE-Core rev: 4c41a3204ef72f53813ddc86fe525fa9c6714daa)
Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Adding "GPLv2 & LGPLv2.1" to create a dual license to cover the libraries.
* Bump up PR
(From OE-Core rev: 468aab48b07d345aadb6f449421824b0447d29c2)
Signed-off-by: Jeff Lance <j-lance1@ti.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use 'run-postinsts' as trigger script name as it describes better the
intent of it.
(From OE-Core rev: 69a4765d63ac6de3f1a6804cfca6b52c008e4c22)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use 'run-postinsts' as trigger script name as it describes better the
intent of it.
(From OE-Core rev: 9a0a106f64a913de593877bf47f79cb29ab87716)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use 'run-postinsts' as trigger script name as it describes better the
intent of it.
(From OE-Core rev: 6bc50e531a15728be019af7bec5bce704fb72f8f)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When building without package management tools the
ROOTFS_BOOTSTRAP_INSTALL packages need to be available to provide the
bare minimal for rootfs unconfigure postinsts to be on first boot.
Those packages where being include in core-image.bbclass' based images
however every image needs those available for proper rootfs generation.
(From OE-Core rev: 4f2845739fc7a1f2c784f4d3be048ee111e7d093)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
During the work to enhance the ability to specify out of tree kernel
features, an assumption was made about PN being part of a patch
path. This assumption is incorrect, since patches can be anywhere in
the valid FILESPATH.
To make locating the patches in WORKDIR simple, we can just query
patch.bbclass and return both the absolute directory of the patch
and the subdirectory as it was specified on the src_uri.
(From OE-Core rev: ecade4c986e5045879ea204e31457c9b53a15e33)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This makes sense in this case even if its empty since this package is the
correct owner for it.
(From OE-Core rev: a5b8067f4d8c4b2aa230d8c998f4188d7b43895b)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The .m4 file has no details but the upstream project is clearly GPLv2
so update the LICENSE file to match.
(From OE-Core rev: 25109aa2a4c2814ad89b4b416b4de31d14b65e93)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The source is unclear which version of the license applies. Since BSD is listed,
we have plenty of choice so lets pick some versions. Most people would pick
BSD out of the three anyway.
(From OE-Core rev: 04c2e69ffb77b43b853170c2b804eab367260063)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch fixes the QA warnings:
WARNING: For recipe librsvg, the following files/directories were installed but not shipped in any package:
WARNING: /usr/lib/gtk-3.0
WARNING: /usr/lib/gtk-3.0/engines
(From OE-Core rev: 973fabc6db9398869c5257b9c761d9d741d5c407)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This resolves the QA warning:
WARNING: For recipe sato-screenshot, the following files/directories were installed but not shipped in any package:
WARNING: /usr/lib/matchbox-panel/libscreenshot.la
(From OE-Core rev: c5f4a9261d582a52429cf5a115efed61987b0dd8)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This addresses the QA warnings:
WARNING: For recipe xf86-input-vmmouse, the following files/directories were installed but not shipped in any package:
WARNING: /lib
WARNING: /lib/udev
WARNING: /lib/udev/rules.d
WARNING: /lib/udev/rules.d/69-xorg-vmmouse.rules
WARNING: /usr/share/X11
WARNING: /usr/share/hal
WARNING: /usr/share/X11/xorg.conf.d
WARNING: /usr/share/X11/xorg.conf.d/50-vmmouse.conf
WARNING: /usr/share/hal/fdi
WARNING: /usr/share/hal/fdi/policy
WARNING: /usr/share/hal/fdi/policy/20thirdparty
WARNING: /usr/share/hal/fdi/policy/20thirdparty/11-x11-vmmouse.fdi
WARNING: /usr/lib/hal
WARNING: /usr/lib/hal/hal-probe-vmmouse
The hal files are simply deleted, we don't care about hal.
(From OE-Core rev: fb1e1ca346c617598726609425406b5afc79270d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some libraries like libcrypto.so are installed at base_libdir
instead of libdir. So add the base_libdir to CMAKE_LIBRARY_PATH
so that these libraries can be found correctly.
This resolves an issues with libzypp, which was not finding the
libcrypo library correctly in an x32 build.
(From OE-Core rev: f47ada62a3da879006e7cb27479dc9b72c56e923)
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This avoids the error:
ln: creating symbolic link `/media/data1/build1/poky/build/tmp/work/x86_64-linux/mesa-dri-glsl-native-7.11-r0/Mesa-7.11/src/glsl//../../configs/current': File exists
(From OE-Core rev: 7871772c74e65ef472c5bf3776e4b3b30308bd5d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
See the comment in the code in the commit for more information.
(Bitbake rev: 2d56dc7b1f0d186e14c4c8a949b280b6b3fc31de)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the initial implementation there was a relcutance on my part to
generate incremental cache components on the fly since it would lead
to some duplicate code.
We are now seeing problems where each thread reading in the saved cache
file causes significant overhead and can make the process appear to hang
on a many core build, particularly when the cache file is large.
This patch changes the code to maintain the delta in a separate dict
right from the start. The code duplication isn't too bad and could be
mitigated in other ways if it becomes an issue.
[YOCTO #2039 partial]
(Bitbake rev: cdd5d0dee6ab12326b252b6b505a316a52638cac)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
James Limbouris
Randy MacLeod
Richard Purdie
Bruce Ashfield
Scott Garman
Andreas Oberritter
Otavio Salvador
Dexuan Cui
Saul Wold
Jeff Lance
Nitin A Kamble