Re: may Automake rely on _AC_SUBST_VARS?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ralf Wildenhues on 4/7/2009 12:41 PM: >> m4_define([_AC_COMPILER_EXEEXT], >> m4_defn([_AC_COMPILER_EXEEXT])[m4_provide([_AM_COMPILER_EXEEXT])]) >> >> m4_provide_if([_AM_COMPILER_EXEEXT], >> [AM_CONDITIONAL([am__EXEEXT], [test -n "$EXEEXT

Re: renamed objects and other languages

[ ] Hello Florian, Stepan, I just found a two-year-old bug report of you, with a patch and a test. Please accept my apologies for having overlooked this one; it looks good. * Florian Briegel at mpia-hd wrote on Tue, May 01, 2007

Re: Vala support for automake

Hi Ralf, On Tue, 2009-04-07 at 23:08 +0200, Ralf Wildenhues wrote: > Other than that, I haven't yet gotten around to get my system up to date > in order to support Vala 0.7 yet. Would you be so nice as to post > verbose log output for all the vala tests? That is, just > cd tests > for t in p

Re: Vala support for automake

Hello Jürg, very nice. Thanks again for working on this. At a first glance, all I could find while reading the patch was a trivial s/_SOURCE/_SOURCES/ in the manual. Other than that, I haven't yet gotten around to get my system up to date in order to support Vala 0.7 yet. Would you be so nice

Re: may Automake rely on _AC_SUBST_VARS?

Hi Eric, * Eric Blake wrote on Tue, Apr 07, 2009 at 02:23:01PM CEST: > According to Ralf Wildenhues on 4/6/2009 11:28 PM: > > > > In other occasions, it is often clear which macro introduces a variable. > > For example, here it's _AC_COMPILER_EXEEXT, but that one is define'd > > only, not defun'e

Re: may Automake rely on _AC_SUBST_VARS?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ralf Wildenhues on 4/6/2009 11:28 PM: >> people start wanting to get at the same information, we can add a public >> wrapper along the lines of: >> >> # AC_SUBST_VARS_QUERY([VAR], [IF-USED], [IF-UNUSED]) >> # --