diff options
| author | Khem Raj <raj.khem@gmail.com> | 2015-08-15 15:04:31 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-08-30 12:35:56 +0100 |
| commit | 06b97accfe6b13f31c63cc850bdcdebf8b4da24a (patch) | |
| tree | 1200b1e996bf3dadd672d8219261682014e7a9f0 /meta/conf/bitbake.conf | |
| parent | 2a9cf4d0a769300878c5c670f496a62b64a71c18 (diff) | |
| download | poky-06b97accfe6b13f31c63cc850bdcdebf8b4da24a.tar.gz | |
systemd: Cache/define tool paths for target
Recently, systemd has added a patch
f00929ad622c978f8ad83590a15a765b4beecac9
where it now pokes at the system to find
out the path of mount/umount tools, this caused the builds to fail
because it ended up with identifying these programs from native sysroot
but they were actually meant for target, this lead to boot failures due
to none of mount worked because the paths are encoded into systemd
binaries during build time.
Correct few others while here, these are not yet detected wrongly in my
build, because those binaries are not found in my native sysroot but if
some one staged the native providers of these packages they will fail too.
(From OE-Core rev: 9d87fbc87276673d958a65d476d06fec96add8e7)
(From OE-Core rev: b30d7b1b97ffd1d44083d93ed0e572d80fcebc54)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/conf/bitbake.conf')
0 files changed, 0 insertions, 0 deletions