From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/iperf3: bump to version 3.8.1
Date: Thu, 18 Jun 2020 21:55:18 +0200 [thread overview]
Message-ID: <20200618215518.62d2ed38@windsurf.home> (raw)
In-Reply-To: <d3ba56c5fb5b641d8817ff90b19e575288fb5333.1591939941.git.baruch@tkos.co.il>
On Fri, 12 Jun 2020 08:32:21 +0300
Baruch Siach <baruch@tkos.co.il> wrote:
> Don't pass --disable-profiling, profiling is now disabled by default.
> For some reason adding --disable-profiling makes it enabled.
That's because they don't use AC_ARG_ENABLE correctly:
# Check if enable profiling
AC_ARG_ENABLE([profiling],
AS_HELP_STRING([--enable-profiling], [Enable iperf3 profiling binary]),
[enable_profiling=yes],
[:])
AM_CONDITIONAL([ENABLE_PROFILING], [test x$enable_profiling = xyes])
The [enable_profiling=yes] should be [enable_profiling=$enableval]
This is a common mistake. Many people think AC_ARG_ENABLE arguments are:
- option name
- option help
- what gets executed if option is enabled
- what gets executed if option is disabled
But in fact, the arguments of AC_ARG_ENABLE are:
- option name
- option help
- what gets executed if option is passed, regardless of whether it is
enabled or disabled. The value is in $enableval
- what gets executed if no value is passed at all (i.e neither
--enable nor --disable are passed)
So, I've slightly reworked the commit log and applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-06-18 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 5:32 [Buildroot] [PATCH] package/iperf3: bump to version 3.8.1 Baruch Siach
2020-06-18 19:55 ` Thomas Petazzoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200618215518.62d2ed38@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox