Hi, more ideas would be:
Add option -d to the "make" command in ./configure. Or skip the test by setting variable am_cv_make_support_nested_variables to "yes" before running configure: export am_cv_make_support_nested_variables=yes ./configure If skipping the test does reliably help, then the problem is with that single test. If ./configure gets stuck some steps later, then there is a general problem with the terminal or the shell which is running in it. When i do this with the ./configure of GNU xorriso, i get the message checking whether make supports nested variables... (cached) yes The text "(cached)" is emitted it "make" is not run. The further code in ./configure then acts as if the test yielded the result which we expect on Debian. See e.g. the result in https://buildd.debian.org/status/fetch.php?pkg=libisoburn&arch=amd64&ver=1.5.0-1&stamp=1539085692&raw=0 If i set the variable to "no", i get checking whether make supports nested variables... (cached) no A following run of "make" yields no suspicious messages. The binary starts and reports its version. Have a nice day :) Thomas
