linux/poky.git, branch uninative-2.3

oe-selftest: devtool: Support meta being a symbolic link

2018-10-21T20:30:35+00:00

oe-selftest's devtool tests have been broken since commit 2457cd57 (oe-selftest: devtool: avoid parallel races by using temporary copy of core) if meta is a symbolic link. (From OE-Core rev: daba6c5a991b370709d17e51305334f55a3858ec) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

tcmode-default: Drop pinning go to 1.9

2018-10-21T20:30:35+00:00

This ensures that we default to latest go recipes 1.9 is not supported anymore (From OE-Core rev: d48c8148eae41e613448d78c26516538244cd9c9) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

systemd: Remove items that made this machine (qemu) specific

2018-10-21T20:30:35+00:00

Create a new systemd-conf recipe to contain the specific system/machine configuration items. This new package is now machine specific. Without doing this trying to create a single system with multiple BSPs, one of which was qemu based, would result in the systemd -and- everything that dependend upon systemd to have their hash changed. The hash changing means lots of rebuilds, but worse if it's a package based system each different machine ends with a new PR value and a newly generated package. (From OE-Core rev: d3395418758ed414eee3e95e13d2d8bc5dca88cc) Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie

linux-yocto: update genericx86* SRCREV for 4.18

2018-10-20T21:40:51+00:00

Bump to kernel release v4.18.14. (From meta-yocto rev: 7cf931279918affe77330f7803e57678c33f5e51) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

linux-yocto: update genericx86* SRCREV for 4.14

2018-10-20T21:40:51+00:00

Bump to kernel release v4.14.76. (From meta-yocto rev: e864c929738fcd07e1b2a2d1e04800d82030b4a5) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

valgrind: update from 3.13.0 to 3.14.0

2018-10-20T21:40:16+00:00

The removed patches are all upstream. Adjusted two patches due to rebase. Guard against __GLIBC_PREREQ for musl libc (From OE-Core rev: 37841ec56d7756ec9ee00e2a2005681b220f6f5d) Signed-off-by: Randy MacLeod Signed-off-by: Richard Purdie

volatile-binds: use overlayfs if available

2018-10-20T21:40:16+00:00

Copying files from the read-only root filesystem to the tmpfs providing the volatile directories can be slow and waste memory. If the kernel supports the overlay filesystem, use it to mount a writable tmpfs on top of the read-only directory from the rootfs and avoid copies. Analogous to the modification made to initscripts's read-only-rootfs-hook in 370fda1b2e8d5dc011522131bba4106de26bfb19. (From OE-Core rev: b4976f3cf8cd028f165100b67867adb862da4d7f) Signed-off-by: Matt Hoosier Signed-off-by: Richard Purdie

openssl: do an out-of-tree build

2018-10-20T21:40:16+00:00

OpenSSL supports out-of-tree builds so we should use them. This makes builds more reliable, and makes it easier to reduce the size of the ptest package. (From OE-Core rev: e028b4457781f60d8491a99a23011996fa913013) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

openssl: fix ptest

2018-10-20T21:40:16+00:00

Previously the ptest installation was simply a copy of the entire build tree, which is terribly ugly. Instead copy just the pieces we need, symlink to /usr as appropriate, and add missing dependencies. Remove PRIVATE_LIBS as we don't ship copies of the libraries now. Also remember to do 'set -x' in run-ptest, so if the tests fail the runner knows! [ YOCTO #12965 ] [ YOCTO #12967 ] (From OE-Core rev: 7831d2d3a1069b9d3a8d32e41f0a292e1add56ba) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

npm: change install directory to upstream default

2018-10-20T21:40:16+00:00

The node binary searches for packages in a number of locations, the last of which is $PREFIX/lib/node (here: /usr/lib/node) from the list of GLOBAL_FOLDERS [1]. Change the installation directory for all packages depending on npm.bbclass to that location. This removes the need to define the NODE_PATH variable to the non-standard /usr/lib/node_modules value. While the Tips for Package Managers [2] discusses installing packages to /usr/lib/node_modules//, this has several drawbacks: * it does not work for the REPL as mentioned in the documentation * it also does not work for any code _not_ installed as a global package under /usr/lib/node_modules (e.g. /usr/share/foo.js will not find any packages below /usr/lib) * using the non-default location and then having to set NODE_PATH barely saves any time: there are only two file-system lookups (to the legacy $HOME/.node_modules and $HOME/.node_libraries) directories before the library would be found And the suggestion was made in the context of deduping the node_modules tree by installing all packages in a flat hierarchy and using symlinks to the correct version of each dependency. This is not what OpenEmbedded does, so none of those benefits (deduping, cleaner packages) are being had by shifting the installation directory to /usr/lib/node_modules. [1]: https://nodejs.org/api/modules.html#modules_loading_from_the_global_folders [2]: https://nodejs.org/api/modules.html#modules_addenda_package_manager_tips (From OE-Core rev: 2036137151929b541293154ff529475071cd92b0) Signed-off-by: Olaf Mandel Signed-off-by: Richard Purdie