Age | Commit message (Collapse) | Author |
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This reverts commit d2f12c16738e1e122d3723e3f2f3e42c1f2ffbf4.
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This reverts commit 5eafbb17fddf04b6f4c1b4d3f8b5c213355e2d97.
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This reverts commit 185a1ba5f842fdb6cb640380638351c7a1870d2c.
|
|
listed in pseudo.log"
This reverts commit 1fca4418a47dee3ee884d93419ab05cd4dd16cdf.
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
There are some cases where we need a single BuildCompleted event, not
the multiple events that multiconfig has required. Add such a single
event (see my previous changes to the BuildStarted/BuildComplete events
to understand why we need to fire those for each multiconfig).
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
The top level LICENSE file is not actually a license, it refers
other licenses that are used by Bitbake and Meta-data. Relying
on this file could cause problems for recipes when this file
changes, which it is about to.
(From OE-Core rev: a1948ab38c9cb7f0b16cce9dadc03ae6e2fe44ad)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
It was required only by oprofile.
(From OE-Core rev: 78bfa5fb52c292b71caddab85c6acc50a549fe97)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Perf is the preferred solution, and oprofile is difficult to
maintain against musl.
(From OE-Core rev: c3db8bc1ccac7ca8db38b1e61044b61ce964bc72)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
There was a race condifion in externalsrc_configure_prefuncs when the
same source folder is used for several variants of the same recipe,
like this:
EXTERNALSRC_pn-foo = "..."
EXTERNALSRC_pn-foo-native = "..."
The symlinks were created once for each variant of the recipe, and
where they led in the end depended on which do_configure task executed
last. Create one set of symlinks for each variant by adding an EXTSRC_SUFFIX
variable to the end of the link names.
Tries to handle all known virtclasses and multilib variants.
Use a lockfile for externalsrc_configure_prefuncs to protect the
.git/info/exclude file.
(From OE-Core rev: 7cd896735f93f206314afb28c8c1286f775aa804)
Signed-off-by: Ola x Nilsson <olani@axis.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
in pseudo.log
* we often see QA warnings like:
glibc-locale-2.26: glibc-locale: /glibc-binary-localedata-en-gb/usr/lib/locale/en_GB/LC_MEASUREMENT is owned by uid 3004, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
glibc-locale-2.26: glibc-locale: /glibc-binary-localedata-nn-no.iso-8859-1/usr/lib/locale/nn_NO.ISO-8859-1/LC_MEASUREMENT is owned by uid 3004, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
but we don't know the root cause of it.
* the only theory we currently have is that it's a bug in pseudo when
inode is being reused for different files, which is supported by
pseudo.log entries:
Good build:
pseudo$ grep -v "^path mismatch" pseudo.log
debug_logfile: fd 2
pid 7975 [parent 7974], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 7974.
db cleanup for server shutdown, 17:33:58.787
memory-to-file backup complete, 17:33:58.787.
db cleanup finished, 17:33:58.787
Build with QA host-user-contaminated issue:
ERROR: foo-1.0.0-r0 do_package_qa: QA Issue: foo: file-with-wrong-UID is owned
by uid 2001, which is the same as the user running bitbake. This may be due to
host contamination [host-user-contaminated]
pseudo$ grep "file-with-wrong-UID" pseudo.log
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
creat ignored for existing file 'file-with-wrong-UID'.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
path mismatch [1 link]: ino 13242270 db 'file-with-wrong-UID' req 'some-other-unrelated-file'.
creat for 'some-other-unrelated-file' replaces existing 13242270 ['file-with-wrong-UID'].
db cleanup for server shutdown, 02:16:23.685
memory-to-file backup complete, 02:16:23.685.
db cleanup finished, 02:16:23.685
And some-other-unrelated-file is really some different file, not just hardlink
to the same file from some different directory (like between WORKDIR and sysroot
other "path mismatch" entries show).
(From OE-Core rev: 803b18e399c22e0a1379e92b47df58197554d65d)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
listed in pseudo.log"
This reverts commit a4c2068c536f1fff585e5f94166a78e158cd52f1.
|
|
in pseudo.log
* we often see QA warnings like:
glibc-locale-2.26: glibc-locale: /glibc-binary-localedata-en-gb/usr/lib/locale/en_GB/LC_MEASUREMENT is owned by uid 3004, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
glibc-locale-2.26: glibc-locale: /glibc-binary-localedata-nn-no.iso-8859-1/usr/lib/locale/nn_NO.ISO-8859-1/LC_MEASUREMENT is owned by uid 3004, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
but we don't know the root cause of it.
* the only theory we currently have is that it's a bug in pseudo when
inode is being reused for different files, which is supported by
pseudo.log entries:
Good build:
pseudo$ grep -v "^path mismatch" pseudo.log
debug_logfile: fd 2
pid 7975 [parent 7974], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 7974.
db cleanup for server shutdown, 17:33:58.787
memory-to-file backup complete, 17:33:58.787.
db cleanup finished, 17:33:58.787
Build with QA host-user-contaminated issue:
ERROR: foo-1.0.0-r0 do_package_qa: QA Issue: foo: file-with-wrong-UID is owned
by uid 2001, which is the same as the user running bitbake. This may be due to
host contamination [host-user-contaminated]
pseudo$ grep "file-with-wrong-UID" pseudo.log
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
creat ignored for existing file 'file-with-wrong-UID'.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
path mismatch [1 link]: ino 13242270 db 'file-with-wrong-UID' req 'some-other-unrelated-file'.
creat for 'some-other-unrelated-file' replaces existing 13242270 ['file-with-wrong-UID'].
db cleanup for server shutdown, 02:16:23.685
memory-to-file backup complete, 02:16:23.685.
db cleanup finished, 02:16:23.685
And some-other-unrelated-file is really some different file, not just hardlink
to the same file from some different directory (like between WORKDIR and sysroot
other "path mismatch" entries show).
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
listed in pseudo.log"
This reverts commit ef225fc591aa29ec81b93ee87df1adaea31385c8.
|
|
in pseudo.log
* we often see QA warnings like:
glibc-locale-2.26: glibc-locale: /glibc-binary-localedata-en-gb/usr/lib/locale/en_GB/LC_MEASUREMENT is owned by uid 3004, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
glibc-locale-2.26: glibc-locale: /glibc-binary-localedata-nn-no.iso-8859-1/usr/lib/locale/nn_NO.ISO-8859-1/LC_MEASUREMENT is owned by uid 3004, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
but we don't know the root cause of it.
* don't trigger error from '^inode mismatch'
* show parts of pseudo.log in console
many builds are executed in tmpfs, so I cannot check the pseudo.log later
* lower from error to warn as I hate all my builds reporting failure
just because of this pseudo debug
* the only theory we currently have is that it's a bug in pseudo when
inode is being reused for different files, which is supported by
pseudo.log entries:
Good build:
pseudo$ grep -v "^path mismatch" pseudo.log
debug_logfile: fd 2
pid 7975 [parent 7974], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 7974.
db cleanup for server shutdown, 17:33:58.787
memory-to-file backup complete, 17:33:58.787.
db cleanup finished, 17:33:58.787
Build with QA host-user-contaminated issue:
ERROR: foo-1.0.0-r0 do_package_qa: QA Issue: foo: file-with-wrong-UID is owned
by uid 2001, which is the same as the user running bitbake. This may be due to
host contamination [host-user-contaminated]
pseudo$ grep "file-with-wrong-UID" pseudo.log
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
creat ignored for existing file 'file-with-wrong-UID'.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
inode mismatch: 'file-with-wrong-UID' ino 13242270 in db, 13242271 in request.
path mismatch [1 link]: ino 13242270 db 'file-with-wrong-UID' req 'some-other-unrelated-file'.
creat for 'some-other-unrelated-file' replaces existing 13242270 ['file-with-wrong-UID'].
db cleanup for server shutdown, 02:16:23.685
memory-to-file backup complete, 02:16:23.685.
db cleanup finished, 02:16:23.685
And some-other-unrelated-file is really some different file, not just hardlink
to the same file from some different directory (like between WORKDIR and sysroot
other "path mismatch" entries show).
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
lld and gold can not handle it and treat it wrong
Fixes
[YOCTO #11689]
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
Force items into packagegroup-core-tools-profile? I don't think so.
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
|
|
|
|
When tinfoil request a command to bitbake is handled in async
manner [1], sometimes is this ends on return a Busy status.
This is a workaround a needs to be fixed in proper manner
inside bitbake code.
For example when running clientComplete and buildFile is on progress,
ERROR: Function failed: base_do_unpack
Traceback (most recent call last):
File "/home/alimon/repos/poky/scripts/lib/devtool/standard.py", line
797, in modify
initial_rev = _extract_source(srctree, args.keep_temp, args.branch,
False, rd, tinfoil)
File "/home/alimon/repos/poky/scripts/lib/devtool/standard.py", line
562, in _extract_source
runtask(fn, 'unpack')
File "/home/alimon/repos/poky/scripts/lib/devtool/standard.py", line
552, in runtask
raise DevtoolError('Task do_%s failed' % task)
devtool.DevtoolError: Task do_unpack failed
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/alimon/repos/poky/scripts/devtool", line 351, in <module>
ret = main()
File "/home/alimon/repos/poky/scripts/devtool", line 338, in main
ret = args.func(args, config, basepath, workspace)
File "/home/alimon/repos/poky/scripts/lib/devtool/standard.py", line
864, in modify
tinfoil.shutdown()
File "/home/alimon/repos/poky/bitbake/lib/bb/tinfoil.py", line 427, in
shutdown
self.run_command('clientComplete')
File "/home/alimon/repos/poky/bitbake/lib/bb/tinfoil.py", line 320, in
run_command
raise TinfoilCommandFailed(result[1])
bb.tinfoil.TinfoilCommandFailed: Busy (buildFile in progress)
(Bitbake rev: c75990aa8c13305d0f3efeaa817fdc6fc563eb98)
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Currently do_rootfs gets to see all rpms in the deploy directory. This filters
that view to only rpms which the image recipe has actual depends upon which
potentially removes some sources of confusion in the image construction.
(From OE-Core rev: eabed5913f7b3b6a98a4ed8bdd72832059668e03)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Upgrade to a new stable release and drop patches applied on upstream.
For a full release notes, please see:
https://mesa3d.org/relnotes/17.2.0.html
https://mesa3d.org/relnotes/17.2.1.html
(From OE-Core rev: f537fea5aeb88eaf7d4f8ab159631e39c179946d)
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Bugfixes only release.
(From OE-Core rev: 25772447a56f8f007aaad30643fca1635a7d4d3e)
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
* Bugfixes only release.
* Removed SRC_URI from .inc file since it was duplicated in .bb file as well.
(From OE-Core rev: e13826296ee4ec06087d006d61a8e8639228bd81)
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Bugfixes only release.
(From OE-Core rev: 69d0068aaf71227b8a4870cd9f7dbf3fead620cc)
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Bugfixes only release.
(From OE-Core rev: 49c2d6fa3b91c80ef4109ae87f1d4d35c64b06f1)
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Bugfixes release only.
(From OE-Core rev: 144dada6cd075f9ef16c2c5532f0b52a23afbfaa)
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Bugfixes only release.
(From OE-Core rev: 51b6af74846532d222820d2d5402c970cb2b8527)
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Bugfixes only release.
(From OE-Core rev: 7da060990eb0bd53d6490eef833f7653c04e10d4)
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Patch removed since it is already upstream now.
Bugfixes release only.
(From OE-Core rev: ee1b63e379c7c2521d8fb8a44d6ce66b2fe0b271)
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Bugfixes release only.
(From OE-Core rev: 4537a52c11fe24fef7da40675ae70b9e921bdc5f)
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Bugfixes release only. Removed local patch which was merged upstream.
(From OE-Core rev: 16b7ac03a97f725395efecfeefb57e408f8d2ee0)
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
on mips, cgo used mips32r1 and that conflicts with mips32r2
lets remove it for now and work go upstream to make it work
for golang as well
Fixes
| # runtime/cgo
| cc1: error: '-mips32r2' conflicts with the other architecture options, which specify a mips32 processor
Fixes [YOCTO #12108]
(From OE-Core rev: 430f1c3fba5387583599647fd376af7bd3eb641f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Since systemd-boot is a bootloader, it needs to be built for
the native IA instruction set size and x32 is not valid.
(From OE-Core rev: ccef7979afe03faa519effb6e3ce53b5dfb87b89)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Currently systemd-boot actually incorporates libgcc, since the
systemd-boot needs to be built with 64bit instructions it can not
use the x32 based libgcc.
Use the new override to ensure it gets overriden, linux-gnux32 could
not be used because x86-64 has higher priority.
(From OE-Core rev: 8d92848d88af07092bf8827edff72935c602d459)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This is needed as an x32 more generic x32 override later in the
OVERRIDES, currently linux-gnux32 is the first override, but we
need a stronger (later in the list) x32 override to deal with some
needed x32 dependency overrides.
(From OE-Core rev: 812f7427071a6251c428bbc485b336956d779118)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
(From meta-yocto rev: 18d164344b4468ab52bbdd160d0474878042dabb)
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
With default --without-nghttp2 flag set there was no way to get
http2 protocol support using nghttp2 library. Instead moved it to
PACKAGECONFIG options
(From OE-Core rev: 30bc57d689794240343dd599b5d5d654d1976de6)
Signed-off-by: baali <shantanu@senic.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
gpg directory
The high-level method tempfile.TemporaryDirectory give us no way to ignore erros on
removal thus use tempfile.mkdtemp instead. Ignoring possible issues on removal
is neccesary because it contains gpg sockets that are automatically removed by
the system once the process terminates, otherwise the following log is observed:
File "/usr/lib/python3.5/shutil.py", line 436, in _rmtree_safe_fd
os.unlink(name, dir_fd=topfd)
FileNotFoundError: [Errno 2] No such file or directory: 'S.gpg-agent.browser'
This is the same fix as 7e3a7cd2426feac757def81850dc44156cd0f33e, but this applies
to runtime (instead of signing).
[YOCTO #11821]
(From OE-Core rev: cafbee0ae1ed1dd0a5cd6446d0814af505462f81)
Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Newer versions of gpg (at least 2.1.5 and 2.2.1) have issues when signing occurs in parallel
so (unfortunately) the signing must be done serially. Once the upstream problem is fixed,
this patch must be reverted, otherwise we loose all the intrinsic parallelism from
bitbake.
[YOCTO #12022]
(From OE-Core rev: 5301712f9735fcf8d3dec756772668de930e53fe)
Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This image is very large and is skirting the maximum size of hddimg images (4GB,
as they're embedded inside FAT partitions). Making the image 10MB bigger can be
enough to cause the build to fail. This image is also used by QA so currently
we need to keep it working.
The default values for expanding an image to give it usable space are quite
generous, (3GB rootfs * 1.3 gives 1GB of empty space), so change the overhead
multiplier to 1.0x and explicitly request just 0.5GB of empty space in the
images.
This should give us a bit more breathing room until we can either remove hddimg
from the default build, or make this image dramatically smaller.
(From OE-Core rev: 98d9d8958fd5a3bba849e9051bf0310c28b551c2)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Create an option to wic doesn't change fstab file, the final
fstab file will be same that in rootfs and wic doesn't update
file, e.g adding a new mount point.
Users can control the fstab file content in base-files recipe.
This is useful if you want to only create an partition but not
add fstab mount point or add new mount point using label e.g:
LABEL=recovery /recovery auto defaults 0 1
(From OE-Core rev: 00420ec42140c1b752132bda190dede85756d157)
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Backport the fix from https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;
a=commit;h=bf76acbf0da6b0f245e491bec12c0f0a1b5be7c9
(From OE-Core rev: 3b827eff306c484d78d61b259cd5d4eef8df381c)
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Search made with the following regex: getVar ?\((.*), True\).
(From OE-Core rev: b848c3cb495905605283c57c79f2ed8ca17758db)
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|