kumquat-buildroot/package/iperf/Config.in

config BR2_PACKAGE_IPERF
	bool "iperf"
	depends on BR2_INSTALL_LIBSTDCPP
	# uses fork()
	depends on BR2_USE_MMU
	help
	  Internet Protocol bandwidth measuring tool for measuring
	  TCP/UDP performance.

	  https://sourceforge.net/projects/iperf2/

comment "iperf needs a toolchain w/ C++"
	depends on BR2_USE_MMU
	depends on !BR2_INSTALL_LIBSTDCPP
iperf package. Closes #0001224 2007-02-16 21:16:24 +01:00			`config BR2_PACKAGE_IPERF`
			`bool "iperf"`
iperf: don't silently enable C++ support in toolchain 2008-09-01 17:33:17 +02:00			`depends on BR2_INSTALL_LIBSTDCPP`
iperf: needs MMU Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk> 2012-05-20 19:52:35 +02:00			`# uses fork()`
			`depends on BR2_USE_MMU`
iperf package. Closes #0001224 2007-02-16 21:16:24 +01:00			`help`
			`Internet Protocol bandwidth measuring tool for measuring`
			`TCP/UDP performance.`

iperf: bump to version 2.0.9 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 <baruch@tkos.co.il> [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 <pkg>_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 <thomas.petazzoni@free-electrons.com> 2016-07-29 11:26:47 +02:00			`https://sourceforge.net/projects/iperf2/`
iperf: don't silently enable C++ support in toolchain 2008-09-01 17:33:17 +02:00
Config.in files: unify comments of toolchain option dependencies 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 <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> 2013-10-13 16:55:32 +02:00			`comment "iperf needs a toolchain w/ C++"`
Config.in files: add missing dependencies to toolchain option comments 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 <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> (untested) Signed-off-by: Peter Korsgaard <peter@korsgaard.com> 2013-11-07 09:24:37 +01:00			`depends on BR2_USE_MMU`
iperf: don't silently enable C++ support in toolchain 2008-09-01 17:33:17 +02:00			`depends on !BR2_INSTALL_LIBSTDCPP`