./configure script outputs
checking if and
checking whether on execution
how the two results are different for checking conditions?
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It only takes a minute to sign up.Sign up to join this community
configure script will most often use the wording
checking whether because this is the default wording in the default
If a project's
configure script says
checking if, then this means the same thing and is probably produced by a custom test macro that the developers have written themselves (or borrowed).
As an example, when configuring
bash 5.0.7 on my machine, I get 44
checking whether and only 5
checking if. The
checking if mostly come from custom test macros.
checking if the linker (/usr/bin/ld) is GNU ld... yes checking if dup2 fails to clear the close-on-exec flag... no checking if opendir() opens non-directories... no checking if getcwd() will dynamically allocate memory with 0 size... yes checking if signal handlers must be reinstalled when invoked... no
In a project I'm maintaining for work, in which we mostly use default test macros and macros from the Autoconf Archive, there are no
checking if at all, but 65 outputs of the other kind.
At the end of the day, there is no effective difference between the two, just as there is no real difference between them in spoken English.