Score:0

How to display error messages during .configure to the standard console?

ng flag

When compiling from source, we use .configure as the first step. .configure may call some other commands like cc which may fail and print error messages, like header not found or some other compile errors. But these error messages are not displayed on the standard console where I run .configure. This causes difficulty in troubleshooting because sometimes .configure will only tell you it fails. So, how to force error messages of commands called during .configure to be displayed on the standard console, possibly multiplexed with other normal .configure messages?

Score:2

You did not specify which package you are dealing with.

Regardless, the output (stdout, stderr, and other info) of ./configure (not .configure) is not lost. It is typically contained in files in the working directory, e.g., config.log.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.