Verbose output of ./configure not verbose at all

Question

I have a problem installing OpenOCD:

checking for ftd2xx.h... yes
checking for library containing FT_GetLibraryVersion... no

Said library is installed and tested.

In hopes of seeing where is configure looking for the library, I passed the verbose command switch. No change at all!

Is there a way to check where and under what name is configure looking for said library?

./configure --verbose --enable-ftdi --enable-ft2232_ftd2xx. I found my mistake elsewhere, but this config.log is good to know. — Vorac, Aug 16 '13 at 10:33

score 25 · Accepted Answer · answered Aug 16 '13 at 09:15

25

./configure usually creates a config.log file. It should contain the commands executed to check for the library.

answered Aug 16 '13 at 09:15

Matteo

9,796
4
51
66

badasz · Answer 2 · 2022-09-23T06:08:51.253

4

As @Matteo said, there is config.log.

Notice, it is not always created in the same directory as your configure script you ran. See the configure output to find the log -- it will be in the last few lines.

If you want to see what your configure script does, open the configure script and add set -x in the second line (after #!/bin/bash or something similar).

#!/bin/bash
set -x
... # rest of the configure script

The output would be pretty verbose, but you would have information about each command script ran.

edited Sep 23 '22 at 06:08

answered Aug 08 '22 at 09:38

badasz

43
4

Or just bash -x ./configure... – Stéphane Chazelas Aug 08 '22 at 09:41
On systems where sh is bash, you can also do env SHELLOPTS=xtrace ./configure for all sh and bash invocations to have xtrace enabled. – Stéphane Chazelas Aug 08 '22 at 09:42
good point @StéphaneChazelas, thanks! :) I would check maybe, but wouldn't it affect the environment of the script run somehow? Thanks for your info share – badasz Aug 08 '22 at 09:57

score 1 · Answer 3 · answered Jul 16 '16 at 07:32

The configure file, is a shell script and cannot have verbose logging by default, unless someone wrote specific echo instructions in it. But you should find something like configure.ac / configure.in which will have details on what logic is ran to assert the presence/absence of a particular program / library. I guess that should be more than enough for you to debug the issue in case configure.log doesn't have any information in it.

Verbose output of ./configure not verbose at all

3 Answers3