[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: |
Sun, 1 Nov 2009 12:21:12 +0100 |
User-agent: |
Mutt/1.5.20 (2009-08-09) |
* Eric Blake wrote on Fri, Oct 30, 2009 at 01:00:08PM CET:
> According to Ralf Wildenhues on 10/30/2009 12:31 AM:
> > 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?
>
> Hmm, those aren't done as often (about all you can do is run nm on it;
> that seems like something libtool might want to do, but who else does it
> to be worth documenting it?).
You can rename it, compile another object and link both together.
There are cases where testing a program made up of more than one object
is of interest.
Even for libtool it would be nice to have certainty. But you're right,
this isn't that urgent or important.
> > And add testsuite exposure to each?
>
> I won't turn down help on that front.
Not even needed: I merely didn't find
tests/compile.at:Order of user actions and cleanup
until now. Gee, I really should try to hack up that coverage map ...
Cheers,
Ralf
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: link and run a (fortran) program redirecting its stdout/stderr,
Ralf Wildenhues <=