At Tuesday 13 October 2009, Ralf Wildenhues <Ralf.Wildenhues@xxxxxx> 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. Was I misunderstood, or am I missing something? > To allow for cross > compilation, in the fourth argument you could try to find out which > versions of gfortran have this issue, and check for those versions > there (probably easiest done by GCC-specific preprocessor > conditionals). Luckily, cross compilation is not an issue here: my package is a simple testsuite for ratfor, and I need the fortran compiler only to build test programs from fortran sources generated by ratfor; this test programs must then be run on the spot, so that a native compiler is needed anyway. Regards, Stefano _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
