After working through this stuff I was still confused as to how to
guide the user toward proper toolchain installation and on what they
needed to do for collecting their kernel and filesystem images.
These changes included some information on when and how to extract
the rootfs when the user is booting to NFS. Plus some other
general items like the significance of meta-toolchain-sdk as
compared to meta-toolchain.
(From yocto-docs rev: 2cc88b5193888a074ffd87cb253b9cfe08146877)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I had definitions for "The Yocto Project Files" and "The Yocto
Project Build Tree" in this chapter. They were misplaced. I have
deleted them and moved them to the development manual.
(From yocto-docs rev: 9238e75abc4578043fd625b3796b86d42204e16f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I moved the terms "Yocto Project Files" and "Yocto Project Build
Tree" into this development manual. They were previous defined
in the ADT manual. It makes more sense to have them where with other
terms.
(From yocto-docs rev: 2133110fd280db8cfbe998e6b46cdee0b260e777)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I made changes to the section titles so they have quotes around them
for easier reading in the PDF manual.
(From yocto-docs rev: 5bea470682c3d834f30ab0d2fcba148ea33d653f)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a development writer note and I noted that running a project
as an eclipse application pops a new instance of Eclipse.
(From yocto-docs rev: 6408ff7f4d59a0e535e560c7c0c63a3f373c640b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I added a couple of writer notes for development purposes. I also
formated the section title references so they have quotes around them
for easier reading in the PDF verison.
(From yocto-docs rev: 37adb580cf6c1369da43fc4ef7aaa4cc1cee0e5c)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
fixed some section naming conventions and minor wordings.
(From yocto-docs rev: 768d386c135c57ed3573e08bac72cad47fa101ce)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The information in the "Contributions" section has been migrated to
a "Submitting a Change" section in the YP Development Manual.
I re-wrote this section here to simply make a general statement
about how you can submit a change and then provided a reference
link to the appropriate section in the dev manual.
(From yocto-docs rev: 038caebb2815a8f09d35e99d5a2a0be76b05cacf)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The section on submitting a change was very sparse and incomplete.
I have significantly upgraded this section to provide more details.
(From yocto-docs rev: af43bb1e4902c45afb5ac4b0f099877acd7a81a2)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without this change we may or may not include startup-notification support.
We therefore explictly include it in the dependency list.
(From OE-Core rev: 8ad24306d8bc9c2fd73f4b814eb1a64c04707da5)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a native sstate post install function to fix the links
created between /lib and /usr/lib for the library files. These
links could point to an invalid build area when using shared state.
(From OE-Core rev: 8ab7b681cdb43c6c21c187b8cd01faa39727824a)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This fixes a problem when building meta-toolchain-gmae, by adding items that
will be provided by the host system, such as /bin/bash, /usr/bin/env and
libGL.so
(From OE-Core rev: 01361f9d25b0a0027bbbe713b93051a4663b14fc)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
RP: libGL.so() -> libGL.so
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #1514]
Without a native dependency on libxml-parser-perl-native,
shared-mime-info-native can fail its do_configure task.
checking for XML::Parser... configure: error: XML::Parser perl module is
required for intltool
Testing: Successfully built shared-mime-info and shared-mime-info-native for
qemuppc.
(From OE-Core rev: 51b1df89828e677232e125181209b26d3c5ec928)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Joshua Lock <josh@linux.intel.com>
CC: Richard Purdie <richard.purdie@linuxfoundation.org>
CC: Koen Kooi <koen@dominion.thruhere.net>
CC: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch partially fixes problems when building multilib extended
images such as libXX-core-image-minimal. Its not a perfect/complete
solution but works much better than any previous code did.
[YOCTO #1496] (partial)
[YOCTO #1497] (partial)
[YOCTO #1498] (partial)
(From OE-Core rev: 00c38774ef0232cc2be924ed8e59220e7c452096)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[YOCTO #1507]
We need to remove the file qemuarm/shutdown.desktop, or else, on qemuarm,
due to the PACKAGE_ARCH overriding from all to qemuarm in base.bbclass,
the generated deb file will be stored at
tmp/deploy/deb/qemuarm/qemu-config_1.0-r21_allarch.deb rather than
tmp/deploy/deb/all/qemu-config_1.0-r21_all.deb, and the package qemu-config
won't be installable -- task-base finally rdepends on qemu-config, so we get
the do_rootfs failure:
The following packages have unmet dependencies:
| task-base-extended: Depends: task-base but it is not going to be installed
| E: Broken packages
There is also a generic shutdown.desktop, we can keep it and use a proper
pkg_postinst to cope with the case of qemuarm.
(From OE-Core rev: 751212d5effdceab91d95705e647cf07e6820940)
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New gcc uses "%esp" rather than "%ebp" to index local variable in stack, and
push between save-to/restore-from stack decrease "%esp", which leads wrong
index. Saving registers via local variables to make gcc aware of this and avoid
stack disorder.
[YOCTO #1442] got fixed
(From OE-Core rev: afc9edc27e77e80fdd24b4c8c538f91672940e75)
Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libxml2 provides a libxml2.a library, which wasn't included in any of
the packages. Usually static libs are included into a -staticdev
package, but this package wasn't generated for libxml2, due to
libxml2.inc redeclaring PACKAGES variable (to include libxml2-utils).
Replace PACKAGES setting with expansion to include all default packages
(and so -staticdev package with libxml2.a).
(From OE-Core rev: 76052861cc95fd4ad4c4b9eb6ce4cd1065ad4dc9)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It seems nobody uses preloadable_libintl.so in OE world. It's not
included in any package. To stop oe-core from emiting a unshipped files
warning, remove that file in the end of do_install.
(From OE-Core rev: 9d33b6973438f514f1ca609c3a936b45af921e2f)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1) Drop static versions of extensions, as there is no point in them
2) For completeness include .la files for extensions into polkit-dev
(From OE-Core rev: e1a9f9e7f823330ab5140735b80988541e86e2d4)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1) Package gail modules into libgail package. .la files go into main
gtk+-dev package, debug symbols to gtk+-dbg.
2) For completeness add printerbackends .la files to gtk+-dev
(From OE-Core rev: a797c4ff1246566b545dc6cab2713a04f24fea6e)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
OE doesn't have common-lisp neither in oe-core, nor in org.oe.dev. Stop
this package from installing clisp-related files.
(From OE-Core rev: 894254c18fe19b6321c790d9a5d93b24868ba6f2)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is no point in warning against .so symlinks in -nativesdk
packages. They have to contain such links, so shut up the warning.
(From OE-Core rev: 287d02a731e45ce5d843db1fd4d78ba17e9ed487)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
icecc.bbclass assumed that nativesdk and cross-canadian packages should
use local icecc version. Instead those packages should use target-like
scheme for toolchain tarball generation.
(From OE-Core rev: 394c7c8cf262efeaafce40dc5eb480a1e041ac50)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
icecc-create-env(-native) is a native package. But if it doesn't have
the -native suffix, some dependency tracking stuff in oe-core (in
nativesdk.bbclass) get's crazy about it, trying to generate dependencies
to icecc-create-env-native packages. To fix that simply add -native
suffix to this package.
(From OE-Core rev: 83f9ebe9afb8bec4531899f8001a585c974e1db4)
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
By default cgi.py attempts to use /usr/local/bin/python as its
interpreter. However, on my Linux systems, including OE-Core,
python is installed into {bindir}. Adjust this one file based on
the comment at the top of the upstream file.
This resolves an issue where a runtime dependency discovered during
RPM packaging breaks the rootfs construction.
(From OE-Core rev: 1da01664963b9c6a6df171dcd0fbb1406544035b)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove the perl-dev recipe from the required packages. When this
recipe is included, libc6-dev is automatically added as are a large
number of other -dev packages. Eventually this creates a system
where the dependencies may not be able to be satisfied.
The perl-dev package should not be required in order to pass the LSB
testing.
(From OE-Core rev: 3f24b0f82458bcf15eabc74b9f370d9e774d0f63)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When PAM is enabled for the distribution we need to be sure to have a
build dependency of libpam, and runtime dependencies on the pam modules
used by the sudo package.
(From OE-Core rev: 79db5ccc7ee9b360451074dd42f7676e138cf384)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A small number of target installed programs, "${bindir}/pod*",
were incorrectly using the perl-native paths to access perl. This
caused a dependency failure during RPM rootfs install, and also
prevented those specific components from functioning.
(From OE-Core rev: 7b8db36e088e3e9cd585e8d8dde1c1c2860c3c2e)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
pkgconfig files belong in the -dev package. They automatically add
a runtime dependency (when packaging with RPM) for "pkgconfig", which
is not desired to be installed with this package.
(From OE-Core rev: 79cd09017693e0fd1634ea9748c797fcec4dac14)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
"--enable-configfiles" is deprecated upstream. Here is the original reason &
patch:
http://www.spinics.net/lists/linux-bluetooth/msg14266.html
Replace "--enable-configfiles" with "--enable-datafiles" in the bluez4
recipe.
(From OE-Core rev: 95e73d81554969ca4f0af43773343e1fbceda999)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
@PYTHON@ will points to the abstract path in sysroot, which should be
replaced by "#!/usr/bin/env python".
This should fix the sato-sdk rootfs error.
(From OE-Core rev: 51cd0bdf1fad230e919392db8c72afe2d9e21fdb)
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Sysctl is managed by other initscripts in the sysV world and by systemd itself in the systemd world, so drop it from the procps recipe.
This also fixes some style issues and a global FILES assignenment.
(From OE-Core rev: 80650bf4bce83e4e8d785e9a69eac0abbcdc6844)
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There were some config fragment warnings that were being hidden
by virtue of being output while generating the full config versus
the ones that were generated during the configuration audit task.
This change does the following:
- Updates the kern-tools SRCREV to include changes that move
all kernel configuration warnings to the audit script
- Updates the meta SRCREV for linux-yocto to get updated
kernel configuration fragments that are warning-free. These
are duplicated configs, and other changes that have a net
result of no runtime changes.
(From OE-Core rev: 8e67d4dd1e1bc64a84791abc613e237e29dd2aaa)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.0 kernel to enable blktrace to match our previous
functionality. This is done by the following meta branch commit:
[
meta: add blktrace feature
Add a 'blktrace feature' that turns on kernel support for blktrace, a
block I/O tracing tool. Added to 'standard' alongside similar tracing
tool config.
(From OE-Core rev: 21654cbf766f9c319b2fc8a08f0060c60ef005eb)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
kernel configuration validation takes place between two files. An
unprocessed configuration file (which is all the options found in
the various configuration fragments) and the final .config produced
by the lkc.
The unprocessed configuration file's name historically is based on
the name of the branch that was used to build the BSP. But with the
ability to map machine names to arbitrary branches, this is no longer
always true.
Searching for the pattern *-config-* in the meta subdirectory will
only match the config file, and frees the config validation phase
from being concerned with what branch was used to build the BSP.
(From OE-Core rev: 92e0d61f5bf15ca4eb262dfa3c533f9209a87915)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Scott Rifenbark
Richard Purdie
Saul Wold
Elizabeth Flanagan
Darren Hart
Dexuan Cui
Zhai Edwin
Dmitry Eremin-Solenikov
Mark Hatle
Marko Katić
Dongxiao Xu
Koen Kooi
Otavio Salvador
Bruce Ashfield