buildroot/package/iperf, branch 2016.08

iperf: fix "speed" display in csv report

2016-07-30T12:39:20+00:00

Some parameters displayed in the CSV reports are declared as uint64_t, but the printf format doesn't reflect this. Submitted bug: https://sourceforge.net/p/iperf/bugs/66/ Signed-off-by: Matt Poduska Signed-off-by: Atul Singh Signed-off-by: Matt Weber Reviewed-by: Khem Raj Signed-off-by: Thomas Petazzoni

iperf: bump to version 2.0.9

2016-07-30T12:30:03+00:00

iperf2 is a fork of the original unmaintained iperf project, that continues the development of the iperf 2.x series. Update homepage link, and download location. Signed-off-by: Baruch Siach [Thomas: - change the download location to use downloads.sourceforge.net - turn the patch into a Git-formatted one, since upstream uses Git as its version control system - as noticed by Khem Raj, a C99 compiler is needed for the bool type, so added AC_PROG_CC_C99 to configure.ac, and consequently added IPERF_AUTORECONF = YES. - removed two _CONF_ENV variables related to the bool type, they were added by an older commit e13ac0ec8788092c6508636da94fe0198c18dffd back when we had a config.cache shared between packages (which is no longer the case today)] Signed-off-by: Thomas Petazzoni

iperf: add license information

2015-01-20T16:03:56+00:00

Signed-off-by: Richard Genoud Signed-off-by: Thomas Petazzoni

package: add hashes for SourceForge-hosted packages

2014-12-28T21:21:16+00:00

Since SourceForge sometimes serves us faulty tarballs, we can tons of autobuild failures: http://autobuild.buildroot.org/results/9fb/9fba5bf086a4e7a29e5f7156ec43847db7aacfc4/ http://autobuild.buildroot.org/results/6c8/6c837b244c45ac3b3a887734a371cd6d226cf216/ ... Fix that by adding hash files for all SourceForge-hosted packages (thos etht did not already have it). We normally prefer to use hashes published by upstream, but hunting them all one by one is a tedious task, so those hashes were all locally computed with a script that searched for SF-hosted packages, downloades the associated tarball, computed the hash, and stored it in the corresponding .hash file. Also, SF publishes sha1 hashes, while I used the stronger sha256, since sha1 is now considered to be relatively weak. Signed-off-by: "Yann E. MORIN" Cc: Peter Korsgaard Cc: Thomas Petazzoni Cc: Maxime Hadjinlian Cc: Richard Braun Cc: Nathaniel Roach Signed-off-by: Thomas Petazzoni

packages: rename FOO_CONF_OPT into FOO_CONF_OPTS

2014-10-04T16:54:16+00:00

To be consistent with the recent change of FOO_MAKE_OPT into FOO_MAKE_OPTS, make the same change for FOO_CONF_OPT. Sed command used: find * -type f | xargs sed -i 's#_CONF_OPT\>#&S#g' Signed-off-by: Thomas De Schampheleire Reviewed-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

packages: no longer pass --disable-dependency-tracking in individual packages

2014-08-29T07:17:38+00:00

Now that --disable-dependency-tracking is passed by the autotools-package infrastructure, there's no longer any reason to pass it in individual packages. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

Config.in files: add missing dependencies to toolchain option comments

2013-11-10T22:59:57+00:00

When a package A depends on config option B and toolchain option C, then the comment that is given when C is not fulfilled should also depend on B. For example: config BR2_PACKAGE_A depends on BR2_B depends on BR2_LARGEFILE depends on BR2_WCHAR comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR This comment should actually be: comment "A needs a toolchain w/ largefile, wchar" depends on BR2_B depends on !BR2_LARGEFILE || !BR2_WCHAR or if possible (typically when B is a package config option declared in that same Config.in file): if BR2_B comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR [other config options depending on B] endif Otherwise, the comment would be visible even though the other dependencies are not met. This patch adds such missing dependencies, and changes existing such dependencies from depends on BR2_BASE_DEP && !BR2_TOOLCHAIN_USES_GLIBC to depends on BR2_BASE_DEP depends on !BR2_TOOLCHAIN_USES_GLIBC so that (positive) base dependencies are separate from the (negative) toolchain dependencies. This strategy makes it easier to write such comments (because one can simply copy the base dependency from the actual package config option), but also avoids complex and long boolean expressions. Signed-off-by: Thomas De Schampheleire Acked-by: Arnout Vandecappelle (Essensium/Mind) (untested) Signed-off-by: Peter Korsgaard

Config.in files: unify comments of toolchain option dependencies

2013-10-14T20:45:57+00:00

This patch lines up the comments in Config.in files that clarify which toolchain options the package depends on. Signed-off-by: Thomas De Schampheleire Signed-off-by: Peter Korsgaard

package: remove the default value of the $(PKG)_SOURCE variable

2013-10-06T19:52:19+00:00

Signed-off-by: Jerzy Grzegorek Acked-by: Thomas De Schampheleire Signed-off-by: Peter Korsgaard

Normalize separator size to 80

2013-06-06T20:30:24+00:00

Signed-off-by: Alexandre Belloni Signed-off-by: Peter Korsgaard