Prelink contains some hardcoded assumptions about the path layout of
the target system. Unfortunately if the system doesn't match, prelink
doesn't work. This breaks:
a) prelink of those images
b) the unsafe-references-in-binaries QA test (which uses prelink-rtld)
One way to work around this is to construct an ld.so.conf file which
lists the library paths in question. We do this in sanity QA check and
in the rootfs prelink code, being careful not to trample any existing
target ld.so.conf.
There is an additional problem that $LIB references in RPATHs won't be
handled correctly, I've not see any system use these in reality though
so this change at least improves things.
(From OE-Core rev: 7fd1d7e639c2ed7e0699937a5cb245c187b7c811)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When installing the eSDK, if setscene task fail for some reason, the tests
would ignore this. This is bad since we assume they're working.
This adds some sanity test code which detects if setscene tasks are
needing to run and errors if there are any.
(From OE-Core rev: 7ea670c3b00439ca5eeb6ae1efd475f0954268b7)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When reading the mtime from disk, the system can get a floating point
value. Convert this to an int for comparision purposes, else some
packages always get reindexed as the value in the index is an int.
(From OE-Core rev: cc01ffeee757738c169f8970fd89bf0933e93532)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The xmlto script uses bashisms and checks at configure time to find a bash
binary. If the build host has /bin/sh as bash then this gets detected, which
causes problems in native builds if the sstate is then shared to a machine with
/bin/sh as dash.
(From OE-Core rev: e89cd308792f613e5b4765dc0f7f21569aaaab6f)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Apply a patch taken from Gentoo to hopefully fix the remaining parallel make
races.
(From OE-Core rev: 3d806d59a4c5e8ff35c7e7c5a3a6ef85e2b4b259)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libgcc_s.so.1 is required by btrfs-tools at runtime for certain
operations, such as scrub due to the use of pthread_cancel.
(From OE-Core rev: 3e31e77b8a093aab077dbbb23e4c18c1ebe94bff)
Signed-off-by: Robert Joslyn <robert_joslyn@selinc.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changes to the btrfs-tools recipe means we need to add libgcc-native
to ASSUME_PROVIDED.
(From OE-Core rev: 448726469761b8cdc4b4acedb664cede994dde12)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
do_compile does this but do_install needs same env as well
(From OE-Core rev: 57e4bb197173552706db60a3d82e1dddc0a6b004)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch is no longer required as upstreamed has fixed
the problem in more comprehensive way
(From OE-Core rev: 3eb83b880e66fff0e715e79546ed98d9818390b5)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If gdb was configured to use the internal readline but static libraries were
disabled, gdb wouldn't dutifully not build libreadline.a which was a problem
when it tried to link with that library.
Solve this by ensuring --enable-static is passed to the readline configure.
(From OE-Core rev: 1490caa07d72af81c7e515e4ff7b4905da840d7d)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix the quotes in the bb.utils.contains feature check so that the call
results in a boolean value instead of a string, which allows the warning
check to occur.
(From OE-Core rev: aac3919f538a5608ffcc3af5bd8f121e3c2c3469)
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Clearly I didn't test this part of the code - lists don't have an "add"
method. Needless to say I have tested it now.
(From OE-Core rev: 063ed9058a14775f77e7875d4f6ef5719fa03f18)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A sensible assumption is that BSPs have a USB keyboard and mouse connected
unless told otherwise, so flip the logic in the formfactor config script that
previously assumed that a keyboard was not connected by default.
[ YOCTO #9174 ]
(From OE-Core rev: a82ce3e477a475dccea3837eabacd9e93b873ee6)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
ls adds a '.' at the end of the permission field list on SELinux
machines, filter this out so root tests work on SELinux machines.
And backport one patch for other tests.
(From OE-Core rev: 2981d026460658fd2db7df3618d718fe6e8bfca0)
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libitm is already disabled for big endian MIPS, but needs to be
disabled for little endian MIPS targets too.
(From OE-Core rev: 421e8ac60ff6eb87e66ebeab6f14d74216386578)
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a build-sdk command which is only available within the extensible
SDK that builds a derivative extensible SDK. The idea is recipes in the
workspace become a part of the new SDK - for example, this allows taking
a vendor provided SDK, adding a few libs and then producing a new SDK
with those included.
When normally building the extensible SDK, the workspace is excluded;
here we need to copy into the new SDK (renaming it in the process); the
recipes' task signatures become locked and thus the sources are no
longer needed, so they are removed along with the workspace bbappends
which would interfere with the locked signatures. Additionally we need
to just copy the configuration files (i.e. local.conf and auto.conf)
rather than filtering and appending to them since that work has already
been done when constructing the original SDK. The extra sstate artifacts
from workspace recipes are also determined and copied into the new SDK
in minimal mode (on the assumption that you won't set up a new sstate
mirror).
This reuses some code from build-image, so that needed to be
generalised to allow that.
Implements [YOCTO #8892].
(From OE-Core rev: 59e207ff6dd4b50a8905e14bc9292cf2794f4e7a)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Hyphens aren't allowed in python identifiers, so you shouldn't use them
in module names or they are more difficult to import.
(From OE-Core rev: e8f6db9436dfc923e236f2cbc08f357e3b24fd5d)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixing one of the recipes not to contain unsafe references to paths
results in this QA test failing. Improve the test so that we test
the recipe works, then if we intentionally break the recipe, the
issue is detected.
Also split out the binaries test from the scripts test. The binaries
issue may also get 'fixed' in future and need the same fix.
(From OE-Core rev: 68db200ca5b404d6c0aa0cbf5a587397d0aa65da)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Previously, the checking for unsafe references is not strict enough. It
only checks whether '/usr/' is in the script. As a result, any script
containing statements like below will match this check.
PATH="/bin:/sbin:/usr/bin:/usr/sbin"
However, as we can see, this is actually not an unsafe reference. What
we really want to check is something like '/usr/bin/tail', so we should
make the checking stricter.
This patch solves the QA warning in gzip and nfs-utils.
(From OE-Core rev: f818f7359c1a5db2c5c041c42eecb9f0434d9800)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the "Building Images" section, we just plow into the command
line experience without giving any indication of a GUI option
through which to try out the Yocto Project. I updated the
paragraph introducing the build stuff by presenting the command
line method or a GUI method via Toaster.
(From yocto-docs rev: c7d0b2e1c3f9746bdcf2ba8ded71ee14cfa17e58)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Applied better wording to a couple areas in this section as
pointed out by the review.
Fixes [YOCTO #9114]
(From yocto-docs rev: f5a402aa08b102c767e112d8df05041650733d54)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8620]
Added a couple more clarifications for some nativesdk term
uses. Minor edits to help make things clearer.
(From yocto-docs rev: 38082e1120861332674f97f67966b1f5cec7dc03)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Created the new section for the devtool upgrade flow.
(From yocto-docs rev: f3a7f78305ce5045604d9892e18b31b7eabcba62)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Created a new figure for the devtool upgrade flow. Put the figure
in the "figures" folder of the dev-manual and the mega-manual.
Updated the Makefile to include the new figure when creating
Tarball of the dev-manual and the mega-manual.
(From yocto-docs rev: 4b504f6f179ca7c7e9a69f23fc25b1f33ced8e44)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Made some review changes to the workflow structure, devtool
add flow, and devtool modify flow diagrams.
(From yocto-docs rev: f432d9b0270615974e67a0cc243560fdbfa44724)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Closing in on the devtool add and devtool modify sections.
(From yocto-docs rev: 202b688c03cc1801576bbed3b771bb329f6b8520)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
New figure and some writer notes for now
(From yocto-docs rev: 0a627626f5f353e514b0225b468b0bd0fa3ceef3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
dev-manual: I did not have the checksum figure there or the sources
directory.
mega-manual: Per normal, had to copy the updated figure into the
figures directory of the mega-manual.
(From yocto-docs rev: d6fb3373b2f3c1e89da87d3e8b9877e643f73c8e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This style is for review purposes and can be implemented in
the XML file using <para role='writernotes'>. The text in the
paragraph is rendered red.
(From yocto-docs rev: db990802594af3a70b11e320c06fe6a9dc80579b)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Created a new figure for devtool add flow. Added support
for it in the Makefile. The figure, as usual, needs to
reside in the figures directory in both the dev-manual and
the mega-manual.
(From yocto-docs rev: 2040a31b806fdade060f7a4182a09673b76db7b3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #9114]
Added a "Notes" box to address run script naming points
and the fact that running a task's script is identical to
what BitBake would do when it runs the task.
(From yocto-docs rev: ddfba59743c977a3a3483ed9053434d3c622f698)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8620]
I applied some review comments for the changes made to several
areas in both these manuals. Minor wording fixes and the
dropping of some changes as directed by Joshua Lock.
(From yocto-docs rev: 71af89da612c37162ba27844c297879d643caf65)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #9114]
Added more detail on how to run commands from within the devshell.
(From yocto-docs rev: 6535a8b80bbad3a4ece191c7e5a145ef5e09f1e2)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The manage.py createsuperuser command must be run from the directory
containing the Toaster database, and not from the root of the checkout
directory, as the manual indicated. Amend the section to provide the
correct instructions.
(From yocto-docs rev: 41fa8a04c947169d971c5e1ecb4619249d1dc7b3)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #8620]
I went through and made some judgement calls on the use of
"native" and "sdknative". I tried to make sure that the reader
understood the real meaning of these terms.
(From yocto-docs rev: d711e8c6dfb32a4ad79e9d11dbf44fbc759d0245)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Two instances existed instructing the user about a prompt
for the json file prompt. These have been removed.
(From yocto-docs rev: f45cb8c5db70ef15e685c68508fd3941d8c6727e)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
