NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
27dde92fa8
kumquat-buildroot/package/fio/Config.in

27 lines
1009 B
Plaintext
Raw Normal View History

fio: new package [Thomas: add largefile and thread dependencies, bump to version 2.1.4, use upstream Git instead of Debian tarballs, adjust license information] Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-10-30 16:22:25 +01:00
config BR2_PACKAGE_FIO
bool "fio"
depends on BR2_USE_MMU # fork()
depends on BR2_LARGEFILE
depends on BR2_TOOLCHAIN_HAS_THREADS
fio: prevent selection with unusable uClibc versions The fio program uses posix_madvise(). However, posix_madvise() is only available in the Git tree of uClibc, and in Buildroot's version of uClibc 0.9.33, thanks to the huge number of backported patches that we carry. Therefore, trying to build fio with an external uClibc toolchain is most likely going to fail (as the uClibc version is most likely an official stable release, and no stable release of uClibc ever had the support for posix_madvise()). And similarly, building fio with uClibc 0.9.31 and 0.9.32 is always going to fail. We disable those use cases to avoid repeated autobuilder failures. No kconfig comment has been added, because we don't have a well-defined way of specifying such exceptions. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-12-26 10:44:45 +01:00
# fio uses posix_madvise(), which is not part of any official
# release of uClibc, but is part of uClibc Git, and backported
# in Buildroot patch set of uClibc 0.9.33. Therefore, we
# disable the build of fio for external uClibc toolchains
package: remove references to uClibc 0.9.32 This commit removes all remaining references to uClibc 0.9.32. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-07-01 20:03:04 +02:00
# (which use an unknown uClibc version) and for 0.9.31 which
# don't have posix_madvise().
fio: prevent selection with unusable uClibc versions The fio program uses posix_madvise(). However, posix_madvise() is only available in the Git tree of uClibc, and in Buildroot's version of uClibc 0.9.33, thanks to the huge number of backported patches that we carry. Therefore, trying to build fio with an external uClibc toolchain is most likely going to fail (as the uClibc version is most likely an official stable release, and no stable release of uClibc ever had the support for posix_madvise()). And similarly, building fio with uClibc 0.9.31 and 0.9.32 is always going to fail. We disable those use cases to avoid repeated autobuilder failures. No kconfig comment has been added, because we don't have a well-defined way of specifying such exceptions. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-12-26 10:44:45 +01:00
depends on !BR2_TOOLCHAIN_EXTERNAL_UCLIBC && \
package: remove references to uClibc 0.9.32 This commit removes all remaining references to uClibc 0.9.32. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-07-01 20:03:04 +02:00
!BR2_UCLIBC_VERSION_0_9_31
fio: disable on nios2 because of missing fallocate64() The fallocate() function is replaced by fallocate64() while compiling with LARGE_FILE flags. Current nios2 toolchain is missing the fallocate64() function. Fixes: http://autobuild.buildroot.net/results/9cd/9cd30031a40f768f6090cfba44c880fb2406672b http://autobuild.buildroot.net/results/7da/7da32ca8178aa6bada06dfaea38e9e693fba0db2 http://autobuild.buildroot.net/results/0ef/0ef7358289bff2a5f9efda27115eddb379c1a0b9 [...] [Peter: reference BR2_LARGEFILE, add autobuilder refs as suggested by Yann] Signed-off-by: Frank Bergmann <frank@frajasalo.de> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-19 21:23:30 +02:00
# fio uses fallocate() which becomes fallocate64() while compiling
# with BR2_LARGEFILE but fallocate64() is not available on nios2
depends on !BR2_nios2
fio: new package [Thomas: add largefile and thread dependencies, bump to version 2.1.4, use upstream Git instead of Debian tarballs, adjust license information] Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-10-30 16:22:25 +01:00
help
fio is an I/O tool meant to be used both for benchmark
and stress/hardware verification.
http://git.kernel.dk/?p=fio.git;a=summary
comment "fio needs a toolchain w/ largefile, threads"
depends on !BR2_LARGEFILE || !BR2_TOOLCHAIN_HAS_THREADS
fio: disable on nios2 because of missing fallocate64() The fallocate() function is replaced by fallocate64() while compiling with LARGE_FILE flags. Current nios2 toolchain is missing the fallocate64() function. Fixes: http://autobuild.buildroot.net/results/9cd/9cd30031a40f768f6090cfba44c880fb2406672b http://autobuild.buildroot.net/results/7da/7da32ca8178aa6bada06dfaea38e9e693fba0db2 http://autobuild.buildroot.net/results/0ef/0ef7358289bff2a5f9efda27115eddb379c1a0b9 [...] [Peter: reference BR2_LARGEFILE, add autobuilder refs as suggested by Yann] Signed-off-by: Frank Bergmann <frank@frajasalo.de> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-19 21:23:30 +02:00
depends on !BR2_nios2
fio: add comment mmu depends Otherwise it shows up indirectly when toolchain options aren't enough and then vanishes when they are fulfilled. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-08-04 15:20:26 +02:00
depends on BR2_USE_MMU
Reference in New Issue Copy Permalink