mirror of
https://github.com/openembedded/meta-openembedded.git
synced 2026-10-15 18:27:12 +00:00
Vaibhav Jindal
35a35488b6
Update tiobench from the legacy 0.3.3 SourceForge release to the actively maintained upstream at github.com/mkuoppal/tiobench, pinned to 11c965c8 (35 commits past v0.4.2). Picks up Clang build support, random I/O test enhancements and cache handling updates. Remove obsolete downstream patches, now fixed upstream: avoid-glibc-clashes.patch - helper renamed to tt_aligned_alloc 0001-Specify-printf-formats.patch - format specifiers fixed 0001-Drop-inline-of-crc32-*.patch - crc32 inlining fixed tiobench-makefile.patch - CC?= and LDFLAGS now upstream Pass CFLAGS via EXTRA_OEMAKE. The upstream Makefile hardcodes CFLAGS=-O2 -Wall and oe_runmake does not pass -e, so OE flags never reached the compiler, losing -g (empty -dbg package), the hardening flags, -ffile-prefix-map and the tune flags. DEFINES is separate, so -DUSE_LARGEFILES is unaffected. Install from do_install() rather than the upstream install target, which has no DESTDIR support and installs tiosum.pl and README, both long gone from the tree. COPYING is dropped from docdir as licenses are handled by the license manifest. Trim RDEPENDS to perl and perl-module-getopt-long; tiobench.pl only uses warnings, strict and Getopt::Long, and strict is RPROVIDED by perl. Data::Dumper and Term::ProgressBar are only reachable via the opt-in --dump and --progress flags. Drop the redundant PV, already set by the recipe filename. Runtime validated on IQ-9075 EVK with tiotest and tiobench.pl across multiple benchmark configurations, including tiobench.pl --help on an image carrying only the trimmed RDEPENDS. Build tested with gcc against glibc on aarch64 (armv8-2a). Signed-off-by: Vaibhav Jindal <vaibjind@qti.qualcomm.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Collection of layers for the OE-core universe
Main layer maintainer: Khem Raj raj.khem@gmail.com
This repository is a collection of layers to supplement OE-Core with additional packages, Each layer have designated maintainer Please see the respective READMEs in the layer subdirectories