[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: link and run a (fortran) program redirecting its stdout/stderr

From: Ralf Wildenhues
Subject: Re: link and run a (fortran) program redirecting its stdout/stderr
Date: Fri, 30 Oct 2009 07:31:07 +0100
User-agent: Mutt/1.5.20 (2009-08-09)

* Eric Blake wrote on Wed, Oct 28, 2009 at 03:19:37AM CET:
> According to Stefano Lattarini on 10/14/2009 3:52 AM:
> >> 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.
> > Oh.  This is exactly what I need.  Thank you very much!
> > 
> > Maybe the autoconf documentation might be clearer on this point.
> Good idea.  Done:

Should we also document that the ACTION-IF-TRUE part of
AC_LINK_IFELSE allows linked programs to be inspected (not necessarily
run) and that of AC_COMPILE_IFELSE allows compiled objects to be
inspected?  And add testsuite exposure to each?

/me tries to remember what the difference between $OBJEXT and
$ac_objext, and between $EXEEXT and $ac_ext was again ...


>  The @var{input} can be made by @code{AC_LANG_PROGRAM} and friends.
>  @code{LDFLAGS} and @code{LIBS} are used for linking, in addition to the
>  compilation flags of the current language (@pxref{Language Choice}).
> +Additionally, @var{action-if-true} can run @command{./conftest$EXEEXT}
> +for further testing.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]