* Alexandre Duret-Lutz wrote on Sun, Oct 15, 2006 at 10:04:33PM CEST:
> >>> "RW" == Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
> RW> OK to apply?
>
> Sure. Thank for implementing this.
Done, with Steven added to THANKS, and this added:
> Maybe add here
> # These flags are used as %SOURCE
>>> "RW" == Ralf Wildenhues <[EMAIL PROTECTED]> writes:
[...]
RW> OK to apply?
Sure. Thank for implementing this.
RW> 2006-10-14 Ralf Wildenhues <[EMAIL PROTECTED]>
RW> * lib/am/depend2.am (%SOURCEFLAG%): New substitution, goes
RW> right before the expanded source file name.
RW> * auto
[ http://lists.gnu.org/archive/html/automake-patches/2006-08/msg00073.html
http://lists.gnu.org/archive/html/automake-patches/2006-09/msg00013.html ]
Hello again, and sorry for the delay,
For now I've backed down the previous plans a bit. The FCFLAGS_* are
most important for the extensions .f9
On Fri, 1 Sep 2006, Ralf Wildenhues wrote:
However, the question about introducing AM_FC_SRCEXT was rather meant
the other way round: Can there be uses where you would like to know for
some reason the answer to
AC_FC_SRCEXT([f])
but in your source tree, you have files with extension .f that shou
Hello Steven, all,
(Let's keep the mailing list in Cc:, please. Thanks!)
* Steven G. Johnson wrote on Fri, Sep 01, 2006 at 01:42:43AM CEST:
> On Wed, 30 Aug 2006, Ralf Wildenhues wrote:
> >The incomplete patch below chooses the first answer for both questions.
> >Based on feedback I can supply d
Hello Steven, everyone,
Steven suggested (quite) a while ago[1] to exploit AC_FC_SRCEXT in
Automake in two ways:
- add the computed flag to the compilation rule,
- infer from the macro argument that files with this extensions
should be compiled with $(FC) rather than $(F77).
I'm not yet sure ab
