The question is in the title. For example, as explained here gcc unrecognized command line options '-V' and '-qversion' with autoconf, the error message gcc: error: unrecognized command line option '-V' is, if I understood correctly, an artifact of autoconf trying to figure out the compiler version, not a real error. Is there a list or some reliable trick to figure out those error messages that can be ignored? The answer to a related question here Slackware ./configure error is not very informative, even missing the point. Better, is there a way, without having to change the entire setting, to eliminate these uninformative error messages. It is not my setting. In this case, it is the setting of the excellent Videolan VLC project.
Asked
Active
Viewed 552 times
0
Dominic108
- 111
- 3
1 Answers
0
Oh well, here is what I discovered. All the tests done in the configure file that is generated by autoconf have their output redirected to some other streams than stdout or stderr. This means that they are not in the output that is sent to the terminal. So, to have a file without the output of these tests one can redirect the output streams stderr and stdout of configure to the file, for example: ./configure > config_.log 2>&1. You will still see the conclusion of these tests, because these are sent to stdin or stderr. In particular, in this manner, I don't see the fake error gcc: error: unrecognized command line option '-V' anymore, but I see the result of the test.
Dominic108
- 111
- 3