Alexandre Oliva [EMAIL PROTECTED] writes:
The only way to do it so that it works with both autoconf 2.13 and
CVS autoconf, without triggering the warning in CVS autoconf, is
this (from CVS automake's missing.m4):
am_backtick='`'
AC_MSG_WARN([${am_backtick}$VAR' ...])
Ok, I see. New
On Oct 12, 2000, Akim Demaille [EMAIL PROTECTED] wrote:
This is s heavy :( As I proposed to Pavel, I'm OK with moving this
warning from `syntax' to `obsolete' for 2.50, and move it back to
`syntax' in 2.51 or later.
Probably later :-)
This way, every body is happy. ?
I'm definitely
"Alexandre" == Alexandre Oliva [EMAIL PROTECTED] writes:
Alexandre I'm definitely in favor of this change.
OK I consider this an OK and will apply the change directly.
___
Libtool mailing list
[EMAIL PROTECTED]
On Thu, Oct 12, 2000 at 12:38:11PM +0200, Morten Eriksen wrote:
BTW, I noticed something which looks a bit strange to me. Beginning at
approximately line 2180 of libtool.m4 (from the head CVS branch),
there are a lot of shell variables which are set up. But some of them
are just set to
On Oct 11, 2000, Morten Eriksen [EMAIL PROTECTED] wrote:
Autoconf straight out of CVS will complain about "backquotes and
doublequotes should not be backslashed" when expanding the macro code
of _LT_AC_LTCONFIG_HACK libtool.m4.
The problem is that CVS autoconf changes the way backquotes are
