openembedded-core.git/meta/recipes-devtools, branch master

python3-iniparse: fix upstream version check

2017-04-28T10:26:07+00:00

Signed-off-by: Alexander Kanavin 
Signed-off-by: Ross Burton

rpm: properly relocate additional native tools

2017-04-28T10:26:06+00:00

These tools are not currently used for anything, but we should
still provide working versions of them.

[YOCTO #11400]

Signed-off-by: Alexander Kanavin 
Signed-off-by: Ross Burton

pseudo: Backport two upstream fixes

2017-04-14T09:09:56+00:00

Backport fixes from pseudo master for an acl issue and more importantly, a segfault
issue with bash which can be triggered by the recent useradd changes.

Signed-off-by: Richard Purdie

Revert "dnf: remove systemd units in nativesdk builds"

2017-04-13T22:58:14+00:00

nativesdk builds now control the DISTRO_FEATURES (oe-core 731744) so this
workaround is no longer required.

This reverts commit 415b72ffcbd26e5f3664370d8b2a9b8105fb6342.

Signed-off-by: Ross Burton

apt: fix libdir path for apt.systemd.daily

2017-04-13T22:57:37+00:00

It should be ${libdir} rather than /usr/lib, otherwise it would fail
when multilib:

MACHINE = "qemux86-64"
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"

$ bitbake apt
[snip]
install: target /path/to/apt/1.2.12-r0/image/usr/lib/apt is not a directory: No such file or directory
[snip]

Signed-off-by: Robert Yang 
Signed-off-by: Richard Purdie

base-passwd/useradd: Various improvements to useradd with RSS

2017-04-13T22:57:37+00:00

Currently there are multiple issues with useradd:

* If base-passwd rebuilds, it wipes out recipe specific user/group additions
  to sysroots and causes errors
* If recipe A adds a user and recipe B depends on A, it can't see any of the
  users/groups A adds.

This patch changes base-passwd so it always works as a postinst script
within the sysroot and copies in the master files, then runs any
postinst-useradd-* scripts afterwards to add additional user/groups.

The postinst-useradd-* scripts are tweaked so that if /etc/passwd doesn't exist
they just exit, knowning they'll be executed later. We also add a dummy entry to
the dummy passwd file from pseudo so we can avoid this too.

There is a problem where if recipe A adds a user and recipe B depends on A but
doesn't care about users, it may not have a dependency on the useradd/groupadd
tools which would therefore not be available in B's sysroot. We therefore also
tweak postinst-useradd-* scripts so that if the tools aren't present we simply
don't add users. If you need the users, you add a dependency on the tools in the
recipe and they'll be added.

We add postinst-* to SSTATE_SCAN_FILES since almost any postinst script of this
kind is going to need relocation help.

We also ensure that the postinst-useradd script is written into the sstate
object as the current script was only being added in a recipe local way.

Thanks to Peter Kjellerstedt  and Patrick Ohly for some pieces
of this patch.

[Yocto #11124]

Signed-off-by: Richard Purdie

qemu-helper-native: prepare native sysroot for runqemu

2017-04-12T22:55:54+00:00

Make sure that native sysroot contains qemu and tunctl binaries for
runqemu usage:
  - excluded native sysroot from rm_work
  - added qemu-native to DEPENDS to put qemu binaries into native sysroot
  - forced addto_recipe_sysroot task

[YOCTO #11266]
[YOCTO #11193]

Signed-off-by: brian avery 
Signed-off-by: Ed Bartosh 
Signed-off-by: Richard Purdie

recipes/*-cross recipes: ignore TARGET_ARCH sstate hash

2017-04-12T14:02:13+00:00

"yocto-compat-layer.py --machines" showed that shared packages like
gcc-cross-powerpc64 have a sstate signature that depends on
TUNEFLAGS. As a result, there are unnecessary rebuilds and potential
conflicts in a multiconfig.

That's due to the way how TARGET_ARCH is set. Richard Purdie suggested
setting TARGET_ARCH[vardepvalue] as fix, which works. It would be
shorter to do that in cross.bbclass instead of repeating the relevant
line in different recipes, but Richard was concerned about potential
side-effects in other usages of cross.bbclass.

TARGET_GOARM as used in go.inc is still causing signature differences
for go-cross-powerpc64 and machines b4420qds-64b and p5020ds-64b. This
needs further investigation.

Signed-off-by: Patrick Ohly 
Signed-off-by: Richard Purdie

gdb-cross: avoid tune specific paths

2017-04-12T14:02:13+00:00

gdb-cross used to be specific to the tune flags, but isn't
anymore. Therefore it is enough to use TARGET_SYS instead of
TUNE_PKGARCH to create a unique path.

Fixes a sstate signature difference that was found via
yocto-compat-layer.py's test_machine_signatures check. In practice it
probably showed up as unnecessarily rebuilding gdb-cross when
switching between machines like intel-corei7-64 and qemux86-64.

Signed-off-by: Patrick Ohly 
Signed-off-by: Richard Purdie

go-cross: avoid libgcc dependency

2017-04-12T14:02:13+00:00

libgcc gets compiled differently depending on the tune flags for the
target. That dependency would make go-cross also tune specific and
prevent sharing it between different machines using the same
architecture.

For example, MACHINE=intel-corei7-64 and MACHINE=qemux86-64 shared the
same go-cross-x86_64, but compiled libgcc differently.

The libgcc dependency gets inherited from go.inc, but does not seem to
be necessary for go-cross (compiling go-helloworld still succeeds).
The dependency is left in go.inc conditionally, just in case that it
really is relevant for the various on-target recipes which inherit
that.

Because go-cross*.bb includes go*.bb, moving the DEPENDS into a .inc
file that only gets included for the target recipes doesn't
work. Reshuffling the content of three .bb files seems too intrusive
at this point.

Signed-off-by: Patrick Ohly 
Signed-off-by: Richard Purdie