ports/iperf3
ports/iperf3
1
1
Fork 0
Code Releases Activity

docs: Update FAQ item on profiled executables to match reality.

Browse Source 
(Specifically as on iperf-3.8 these aren't built by default anymore.)
This commit is contained in:
Bruce A. Mah 2020-07-30 11:34:43 -07:00
parent a9c28038c0
commit de289c9500
No known key found for this signature in database
GPG Key ID: 4984910A8CAAEE8A
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/faq.rst
View File

@ -74,10 +74,16 @@ How can I build a statically-linked executable of iperf3?
How can I build on a system that doesn't support profiled executables?
This problem has been noted by users attempting to build iperf3 for
Android systems. There are several workarounds. In order from least
Android systems, as well as some recent versions of macOS.
There are several workarounds. In order from least
effort to most effort:
#. Beginning with iperf-3.6, the ``--disable-profiling`` flag can be
#. Beginning with iperf-3.8, profiled executables are actually not
built by default, so this question becomes somewhat moot. Pass
the ``--enable-profiling`` flag to ``configure`` to build
profiled executables.
#. In iperf-3.6 and iperf-3.7, the ``--disable-profiling`` flag can be
passed to ``configure`` to disable the building of profiled
object files and the profiled executable.