* Stefano Lattarini wrote on Tue, Oct 13, 2009 at 08:39:11PM CEST: > At Tuesday 13 October 2009, Ralf Wildenhues wrote: > > * Stefano Lattarini wrote on Tue, Oct 13, 2009 at 03:22:51PM CEST: > > > What matters to me is that the *program generated* by the > > > compiler, when executed, is not too verbose w.r.t. the `stop' > > > builtin. > > > > Then you should be able to use AC_RUN_IFELSE. > But in the documentation of AC_RUN_IFELSE, as found at: > http://www.gnu.org/software/autoconf/manual/autoconf.html#Runtime > I can't find any mention of files where the stdout/stderr of the test > program is saved. And I known in advance that the test program will > succeed: what I must verify is that it won't write anything on stdout > or stderr. In this respect, AC_RUN_IFELSE does not seem helpful. Sorry; I forgot to add: In the ACTION-IF-TRUE argument of AC_RUN_IFELSE, you can invoke ./conftest$EXEEXT yourself and see what it does. Cheers, Ralf _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
