aboutsummaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-benchmark/iperf
AgeCommit message (Collapse)Author
2018-01-23iperf: rename to iperf2 and bump 2.0.5 -> 2.0.10akuster/mut-nextIoan-Adrian Ratiu
Both iperf2 and iperf3 are actively maintained projects. iperf2 was forked from the old iperf codebase because iperf3 is an incompatible and as of yet incomplete rewrite from scratch. Rename the old iperf to ipref2 to avoid ambiguity. Drop all 3 patches we were carrying because they got merged upstream. Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Armin Kuster <akuster808@gmail.com>
2018-01-23Revert "iperf: remove deprecated package"Ioan-Adrian Ratiu
This reverts commit 2b6cad9522582b0816251b5efbbc4601d037ae0e. iperf3 is a complete rewrite which does not have full parity with iperf2 and in some cases it's intentionally backwards incompatble so moving to iperf3 is not possible for everyone. That's why the project got forked. These recipes/packages can live side by side because their projects are now independent (separate codebases and maintainers). Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Armin Kuster <akuster808@gmail.com>
2017-02-13iperf: remove depricated packageArmin Kuster
Now the we have iPerf3, we should drop iPerf. This is the recommendation from the website. https://sourceforge.net/projects/iperf/ "This is the old, Iperf 2 code base. This version of Iperf is deprecated and we do not recommend it any longer. Please use Iperf3. " Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2016-09-05iperf: control ipv6 support based on DISTRO_FEATURESJackie Huang
Add PACKAGECONFIG for ipv6 and control it based on DISTRO_FEATURES. Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2016-06-22iperf: resolve issues with gcc6Derek Straka
Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2016-06-13faac, iperf, crash, espeak, open-vcdiff: blacklist, fails to build with gcc-6Martin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2015-05-13iperf: fix ${PN}-${PV} -> ${BP} for multilibYi Zhao
Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-12-19iperf: fix out of tree configurationBelal, Awais
The configure step uses a package header to check for support of types/declares, this package header encapsulates all the required system headers for providing the needed resources. When configured from an out of tree directory the package header is not found due to the hard path. We now make the path for package header relative to 'srcdir' so it is found appropriately. Signed-off-by: Awais Belal <awais_belal@mentor.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-07-15meta-oe: use BPN in SRC_URIRobert Yang
Fixed SRC_URI: * ${PN} -> ${BPN}, use ${BP} if it was ${PN}-${PV} * ${P} -> ${BP} Otherwise we would meet do_fetch errors when we do the multilib, native or nativesdk build. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2014-03-18iperf: Upgrade to version 2.0.5Lauren Post
This version provides better ethernet performance Patch is required for man page portion of build Signed-off-by: Lauren Post <lauren.post@freescale.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2013-08-08iperf: Fix licenseChunrong Guo
*the current version of Iperf has a false LICENSE set, so fix license with the generic BSD license Signed-off-by: Chunrong Guo <B40290@freescale.com> Acked-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2013-04-15recipes: Unify indentationMartin Jansa
* 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>
2011-08-29iperf: Add version 2.0.4 (initial recipe)Noor Ahsan
* Imported from oe.dev commit id 0ff10ecb88de73074ae4857046643cef15dc4e97 and c10c33f86903c93611023197a7f812459c2dfe2d. * Combined .inc and bb file from oe.dev and made a single bb file. * Removed EXTRA_OECONF_append_epia = " --disable-threads" while importing as this should go in epia layer. Signed-off-by: Noor Ahsan <noor_ahsan@mentor.com>