On Fri, Sep 08, 2000 at 09:05:57AM -0400, Pavel Roskin wrote:
: I'll try to remove changequote()s from libtool.m4 as long as it remains
: compatible with Autoconf-2.13
I don't see how this can be a problem - it's strictly an m4 parse issue,
and the m4 parsing is the same, no matter which autoconf
> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes:
Pavel> I'm fixed now :-)
:)
Pavel> I'll try to remove changequote()s from libtool.m4 as long as it
Pavel> remains compatible with Autoconf-2.13
This is totally independent from the Autoconf release.
Hello, Akim!
> Yes, this is a bad recommendation. And in fact you frightened me
> Pavel, by current you mean 2.13, right? I could not find this horror
> in the CVS documentation. But there is an answer to the above
> statement:
Sorry to all :-(
"info --file autoconf.info" looks in /usr/info b
| On Thu, Sep 07, 2000 at 02:12:34PM -0400, Pavel Roskin wrote:
| > -
| > However, in a few places the macros need to use brackets (usually in C
| > program text or regular expressions). In those places, they use the `m4'
| > builtin command `changequote' to temporarily change the qu
On Thu, Sep 07, 2000 at 02:12:34PM -0400, Pavel Roskin wrote:
> -
> However, in a few places the macros need to use brackets (usually in C
> program text or regular expressions). In those places, they use the `m4'
> builtin command `changequote' to temporarily change the quote charact
Hello, Lars!
I'm moving the discussion to [EMAIL PROTECTED] where it seems more
appropriate.
>From the discussion in [EMAIL PROTECTED]
> : # Check for any special shared library compilation flags.
> : -changequote(,)dnl
> : if test -n "$ac_cv_prog_cc_shlib"; then
> :AC_MSG_WARN([\`$CC' re
