diff options
| author | Bruce A. Mah <bmah@es.net> | 2020-07-30 11:34:43 -0700 |
|---|---|---|
| committer | Bruce A. Mah <bmah@es.net> | 2020-07-30 11:34:43 -0700 |
| commit | de289c950095ff3afc9f1a5a4efafeadc3aec49b (patch) | |
| tree | f8ea2f75ccfc432f68fd85621b1a76346d9bc875 | |
| parent | a9c28038c08d4287d4bcc369514ef411336c5d1f (diff) | |
| download | iperf3-de289c950095ff3afc9f1a5a4efafeadc3aec49b.tar.gz | |
docs: Update FAQ item on profiled executables to match reality.
(Specifically as on iperf-3.8 these aren't built by default anymore.)
| -rw-r--r-- | docs/faq.rst | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/docs/faq.rst b/docs/faq.rst index c7170cc..167b921 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -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. |