]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/log
thirdparty/openembedded/openembedded-core-contrib.git
6 years agoelfutils: check data_list.data.d.d_buf before free it
Robert Yang [Thu, 16 Aug 2018 02:38:22 +0000 (10:38 +0800)] 
elfutils: check data_list.data.d.d_buf before free it

[YOCTO #12791]

The one which actually saves the data is data_list.data.d.d_buf, so check it
before free rawdata_base.

This can fix a segmentation fault when prelink libqb_1.0.3:
prelink: /usr/lib/libqb.so.0.18.2: Symbol section index outside of section numbers

The segmentation fault happens when prelink call elf_end().

Fixed:
MACHINE="qemux86-64"
IMAGE_INSTALL_append = " libqb" #libqp is from meta-openembedded
$ bitbake core-image-minimal
Segmention fault

(From OE-Core rev: 560154e8525dce4beb8199ffc0d7c964da9d665a)

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoprelink: use ehdr.e_shstrndx as index rather than ehdr.e_shnum
Robert Yang [Thu, 16 Aug 2018 02:25:46 +0000 (10:25 +0800)] 
prelink: use ehdr.e_shstrndx as index rather than ehdr.e_shnum

[YOCTO #12791]

According to struct elf32_hd, the e_shnum is section header number, and the
index is e_shstrndx, not e_shnum.

This can fix segmention fault when handle libqb.so.0.18.2 from libqb_1.0.3.
It fails to handle libqb.so.0.18.2 and get errors:
Symbol section index outside of section numbers

Then segmentation fault, this is because the e_shnum is 34, while e_shstrndx is
27 (it would be 33 when no errors), I've checked several elf files to confirm
that the ones after e_shstrndx is NULL, so use e_shstrndx should be correct.

Fixed:
MACHINE="qemux86-64"
IMAGE_INSTALL_append = " libqb" #libqp is from meta-openembedded
$ bitbake core-image-minimal
Segmention fault

(From OE-Core rev: b7c291ee6532cba845ee6bfbbaa21076a2b2cbe5)

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agobinutils: Improve check for input file matching output file
Robert Yang [Thu, 16 Aug 2018 02:54:39 +0000 (10:54 +0800)] 
binutils: Improve check for input file matching output file

When the assembler reports that the input and output are the same, report the
file names involved, in order to help debugging.  Also do not equate two files
are the same if the have the same inode value but reside on different file
systems.

(From OE-Core rev: 83cb0938b90bab9ba727f883b8955b0b40d49a01)

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agobitbake: bb/utils.py: add break_hardlinks helper
Rasmus Villemoes [Tue, 10 Jul 2018 12:03:34 +0000 (14:03 +0200)] 
bitbake: bb/utils.py: add break_hardlinks helper

bb.utils.copyfile is called in a few places with identical src and dst
in order to create an st_nlinks==1 version of the file. That that even
works relies on an implementation detail of copyfile (namely, that it
creates a temporary file and then does a rename). Moreover, it's a waste
of time if the file already has st_nlinks==1.

So create a helper that optimizes away the copy in the st_nlinks==1
case. Of course, this helper relies on the same implementation detail,
but that's now contained within bb.utils itself.

To test that we do at least sometimes hit the no-copy path, I tested
locally with

     if sstat[stat.ST_NLINK] == 1:
+        bb.note("Woohoo, 2*%d bytes I/O avoided" % sstat[stat.ST_SIZE])
         return True

(and the obvious places in oe-core patched), and the do_package log files
are indeed filled with woohoo notes.

(Bitbake rev: 7ae93cf40ab91965147055100432961436bce46c)

Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agopopulate_sdk_base.bbclass: inherit and use image-postinst-intercepts
Christopher Larson [Fri, 27 Jul 2018 17:24:30 +0000 (22:24 +0500)] 
populate_sdk_base.bbclass: inherit and use image-postinst-intercepts

(From OE-Core rev: fb83997ded3789c7447402a9fda03b1669cecae0)

Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoimage.bbclass: inherit and use image-postinst-intercepts
Christopher Larson [Fri, 27 Jul 2018 17:24:29 +0000 (22:24 +0500)] 
image.bbclass: inherit and use image-postinst-intercepts

(From OE-Core rev: 73cccdb6942404961415e5939263686719b24061)

Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoimage-postinst-intercepts.bbclass: add class
Christopher Larson [Fri, 27 Jul 2018 17:24:28 +0000 (22:24 +0500)] 
image-postinst-intercepts.bbclass: add class

This class sets POSTINST_INTERCEPTS and POSTINST_INTERCEPTS_CHECKSUMS,
to allow us to pull intercepts from BBPATH. This is kept as a separate
class, as it's needed by both image construction and sdk construction,
the latter to support meta-toolchain & similar recipes.

(From OE-Core rev: 7a2044df4ae8d80cf25a6bfd9b71978ffefbfa33)

Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agooe.package_manager: support loading intercepts from multiple paths
Christopher Larson [Fri, 27 Jul 2018 17:24:27 +0000 (22:24 +0500)] 
oe.package_manager: support loading intercepts from multiple paths

- if POSTINST_INTERCEPTS is set, use the listed intercept files, or
- if POSTINST_INTERCEPTS_PATH is set, load from the listed paths, or
- if POSTINST_INTERCEPTS_DIR is set, load from it (for compatibility), or
- load from ${COREBASE}/meta/postinst-intercepts

(From OE-Core rev: 9ba2f2b1df277b2b881f68166d9cd1c19db66e23)

Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoacpica: Add missing DEPENDS on bison-native
Richard Purdie [Wed, 15 Aug 2018 20:42:46 +0000 (21:42 +0100)] 
acpica: Add missing DEPENDS on bison-native

(From OE-Core rev: e7c0ad5d3eff6b1d7170e7e0a539d1807a2bb452)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosstate: Optimise SSTATE_EXCLUDEDEPS_SYSROOT handling
Richard Purdie [Wed, 15 Aug 2018 14:30:07 +0000 (14:30 +0000)] 
sstate: Optimise SSTATE_EXCLUDEDEPS_SYSROOT handling

Using re.compile() is around six times faster than recompiling the regexp
each time so maintain a cache.

(From OE-Core rev: 41eb382737706e245f2b7104e313c8dfaa370945)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosstate: use SSTATE_EXCLUDEDEPS_SYSROOT for skipping base-passwd|shadow-sysroot recipes
André Draszik [Tue, 22 May 2018 12:25:52 +0000 (13:25 +0100)] 
sstate: use SSTATE_EXCLUDEDEPS_SYSROOT for skipping base-passwd|shadow-sysroot recipes

Use the newly introduced SSTATE_EXCLUDEDEPS_SYSROOT for specifying
the base-passwd|shadow-sysroot recipes to be excluded from a recipe sysroot.

(From OE-Core rev: 68e502e9063a88532fe0154f152ba408f0091900)

Signed-off-by: André Draszik <andre.draszik@jci.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosstate: use SSTATE_EXCLUDEDEPS_SYSROOT for skipping *-initial recipes
André Draszik [Tue, 22 May 2018 12:25:51 +0000 (13:25 +0100)] 
sstate: use SSTATE_EXCLUDEDEPS_SYSROOT for skipping *-initial recipes

Use the newly introduced SSTATE_EXCLUDEDEPS_SYSROOT for specifying
the *-initial recipes to be excluded from a recipe sysroot.

(From OE-Core rev: 6706bad52f9311ea79c534ee90014c3216992999)

Signed-off-by: André Draszik <andre.draszik@jci.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosstate: allow specifying indirect dependencies to exclude from sysroot
André Draszik [Tue, 22 May 2018 12:25:50 +0000 (13:25 +0100)] 
sstate: allow specifying indirect dependencies to exclude from sysroot

Currently, a dependency on any -native recipe will pull in
all dependencies of that -native recipe in the recipe
sysroot. This behaviour might not always be wanted, e.g.
when that -native recipe depends on build-tools that are
not relevant for the current recipe.

This change adds a SSTATE_EXCLUDEDEPS_SYSROOT variable,
which will be evaluated for such recursive dependencies to
be excluded. The idea is similar to
   http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146324.html
except that the list is not hard-coded anymore.

SSTATE_EXCLUDEDEPS_SYSROOT is evaluated as two regular
expressions of recipe and dependency to ignore, e.g. in
the above flex-native / bison-native use-case, one would
specify

    SSTATE_EXCLUDEDEPS_SYSROOT = ".*->(flex|bison)-native"

in layer.conf.

The existing special handling of "-initial" as well as
"base-passwd" and "shadow-sysroot" could also be
streamlined:

    SSTATE_EXCLUDEDEPS_SYSROOT += "\
        .*->.*-initial.* \
        .*(base-passwd|shadow-sysroot)->.* \
    "

Another anticipated user is meta-java, where certain newer
JDKs can only be bootstrapped (built) using older JDKs,
but it doesn't make much sense to copy all those older
JDKs and their own build tools (ant, etc.) into the
sysroot of recipes wanting to be built using the newer JDK
(only), e.g.:

    SSTATE_EXCLUDEDEPS_SYSROOT += "\
        openjdk-8-native->(ant-native|attr-native|coreutils-native|icedtea7-native|libxslt-native|make-native|openssl-native|zip-native|unzip-native) \
    "

(From OE-Core rev: 92c5131a2feae2036c71a36c18bb9175bb2856dc)

Signed-off-by: André Draszik <andre.draszik@jci.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosecurity_flags: Add PIC to cflags for some recipes on ppc
Khem Raj [Wed, 15 Aug 2018 01:40:05 +0000 (18:40 -0700)] 
security_flags: Add PIC to cflags for some recipes on ppc

Fixes issues related out of range R_PPC_REL24
e.g.
/usr/lib/xorg/modules/input/libinput_drv.so: /usr/lib/libinput.so.10: R_PPC_REL24 relocation at 0x0e8602c4 for symbol `libevdev_has_event_code' out of range

(From OE-Core rev: 48c8d13a9bdcacb64a330074588f7c6bb5cae90d)

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agolibdrm: Upgrade to 2.4.93
Khem Raj [Wed, 15 Aug 2018 01:40:04 +0000 (18:40 -0700)] 
libdrm: Upgrade to 2.4.93

(From OE-Core rev: c855d485204e7674db6c660c868fbc3cf28ef308)

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoopenssl-1.1: /etc/ssl location compatibility
Andrej Valek [Tue, 17 Jul 2018 09:10:35 +0000 (11:10 +0200)] 
openssl-1.1: /etc/ssl location compatibility

Some packages have hard-coded path to /etc/ssl location.
Create a symlinks to correct location.

(From OE-Core rev: 87ae1f2de1b033172560e3c89caa06bd9e10d071)

Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
Signed-off-by: Marko Peter <peter.marko@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoopenssl-1.1: rework packaging
Andrej Valek [Tue, 17 Jul 2018 09:10:34 +0000 (11:10 +0200)] 
openssl-1.1: rework packaging

The main idea is to have libssl and libcrypto in separate packages.
This saves space if only single library is needed and also some recipes
(in other layers) depend on these library packages.
Together with this other packages like in 1.0.x were created.
The only difference is that openssl 1.1 has additional package openssl-bin.

Add missing dependency to perl for openssl-bin pkg, c_rehash requires it.

(From OE-Core rev: b729cae26de23ac6df10cbf74bab0105580cc43d)

Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
Signed-off-by: Marko Peter <peter.marko@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoopenssl-1.1: fix c_rehash perl errors
Andrej Valek [Tue, 17 Jul 2018 09:10:33 +0000 (11:10 +0200)] 
openssl-1.1: fix c_rehash perl errors

Patch original c_rehash script with Debian patch instead
of overriding it with own version.

Error output from c_reshah without patching:
  Unknown regexp modifier "/b" at ./c_rehash line 15, at end of line
  Unknown regexp modifier "/W" at ./c_rehash line 28, at end of line
  Unknown regexp modifier "/3" at ./c_rehash line 28, at end of line
  Unknown regexp modifier "/2" at ./c_rehash line 28, at end of line
  No such class installdir at ./c_rehash line 63, near "Prefix our
  installdir"
    (Might be a runaway multi-line // string starting on line 28)
  syntax error at ./c_rehash line 63, near "Prefix our installdir"
  Can't redeclare "my" in "my" at ./c_rehash line 68, near ""
  Execution of ./c_rehash aborted due to compilation errors.

(From OE-Core rev: f8a826f497073533a3e4c390255ae197d65d6ef3)

Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
Signed-off-by: Marko Peter <peter.marko@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agomachine configs: replace deprecated "SERIAL_CONSOLE"
Maciej Pijanowski [Mon, 13 Aug 2018 17:57:13 +0000 (19:57 +0200)] 
machine configs: replace deprecated "SERIAL_CONSOLE"

SERIAL_CONSOLE was already deprecated in 2013, yet still some
machine configuration files were using it. This patch replaces
it with SERIAL_CONSOLES, which is the successor.

The default value in systemd-serialgetty.bb can also be safely
transitioned from SERIAL_CONSOLE to SERIAL_CONSOLES, as this
recipe already uses SERIAL_CONSOLES within do_install().

The documentation seems to be already up do date.
beaglebone-yocto.conf in the bsp-guide already uses
SERIAL_CONSOLES. The ref-manual redirects from SERIAL_CONSOLE
to SERIAL_CONSOLES.

[YOCTO #12653]

(From meta-yocto rev: a0c5332aefe75cf314e78284f578b17c51b8ab27)

Signed-off-by: Maciej Pijanowski <maciej.pijanowski@3mdeb.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agometa-yocto-bsp: beaglebone: Use the uuid for the block device naming in wic image
Kevin Hao [Tue, 14 Aug 2018 01:31:26 +0000 (09:31 +0800)] 
meta-yocto-bsp: beaglebone: Use the uuid for the block device naming in wic image

(From meta-yocto rev: b713626dda68d4f03632da2ecbb1e073397e0c7a)

Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agometa-yocto-bsp: beaglebone: Add the u-boot boot config file for the wic image
Kevin Hao [Tue, 14 Aug 2018 01:31:25 +0000 (09:31 +0800)] 
meta-yocto-bsp: beaglebone: Add the u-boot boot config file for the wic image

(From meta-yocto rev: 800fc3ea87add6a7205ecfa3b088701ed635082f)

Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agobitbake: runqueue: Move decision if a task can be started to one common place
Andreas Müller [Mon, 13 Aug 2018 21:04:44 +0000 (23:04 +0200)] 
bitbake: runqueue: Move decision if a task can be started to one common place

(Bitbake rev: 99d9e4389e1f1d78d17a23ee078fe3f4a12cb31d)

Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agocve-check.bbclass: do not download the CVE DB in package-specific tasks
Konstantin Shemyak [Mon, 13 Aug 2018 07:23:28 +0000 (10:23 +0300)] 
cve-check.bbclass: do not download the CVE DB in package-specific tasks

Disable downloading of the vulnerability DB in do_check_cves() task.

When invoked in this task, cve-check-tool attempts re-download of the CVE DB
if the latter is older than certain threshold. While reasonable for a
stand-alone CVE checker, this behavior can cause errors in parallel builds
if the build time is longer than this threshold:
* Other tasks might be using the DB.
* Several packages can start the download of the same file at the same time.

This check is not really needed, as the DB has been downloaded by
cve_check_tool:do_populate_cve_db() which is a prerequisite of any do_build().
The DB will be at most (threshold + build_time) old.

(From OE-Core rev: 125789b6ee6d47ab84192230f63971c4e22418ba)

Signed-off-by: Konstantin Shemyak <konstantin.shemyak@ge.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoimage: Use ${COREBASE}/meta for timestamp, fallback to bitbake.conf
Alex Kiernan [Fri, 20 Jul 2018 04:33:17 +0000 (04:33 +0000)] 
image: Use ${COREBASE}/meta for timestamp, fallback to bitbake.conf

To handle the case where ${COREBASE} isn't the git directory, avoid
erroring out when the git command fails. If we don't have a timestamp
after this, fall back to the timestamp from conf/bitbake.conf.

(From OE-Core rev: 97b439469a45a089431ca9c31893288c855045f4)

Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agopackage.bbclass: improve -dbg and -src package ordering
Rasmus Villemoes [Wed, 11 Jul 2018 11:38:56 +0000 (13:38 +0200)] 
package.bbclass: improve -dbg and -src package ordering

nativesdk-gpgme fails package_qa when setting PACKAGE_DEBUG_SPLIT_STYLE
= "debug-with-srcpkg".

ERROR: nativesdk-gpgme-1.10.0-r0 do_package_qa: QA Issue: non debug package contains .debug directory: nativesdk-python3-gpg path /work/x86_64-nativesdk-oesdk-linux/nativesdk-gpgme/1.10.0-r0/packages-split/nativesdk-python3-gpg/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/lib/python3.5/site-packages/gpg/.debug/_gpgme.cpython-35m-x86_64-linux-gnu.so [debug-files]

This turns out to be because the automatic moving of the -dbg package to
the beginning of the package list is disabled in that case, so the
python3-gpg packages that the recipe prepends to PACKAGES ends up before
the -dbg package.

It's not clear why the "and not split_source_package" was added when
debug-with-srcpkg was introduced. Presumably the intention was to
prevent the -dbg package to end up before the -src package, which we of
course need to. But at the same time, we still need -dbg packages to end
up before all other packages.

Using list.insert(0, ...) also means that if there happens to more than
one -dbg package, their relative ordering gets inverted in the new list.

This tries to fix these issues by sorting the packages by (priority,
original position), where priority is 10 for -src, 30 for -dbg and 50
for everything else. That guarantees that packages of the same "type"
preserve their relative ordering, while also ensuring that -dbg always
preceed other packages. This scheme is also quite extensible, and,
should the need arise, one could even expose the priorities as a knob
the recipe author could use to ensure specific orderings of packages
instead of the somewhat fragile and coarse-grained method of "prepend or
append, and ensure you do that in a proper order".

Probably the autodebug condition needs to stay, but I think the
split_source_package condition in the preceding elif should be removed,
so that that logic applies to all packages called -src, not just the one
we might have created a few lines above.

(From OE-Core rev: 805edbc7dc9ceae00d991f9b4e185bbbe1d3ba45)

Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoweston: add dependency on virtual/libgbm for kms PACKAGECONFIG
Martin Jansa [Tue, 14 Aug 2018 10:53:11 +0000 (10:53 +0000)] 
weston: add dependency on virtual/libgbm for kms PACKAGECONFIG

* gbm is checked in configure.ac:

AC_ARG_ENABLE(drm-compositor, [  --enable-drm-compositor],,
              enable_drm_compositor=yes)
AM_CONDITIONAL(ENABLE_DRM_COMPOSITOR, test x$enable_drm_compositor = xyes)
if test x$enable_drm_compositor = xyes; then
  AC_DEFINE([BUILD_DRM_COMPOSITOR], [1], [Build the DRM compositor])
  PKG_CHECK_MODULES(DRM_COMPOSITOR, [libudev >= 136 libdrm >= 2.4.30 gbm mtdev >= 1.1.0])
  PKG_CHECK_MODULES(DRM_COMPOSITOR_GBM, [gbm >= 10.2],
                    [AC_DEFINE([HAVE_GBM_FD_IMPORT], 1, [gbm supports dmabuf import])],
                    [AC_MSG_WARN([gbm does not support dmabuf import, will omit that capability])])
fi

(From OE-Core rev: 73e9a5fc3234acda561f26cb915f4b636982ad63)

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoswig: fix gcc8 warnings for cast between incompatible function types
Yi Zhao [Wed, 15 Aug 2018 05:20:36 +0000 (13:20 +0800)] 
swig: fix gcc8 warnings for cast between incompatible function types

We got an error when building setools in meta-selinux:
setools/policyrep/qpol_wrap.c:1819:23:
error: cast between incompatible function types from 'PyObject * (*)(PyObject *)'
{aka 'struct _object * (*)(struct _object *)'} to 'PyObject * (*)(PyObject *, PyObject *)'
{aka 'struct _object * (*)(struct _object *, struct _object *)'} [-Werror=cast-function-type]
{(char *)"disown", (PyCFunction)SwigPyObject_disown, METH_NOARGS, (char *)"releases ownership of the pointer"},

This is a swig issue. See: https://github.com/swig/swig/issues/1259
Backport a patch from upstream to fix it.

(From OE-Core rev: f0f8ee668de34ad30ca16f5300966a3470018940)

Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agowic: bootimg-partition: Add support to create the u-boot boot config file
Kevin Hao [Tue, 14 Aug 2018 01:31:24 +0000 (09:31 +0800)] 
wic: bootimg-partition: Add support to create the u-boot boot config file

By leveraging the distro boot command feature in the u-boot, we can
compose the corresponding extlinux.conf when creating the wic image,
and let u-boot boot the kernel automatically. For more detail about
the u-boot distro boot command feature, please see doc/README.distro
in u-boot source files.

(From OE-Core rev: bdf8ae540af12ecc9ad60efd3651b0f71d12d3bd)

Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agowic: bootimg-partition: Add do_configure_partition() method
Kevin Hao [Tue, 14 Aug 2018 01:31:23 +0000 (09:31 +0800)] 
wic: bootimg-partition: Add do_configure_partition() method

We want to add some u-boot specific config file. Before doing this,
we need know what files will be installed into this partition. So
move the codes about parsing the IMAGE_BOOT_FILES into
do_configure_partition(). No function change.

(From OE-Core rev: 3203037471c761f635d1f1c512cb623ff6977a41)

Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agowic: bootimg-partition: Use the relative path in the install_task
Kevin Hao [Tue, 14 Aug 2018 01:31:22 +0000 (09:31 +0800)] 
wic: bootimg-partition: Use the relative path in the install_task

(From OE-Core rev: 3a85df7bde1e82cd508da8a78b930fa361a0e720)

Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agowic: Remove the unused variable Partition.sourceparams_dict
Kevin Hao [Tue, 14 Aug 2018 01:31:21 +0000 (09:31 +0800)] 
wic: Remove the unused variable Partition.sourceparams_dict

We choose to pass the source parameters to the source plugins' hooks
via a local variable srcparams_dict. So the Partition.sourceparams_dict
is not used by anyone and seems pretty confused. So drop it.

(From OE-Core rev: d7130a7d0e61021f71fec1d7ae7d37ebb27f0e03)

Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agopackage_manager: Add definitions for riscv machines
Richard Purdie [Wed, 15 Aug 2018 08:34:55 +0000 (09:34 +0100)] 
package_manager: Add definitions for riscv machines

Add definitions to the locale table for riscv architecture.

(From OE-Core rev: 624f6fd50da764cde71eb24e40742a48fa65d13c)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoref-manual: Removed misleading paragraph in siteinfo.bbclass
Yevgeny Popovych [Tue, 14 Aug 2018 17:32:24 +0000 (10:32 -0700)] 
ref-manual: Removed misleading paragraph in siteinfo.bbclass

The section on the siteinfo.bbclass file had a paragraph indicating
base.bbclass included siteinfo.class.  This is not true since
2010.  I removed the paragraph.

(From yocto-docs rev: 5d39220baddc9db5c1182cea8447e5c4a2e42bd8)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agodev-manual: Updated the section on CROPS
Scott Rifenbark [Fri, 10 Aug 2018 23:10:47 +0000 (16:10 -0700)] 
dev-manual: Updated the section on CROPS

Final edits to this section.  The procedure is more complete now.

(From yocto-docs rev: 5dcc32917c360e32475851b2b580d3d8bc988d7e)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agodev-manual: Updated link to "CROPS" to be to the GitHub area.
Scott Rifenbark [Thu, 9 Aug 2018 20:36:41 +0000 (13:36 -0700)] 
dev-manual: Updated link to "CROPS" to be to the GitHub area.

The original link was to a deprecated site.

(From yocto-docs rev: 067094d10a8d02d0873deb87508377e896e4f3c7)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agodev-manual, ref-manual: Updated available names for TEST_TARGET
Paulo Neves [Tue, 7 Aug 2018 22:01:17 +0000 (15:01 -0700)] 
dev-manual, ref-manual: Updated available names for TEST_TARGET

The documentation of available names for TEST_TARGET has been
updated to match the convention of using the class names of
controllers.

This commit was modified some to make it work.  Fixed some
formatting errors and isolated and changed missed instances.

(From yocto-docs rev: 1bec1dc38cdd1746ce6dd539f9c3e5665d12ab8e)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agodev-manual: Edits to section on setting up CROPS
Scott Rifenbark [Thu, 2 Aug 2018 23:05:26 +0000 (16:05 -0700)] 
dev-manual: Edits to section on setting up CROPS

Performed some edits to bring things in line for the "build host"
terminology.

(From yocto-docs rev: 4fedbdac437691b8a0f8d56931fcaad461c7463a)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agodocumentation: Changed section title for required packages.
Scott Rifenbark [Tue, 31 Jul 2018 22:51:15 +0000 (15:51 -0700)] 
documentation: Changed section title for required packages.

The title needs to use the terminology "Build Host" to be consistent
with the manual set.  I updated the title and the many links into that
section.

(From yocto-docs rev: 930030433e58e6180ee4f95e559d079c3899defc)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agodev-manual: Updates to "Setting Up a Native Linux Host"
Scott Rifenbark [Tue, 31 Jul 2018 22:32:06 +0000 (15:32 -0700)] 
dev-manual: Updates to "Setting Up a Native Linux Host"

I made some terminology changes to be consistent with the
"build host" term.

(From yocto-docs rev: 8e00f6453cbc470c7572f2c18e23e44ce18a7336)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agodev-manual: Adjusted "build host" wording.
Scott Rifenbark [Tue, 31 Jul 2018 22:19:29 +0000 (15:19 -0700)] 
dev-manual: Adjusted "build host" wording.

Fixed the "Preparing the Build Host" section to consistently use
the terminolgy "build host".

(From yocto-docs rev: 6199dde0611b4f077dfb2ad1ebdcc1414c4a081a)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agodev-manual: Added "recommended" for choosing native linux build host.
Scott Rifenbark [Tue, 31 Jul 2018 22:10:24 +0000 (15:10 -0700)] 
dev-manual: Added "recommended" for choosing native linux build host.

(From yocto-docs rev: cddc649590fc6cea74a0b78a584e00e22088541c)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agodocumentation: Fixed bad target ID for the dev-manual.
Scott Rifenbark [Tue, 31 Jul 2018 21:59:20 +0000 (14:59 -0700)] 
documentation: Fixed bad target ID for the dev-manual.

This fix involved a few other manuals.

(From yocto-docs rev: d2659951a458a8db773e8c1b2b86a7b109d667fa)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agodev-manual: Fixed typo in id anchor for a section heading.
Scott Rifenbark [Mon, 30 Jul 2018 22:36:18 +0000 (15:36 -0700)] 
dev-manual: Fixed typo in id anchor for a section heading.

(From yocto-docs rev: 05e6520843fda764f3090c7d681f8fdad5f80311)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agodev-manual: Updated team development environment section.
Scott Rifenbark [Mon, 30 Jul 2018 22:35:06 +0000 (15:35 -0700)] 
dev-manual: Updated team development environment section.

Found several areas that needed improvement.  Made these
modifications.

(From yocto-docs rev: e2125363d39b9a54a371fc737cc9b55d66c9be59)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agodev-manual: Updates to intro chapter.
Scott Rifenbark [Fri, 27 Jul 2018 20:46:46 +0000 (13:46 -0700)] 
dev-manual: Updates to intro chapter.

(From yocto-docs rev: a991415c8645a3ad31bf2dd20f932d7f3b4ebe18)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoref-manual: UPdates to the PNBLACKLIST variable description
Scott Rifenbark [Thu, 26 Jul 2018 22:45:43 +0000 (15:45 -0700)] 
ref-manual: UPdates to the PNBLACKLIST variable description

(From yocto-docs rev: c8a606dbce01132e95250c33270ff729cadc2c0e)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Minor intro wording change
Scott Rifenbark [Mon, 23 Jul 2018 21:39:41 +0000 (14:39 -0700)] 
sdk-manual: Minor intro wording change

(From yocto-docs rev: 953db3d0b5fe14411e944b021a2f6f50a5bdeabd)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoref-manual: Removed non-existant variable from PACKAGE_WRITE_DEPS description
Scott Rifenbark [Fri, 20 Jul 2018 16:15:10 +0000 (09:15 -0700)] 
ref-manual: Removed non-existant variable from PACKAGE_WRITE_DEPS description

Took out an occurrence of PACKAGE_WRITE_DEPENDS

(From yocto-docs rev: f7b2c7c08f3f504e14943a01e7fc0a73c96e9636)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Fixed bad anchor string.
Scott Rifenbark [Thu, 19 Jul 2018 23:24:28 +0000 (16:24 -0700)] 
sdk-manual: Fixed bad anchor string.

Broken link fixed.

(From yocto-docs rev: 420bc55ceac1d8c89f9153a70c8b4e3ca38d747d)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Updated section on minimizing eSDK installer size
Scott Rifenbark [Thu, 19 Jul 2018 22:12:12 +0000 (15:12 -0700)] 
sdk-manual: Updated section on minimizing eSDK installer size

I made some re-writes for clearity.

(From yocto-docs rev: a68619a2ba8b7877cde6c9ef7dbb726adc75b0cd)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Converted bullet list to ordered list
Scott Rifenbark [Thu, 19 Jul 2018 21:59:51 +0000 (14:59 -0700)] 
sdk-manual: Converted bullet list to ordered list

On second thought, the list I turned into a bullet list from the
previous commit was a bit hasty.  That list is order dependent.
Reverted the list.

(From yocto-docs rev: 9ea640ffea2a2c9827f18070a5b287453c8653e9)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Updated "Providing Additional Installable Extensible SDK Content"
Scott Rifenbark [Thu, 19 Jul 2018 21:54:50 +0000 (14:54 -0700)] 
sdk-manual: Updated "Providing Additional Installable Extensible SDK Content"

The list appears to be not a numbered list.  Fixed that.  Also, provided
better wording around "exposing" the sstate-cache.

(From yocto-docs rev: 15c65db41c9e6eddf7d12e138f6c63755e845beb)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Provided better wording for sharing HTTP or HTTPS server
Scott Rifenbark [Thu, 19 Jul 2018 21:29:14 +0000 (14:29 -0700)] 
sdk-manual: Provided better wording for sharing HTTP or HTTPS server

Step 1 of the "Providing Updates to the Extensible SDK After Installation"
section really did not do much for the reader regarding setting up a
HTTP or HTTPS directory.  I added more detail on how to generally do
that.

(From yocto-docs rev: ff250cea239668db5fe26aa912942c0d142833fa)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Edits to the section that changes the sdk title
Scott Rifenbark [Wed, 18 Jul 2018 21:08:37 +0000 (14:08 -0700)] 
sdk-manual: Edits to the section that changes the sdk title

Made some suggestions on how and where to edit the SDK_TITLE
variable.

(From yocto-docs rev: 4a4393e00c7108eefaaeaa3951a75524589bf360)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Updated section on changing SDK installer title.
Scott Rifenbark [Wed, 18 Jul 2018 20:23:27 +0000 (13:23 -0700)] 
sdk-manual: Updated section on changing SDK installer title.

I added more detail to this section.

(From yocto-docs rev: 15beb33eadd03391a1af0c9bad0620cefad2a0e2)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoref-manual: Updated the SDK_TITLE variable description
Scott Rifenbark [Wed, 18 Jul 2018 20:16:05 +0000 (13:16 -0700)] 
ref-manual: Updated the SDK_TITLE variable description

Provided more detail and a cross-reference into the SDK manual
where you can change the title through the variable.

(From yocto-docs rev: 9617fa70caef48328455a02d5260e536fac19c53)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Added section on changing the default ext. SDK install directory
Scott Rifenbark [Tue, 17 Jul 2018 22:50:14 +0000 (15:50 -0700)] 
sdk-manual: Added section on changing the default ext. SDK install directory

(From yocto-docs rev: d3f0c7b9e2ddea3fec6f42fc9a3c8806b02119f3)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoref-manual: Added SDKEXTPATH variable description.
Scott Rifenbark [Tue, 17 Jul 2018 21:38:42 +0000 (14:38 -0700)] 
ref-manual: Added SDKEXTPATH variable description.

This variable is the default installation directory for the
Extensible SDK.  By default, it is "poky_sdk".  You can override
this variable so it needed to be documented.  The ideal place to
override it is in the distribution configuration file.

(From yocto-docs rev: 67eca50fa973073ce6e7975ab66b89b9706c25c0)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Updates to sections for updating installed Ext SDKs
Scott Rifenbark [Mon, 16 Jul 2018 21:28:52 +0000 (14:28 -0700)] 
sdk-manual: Updates to sections for updating installed Ext SDKs

There are two sections that deal with this topic.  One is from the
standpoint of a user using a 3rd party published and installed
extensible SDK ("Applying Updates to an Installed Extensible SDK").
The other is from the standpoint of a person providing Extensible
SDKs for consumption ("Providing Updates to the Extensible SDK
After Installation").  These sections needed some closer examination
regarding fully describing what was going on.  I provided some
re-writes to both.

(From yocto-docs rev: 1c60b13b5f1813d6e3688e1efce32b7f31422e86)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Changed title to updating the SDK after install
Scott Rifenbark [Mon, 16 Jul 2018 20:22:10 +0000 (13:22 -0700)] 
sdk-manual: Changed title to updating the SDK after install

The title for the section on how to effect changes to an installed
extensible SDK is better suited as "Providing Updates to the
Extensible SDK AFter Installation."

(From yocto-docs rev: 2120ba194abada1769be28ae2737ac12a16adebc)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Fixed grammar error
Scott Rifenbark [Mon, 16 Jul 2018 20:15:43 +0000 (13:15 -0700)] 
sdk-manual: Fixed grammar error

In "Providing Updates After Installing the Extensible SDK" section,
Step 1 had a bit of a grammar error.  Not technically, but it
could have been written better.  I fixed that.

(From yocto-docs rev: 20f1cad5a813697afd99837699bf52a6586893bb)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Updated section on changing title of extensible SDK installer
Scott Rifenbark [Fri, 13 Jul 2018 19:25:58 +0000 (12:25 -0700)] 
sdk-manual: Updated section on changing title of extensible SDK installer

I added more information on how this is done.  Still could use a bit
of detail on how you actually do it.

(From yocto-docs rev: 007bbe40fd11a5f880adf7ad8137d1535f08c815)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoref-manual: Updated DISTRO_NAME variable description.
Scott Rifenbark [Fri, 13 Jul 2018 19:06:08 +0000 (12:06 -0700)] 
ref-manual: Updated DISTRO_NAME variable description.

I provided some real detail on this variable.  It was woefully brief.

(From yocto-docs rev: 4282fabddc81bf4c0fbd0a641ec4f1e9754660c2)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoref-manual: Updated the DISTRO variable description
Scott Rifenbark [Fri, 13 Jul 2018 18:55:32 +0000 (11:55 -0700)] 
ref-manual: Updated the DISTRO variable description

I added a cross-reference to the "DISTRO_NAME" variable as it is
the long version of the distribution name.

(From yocto-docs rev: bb5638409faadb9c6a5fbca729e4e6b8a220433d)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Grammar fix
Scott Rifenbark [Thu, 12 Jul 2018 20:11:24 +0000 (13:11 -0700)] 
sdk-manual: Grammar fix

(From yocto-docs rev: b850e0d520401a52fbba083975f05f529b2b554d)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Updates to "Adjusting the Extensible SDK to Suit Build Host"
Scott Rifenbark [Thu, 12 Jul 2018 18:35:05 +0000 (11:35 -0700)] 
sdk-manual: Updates to "Adjusting the Extensible SDK to Suit Build Host"

I updated this section with clearer text.

(From yocto-docs rev: 433388ff37297d905c465a5f05d93953dfe062c5)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Updates to "Configuring the Extensible SDK" section
Scott Rifenbark [Wed, 11 Jul 2018 22:42:57 +0000 (15:42 -0700)] 
sdk-manual: Updates to "Configuring the Extensible SDK" section

Made improvements to this section and tied the variables together
for the explanation.

(From yocto-docs rev: de882b81ed8525dee5e10f247cc6f5c8f15e0f72)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoref-manual: Fixed cross-reference wording in SDK_LOCAL_CONF_WHITELIST
Scott Rifenbark [Wed, 11 Jul 2018 22:40:25 +0000 (15:40 -0700)] 
ref-manual: Fixed cross-reference wording in SDK_LOCAL_CONF_WHITELIST

Wording did not match that of similar SDK variables.

(From yocto-docs rev: 696eb9ff0b89222dc696adc0bd28247c0a0c731a)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoref-manual: Fixed grammar error in SDK_INHERIT_BLACKLIST description
Scott Rifenbark [Wed, 11 Jul 2018 22:36:46 +0000 (15:36 -0700)] 
ref-manual: Fixed grammar error in SDK_INHERIT_BLACKLIST description

(From yocto-docs rev: 0a5775f7ad3e0b6531fcfd1d328d8e0da8727400)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoref-manual: Added cross-reference to SDK_LOCAL_CONF_BLACKLIST var
Scott Rifenbark [Wed, 11 Jul 2018 22:32:49 +0000 (15:32 -0700)] 
ref-manual: Added cross-reference to SDK_LOCAL_CONF_BLACKLIST var

Put in a cross-reference to the section in the sdk-manual where it
talks about customizing the configuration of the extensible SDK.

(From yocto-docs rev: 062db19dd56cc1827ebd7614eb8a54660421df62)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoref-manual: Updated the SDK_INHERIT_BLACKLIST variable description
Scott Rifenbark [Wed, 11 Jul 2018 22:28:52 +0000 (15:28 -0700)] 
ref-manual: Updated the SDK_INHERIT_BLACKLIST variable description

Added information on the class in which the default is set.  Also,
put in a reference for more information on customizing the
extensible SDK configuration.

(From yocto-docs rev: a0145996aeac1bb45fea9f613789b00327f92d1e)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoref-manual: Updated the SDK_LOCAL_CONF_WHITELIST variable description
Scott Rifenbark [Wed, 11 Jul 2018 22:09:07 +0000 (15:09 -0700)] 
ref-manual: Updated the SDK_LOCAL_CONF_WHITELIST variable description

Enhanced this description by indicating the class that it is set in
and by including a pointer back into the sdk-manual where filters
are described for extending the extensible SDK.

(From yocto-docs rev: 355b05366aadc337ec3337c0a3c918a23027923b)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoref-manual: Updated the SDK_LOCAL_CONF_BLACKLIST variable description
Scott Rifenbark [Wed, 11 Jul 2018 21:50:34 +0000 (14:50 -0700)] 
ref-manual: Updated the SDK_LOCAL_CONF_BLACKLIST variable description

Added more detail including the class that sets the default variables
for exclusion and the list of actual variables that are excluded by
default.

(From yocto-docs rev: f24287851998d554575c6aaf9dcc50d198931e48)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual, mega-manual: Updated the fig for installed ext. SDK
Scott Rifenbark [Tue, 10 Jul 2018 21:47:33 +0000 (14:47 -0700)] 
sdk-manual, mega-manual: Updated the fig for installed ext. SDK

This figure had changed.  I updated the file and folder hierarchy.

Also fixed some wording.

(From yocto-docs rev: 359292397781f9f5eac2fb693d89ec286ddf9940)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual, mega-manual: Updated standard SDK install directory figure
Scott Rifenbark [Tue, 10 Jul 2018 21:24:07 +0000 (14:24 -0700)] 
sdk-manual, mega-manual: Updated standard SDK install directory figure

The figure was incorrect for the installed file and folder hierarchy
for a standard SDK.  I updated it.  This figure goes in both the sdk-manual
and the mega-manual.

(From yocto-docs rev: a0dc11ce74bba0a18f385d9800f93524340ed033)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Final edits to the extracting root filesystem section
Scott Rifenbark [Tue, 10 Jul 2018 20:35:21 +0000 (13:35 -0700)] 
sdk-manual: Final edits to the extracting root filesystem section

Verified a good example and updated the text to match that example.

(From yocto-docs rev: 053467557ef22ce37762222a2997ff9c10be87e8)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosdk-manual: Added note in step to set SDKMACHINE
Scott Rifenbark [Mon, 9 Jul 2018 21:05:28 +0000 (14:05 -0700)] 
sdk-manual: Added note in step to set SDKMACHINE

The value of SDKMACHINE must match the architecture of the machine
on which the SDK installer is being built if you are building an
installer for an extensible SDK.  I added a note to this effect.

(From yocto-docs rev: ffdd9a9d00cccf270b5aa236279e6eeea0ff47ed)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agobitbake: utils/md5_file: don't iterate line-by-line
Ross Burton [Mon, 13 Aug 2018 18:02:25 +0000 (19:02 +0100)] 
bitbake: utils/md5_file: don't iterate line-by-line

Opening a file in binary mode and iterating it seems like the simple solution
but will still break on newlines, which for binary files isn't really useful as
the size of the chunks could be huge or tiny.

Instead, let's be a bit more clever: we'll be MD5ing lots of files, but we don't
want to fill up memory: use mmap() to open the file and read the file in 8k
blocks.

(Bitbake rev: a0ac8d67f1471a0c611d691b856fede67efb53f6)

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosystemd: fixes for the compatibility interface
Andrej Valek [Tue, 14 Aug 2018 10:21:19 +0000 (12:21 +0200)] 
systemd: fixes for the compatibility interface

Use a heap allocated string to set arg_ifname, since a stack allocated
one would be lost after the function returns. (This last one broke the
case where an interface name was suffixed with a dot, such as in
`resolvconf -a tap0.dhcp`.)

(From OE-Core rev: 48775d2f02d6d4024403796b81d6398f3028b965)

Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
Signed-off-by: Simon Ausserlechner <simon.ausserlechner@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agolinux-firmware: package Marvel usb 8997 firmware
Joshua Watt [Tue, 14 Aug 2018 20:01:51 +0000 (15:01 -0500)] 
linux-firmware: package Marvel usb 8997 firmware

Add package for the firmware required by the Marvell 8997 chipset when
connected over USB.

(From OE-Core rev: 650a33d88abfa42936b61465d2a4d42da53d4018)

Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agolibunwind: Fix build with musl+security flags
Khem Raj [Tue, 14 Aug 2018 19:21:34 +0000 (12:21 -0700)] 
libunwind: Fix build with musl+security flags

Fixes
src/os-linux.c:63: undefined reference to `__stack_chk_fail_local'

(From OE-Core rev: 43894faa45884dcc3b6111ed67e1a96fbec019a8)

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agomeson: Support building allarch recipes again
Peter Kjellerstedt [Tue, 14 Aug 2018 19:06:24 +0000 (21:06 +0200)] 
meson: Support building allarch recipes again

This registers "allarch" as a known CPU family.

(From OE-Core rev: f12b64e9332e3988953f87d8cea39ca309be5046)

Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agomeson: Split validate-cpu.patch in three
Peter Kjellerstedt [Tue, 14 Aug 2018 19:06:23 +0000 (21:06 +0200)] 
meson: Split validate-cpu.patch in three

This makes it more suitable to work with, e.g., devtool. It also
prepares for the update to 0.47.0 when the first patch will no longer be
needed (as it is a backport).

(From OE-Core rev: e1297f9a951b1dbafd0e211be63b348f06b1f3cd)

Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoeglinfo: Fix build with raspberrypi with userland graphics driver
Khem Raj [Tue, 14 Aug 2018 16:32:43 +0000 (09:32 -0700)] 
eglinfo: Fix build with raspberrypi with userland graphics driver

Let pkgconfig figure out headers and libraries instead of manually
forcing waf to do it.

(From OE-Core rev: 283026adda7c184e213dacd7f4e42678c304866a)

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agomusl: Fix dirent struct alignment issue seen on armv5te
Khem Raj [Tue, 14 Aug 2018 16:32:42 +0000 (09:32 -0700)] 
musl: Fix dirent struct alignment issue seen on armv5te

- its a general problem however observed on armv5te based boards in OE
  other arches either have ways to compensate for misaligned access in hardware
  or compiler does not use 8byte alignment

- fix internal linux headers

Full logs
https://git.musl-libc.org/cgit/musl/log/?qt=range&q=9cad27a3dc1a4eb349b6591e4dc8cc89dce32277..1ad8138819ced49851e618c9c063aa0ffc86718c

(From OE-Core rev: 5fb668482e06ecd5de70a860d1bb9cef1019c4e8)

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agorunqemu: exit gracefully with an error message if qemu system is not evaluated
Jagadeesh Krishnanjanappa [Tue, 14 Aug 2018 14:35:29 +0000 (20:05 +0530)] 
runqemu: exit gracefully with an error message if qemu system is not evaluated

It solves below error:
-- snip --
return 'qemu-system-%s' % qbsys
UnboundLocalError: local variable 'qbsys' referenced before assignment
-- snip --

[YOCTO #12846]

(From OE-Core rev: 519273f54c0b8a6fff36afeb7646d8e37717be22)

Signed-off-by: Jagadeesh Krishnanjanappa <jkrishnanjanappa@mvista.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agopcmciautils: remove from oe-core
Ross Burton [Tue, 14 Aug 2018 13:09:28 +0000 (14:09 +0100)] 
pcmciautils: remove from oe-core

PCMCIA is pretty rare these days, so now that the recipe is in meta-oe we can
remove it from oe-core.

(From OE-Core rev: 0f8dcb9c717201c4b1edf4fa55880b432bfb7723)

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agomesa: Disble TLS for musl
Khem Raj [Tue, 14 Aug 2018 18:34:40 +0000 (11:34 -0700)] 
mesa: Disble TLS for musl

See https://bugs.freedesktop.org/show_bug.cgi?id=35268
mesa should infact stop using __attribute__((tls_model("initial-exec")))
until then we disale TLS in glx for musl
The problem could happen even on glibc if static TLS sizes are large enough
which would mean that additional space the glibc leaves for such rogue libraries
get consumed and then same problems show up there as well

Fixes errors seen in xorg logs e.g.

(EE) Failed to load /usr/lib/xorg/modules/extensions/libglx.so: Error relocating /usr/lib/libGL.so.1: _ITM_deregisterTMCloneTable: initial-exec TLS resolves to dynamic definition in /usr/lib/libGL.so.1

enable readonly text segment on x86 for musl

(From OE-Core rev: f3a59540d0d1f7ab42ba7cb5ff1a26ac3a8a9f68)

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoselftest/package: Improve test to cover sparseness and hardlinking from sstate
Richard Purdie [Tue, 14 Aug 2018 17:24:14 +0000 (17:24 +0000)] 
selftest/package: Improve test to cover sparseness and hardlinking from sstate

The sparseness test was sometimes working and sometimes failing depending
on whether sstate was valid. This adds an explict test of sstate
to the test for both hardlinking and sparseness. Tweak the test name to
cover the fact its tests sparseness too.

(From OE-Core rev: fe5b37c07b6d07c350516ab6bf849d6d86a84004)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosstate/lib.oe.path: Ensure file sparseness is preserved
Richard Purdie [Tue, 14 Aug 2018 17:23:10 +0000 (17:23 +0000)] 
sstate/lib.oe.path: Ensure file sparseness is preserved

Files when restored from sstate were missing their sparseness. Fix up various
functions to preserve this and make things more deterministic.

(From OE-Core rev: 055402e5504f041c346571e243c7cf0894955cad)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoselftest: Replace bitbake -p with bitbake -e
Richard Purdie [Tue, 14 Aug 2018 17:20:57 +0000 (17:20 +0000)] 
selftest: Replace bitbake -p with bitbake -e

Parsing all the recipes is annoying when trying to re-execute oe-selftest
and also unnecessary as its really just a sanity check. When the tests were
originally being developed the guard was useful but less so now.

Replace it with bitbake -e which is fast and checks the basic configuration
is valid.

(From OE-Core rev: acec5180b8d2731002979179e08439b615631e70)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agosstate: Ensure a given machine only removes things which it created
Richard Purdie [Tue, 14 Aug 2018 14:56:00 +0000 (14:56 +0000)] 
sstate: Ensure a given machine only removes things which it created

Currently if you build qemux86 and then generic86, the latter will
remove all of the former from deploy and workdir. This is because
qemux86 is i586, genericx86 is i686 and the architctures are compatible
therefore the sstate 'cleaup' code kicks in.

There was a valid reason for this to ensure i586 packages didn't get into
an i686 rootfs for example. With the rootfs creation being filtered now, this
is no longer necessary.

Instead, save out a list of stamps which a give machine has ever seen in
a given build and only clean up these things if they're no longer
"reachable".

In particular this means the autobuilder should no longer spend a load of time
deleting files when switching MACHINE, improving build times.

(From OE-Core rev: 5634f2fb1740732056d2c1a22717184ef94405bf)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agopackage_manager/sdk: Use filtered copies of the deploy ipk/deb directories
Richard Purdie [Tue, 14 Aug 2018 15:18:16 +0000 (15:18 +0000)] 
package_manager/sdk: Use filtered copies of the deploy ipk/deb directories

Similar to rpm, use copies of the ipk/deb directories for rootfs construction.
This means the image creation code can no longer "see" recipes wich aren't in its
dependency chain which is good for a variety of reasons including determinism,
incompatible recipe (e.g. systemd/sysvinit) package conflicts and locking
performance.

(From OE-Core rev: c7c5f4065c102fde4e11d138fb0b6e25bffe0379)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agopackage_manager: Remove rpm specific pieces of create_packages_dir()
Richard Purdie [Tue, 14 Aug 2018 14:55:42 +0000 (14:55 +0000)] 
package_manager: Remove rpm specific pieces of create_packages_dir()

This function is generic, tweak the variable names and move out the rpm specific
directory name to make it truly generic and reusable for deb/ipk.

(From OE-Core rev: dba876639b1fb8ea3ccb182c91e19966c4052115)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoglibc: Fix locale archive path patch
Richard Purdie [Mon, 13 Aug 2018 12:44:05 +0000 (12:44 +0000)] 
glibc: Fix locale archive path patch

The locale code uses the archive location in two places, ensure both are
corrected to use the environment variable which avoids nasty build
failures when archiving locales in images.

(From OE-Core rev: 3ab1249a2ac92a0fcb008e92cc9ee272441408f4)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoimage: Add locale archive optimisation
Richard Purdie [Mon, 13 Aug 2018 11:40:03 +0000 (11:40 +0000)] 
image: Add locale archive optimisation

Refactor the locale archive function from the SDK to also make it work during
general image creation. This reduces the size of the locales from 900MB to 220MB
in core-image-lsb-sdk.

The exception handling around subprocess was dropped as the standard subprocess
exception printing is better handled than the catchall exception.

(From OE-Core rev: 8ffd93bdb09b0a4a84b27dafcd684c6abba392ed)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoselftest/package: Add test to ensure sparse files are preserved
Richard Purdie [Sun, 12 Aug 2018 22:29:18 +0000 (22:29 +0000)] 
selftest/package: Add test to ensure sparse files are preserved

Add a new element to the hardlink test to check we also preseve file
sparseness during the packing process. This should ensure we don't regress this
issue again.

(From OE-Core rev: 0a4e6974b49bf68c4a4098d339b5d655e202a3fd)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoxf86-video-intel: Fix for glibc
Richard Purdie [Sat, 11 Aug 2018 16:07:18 +0000 (16:07 +0000)] 
xf86-video-intel: Fix for glibc

It fails to build wi9th glibc 2.28, add the missing required header inclusion.

(From OE-Core rev: 8f5f23a5a985f5d48973f27c143b0d5edb8ca797)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoscreen: Add virtual/crypt dependency
Richard Purdie [Sat, 11 Aug 2018 16:06:54 +0000 (16:06 +0000)] 
screen: Add virtual/crypt dependency

screen uses crypt() so add the missing DEPENDS triggered by glibc 2.28.

(From OE-Core rev: 77ca6be2bcac35a54546b0b468a4d68e8cc8b894)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
6 years agoglibc: Add make-native depends
Richard Purdie [Sat, 11 Aug 2018 10:30:28 +0000 (11:30 +0100)] 
glibc: Add make-native depends

glibc needs make >= 4 yet some of our build workers have older versions of
make. Add a make-native dependency to work around this until all our supported
distros have a recent version of make.

(From OE-Core rev: 0cd89e4af625941f8ab8c033f72f900a2979b304)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>