Use python3. Note that the recipe already depends on python3-core
at runtime. We only change scripts that show up under /usr/bin.
Signed-off-by: Joe Slater <joe.slater@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
"pmemblk", "dev-dax" and "libpmem" engines are used for persistent memory.
In order to enable them, add "pmem" to MACHINE_FEATURES in BSP conf.
Signed-off-by: Yongxin Liu <yongxin.liu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Update fio recipe to target python3 since python2 is EOL and has been
dropped from OE-Core.
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
-files/0001-arch-arm-Consider-armv7ve-arch-as-well.patch
Removed since this is included in 3.17.
-Refresh the following patch:
files/0001-update-the-interpreter-paths.patch
Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
-files/0001-engines-splice-remove-buggy-mem_align-set.patch
Removed since this is included in 3.16.
Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
delete "rev for v3.8" in fio_3.15.bb this is unneeded since version is
in the recipe name itself
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
backport an fio upstream patch to fix "first direct IO errored" when
we specify -ioengine=spice
Signed-off-by: Liwei Song <liwei.song@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Refresh 0001-update-the-interpreter-paths.patch as the
folder unit_tests/ is renamed to t/ in below commit:
c44d2c6e Move steady state unit test to t/
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* Licence-Update:
Address update in COPYING
* Add patch 0001-update-the-interpreter-paths.patch
and add python and bash to RDEPENDS_${PN} to fix
below QA issues:
ERROR: fio-3.7-r0 do_package_qa: QA Issue: /usr/bin/fiologparser.py contained in package fio requires /usr/bin/python2.7, but no providers found in RDEPENDS_fio? [file-rdeps]
ERROR: fio-3.7-r0 do_package_qa: QA Issue: /usr/bin/genfio contained in package fio requires /usr/bin/bash, but no providers found in RDEPENDS_fio? [file-rdeps]
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
As of commit OE-Core:773c9e18071d71454473dd81aff911104a2e9bc6
EXTRA_OECONF is appended with the option --disable-static on
DISABLE_STATIC variable and this cause the error:
DEBUG: Python function sysroot_cleansstate finished
DEBUG: Executing shell function do_configure
Bad option --disable-static
--cpu= Specify target CPU if auto-detect fails
--cc= Specify compiler to use
--extra-cflags= Specify extra CFLAGS to pass to compiler
--build-32bit-win Enable 32-bit build on Windows
--build-static Build a static fio
--esx Configure build options for esx
--enable-gfio Enable building of gtk gfio
--disable-numa Disable libnuma even if found
--enable-libhdfs Enable hdfs support
WARNING: exit code 1 from a shell command.
So, we need to disable this option.
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Make fio's NUMA support optional via PACKAGECONFIG.
Enable this feature by default, except on ARM where libnuma/numactl
is not available.
Signed-off-by: Dominic Sacré <dominic.sacre@gmx.de>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
WAWARNING: QA Issue: fio rdepends on numactl, but it isn't a build dependency? [build-deps]
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Fixes:
| WARNING: QA Issue: fio rdepends on zlib, but it isn't a build dependency? [build-deps]
Signed-off-by: Dominic Sacré <dominic.sacre@gmx.de>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* This change is only aesthetic (unlike indentation in Python
tasks).
* Some recipes were using tabs.
* Some were using 8 spaces.
* Some were using mix or different number of spaces.
* Make them consistently use 4 spaces everywhere.
* Yocto styleguide advises to use tabs (but the only reason to keep
tabs is the need to update a lot of recipes). Lately this advice
was also merged into the styleguide on the OE wiki.
* Using 4 spaces in both types of tasks is better because it's less
error prone when someone is not sure if e.g.
do_generate_toolchain_file() is Python or shell task and also allows
to highlight every tab used in .bb, .inc, .bbappend, .bbclass as
potentially bad (shouldn't be used for indenting of multiline
variable assignments and cannot be used for Python tasks).
* Don't indent closing quote on multiline variables
we're quite inconsistent wheater it's first character on line
under opening quote or under first non-whitespace character in
previous line.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Acked-by: Koen Kooi <koen@dominion.thruhere.net>