>>> "Ralf" == Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> Hi Akim,
> * Akim Demaille wrote on Wed, May 31, 2006 at 04:26:17PM CEST:
>> >>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
>>
>> Some time ago I sent this message for which I had no answer.
>> > I suggest that the AC_DEF
>>> "Stepan" == Stepan Kasal <[EMAIL PROTECTED]> writes:
> Hello,
>> * Akim Demaille wrote on Wed, May 31, 2006 at 04:26:17PM CEST:
>> > I suggest that Automake provide the same feature for AM_CONDITIONAL:
> well, you already implemented it, granting Alexandre one point for
> his hint:
> h
Hello Akim,
* Akim Demaille wrote on Tue, Jun 13, 2006 at 12:08:23PM CEST:
> >>> "Ralf" == Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> > * Akim Demaille wrote on Wed, May 31, 2006 at 04:26:17PM CEST:
> >> >>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
> >>
> >> Some time ago I sent
Hello,
On Thu, Jun 08, 2006 at 09:39:33PM +0200, Andreas Büning wrote:
> What about the following patch? I think it would do. Btw, I forgot that
> $PATH usually contains drive letters.
to recognize absolute filename, Autoconf usually uses
[[\\/$]]* | ?:[[\\/]]* )
or
[[\\/]]* | ?:[[\\/]]* )
The b
Hello Stepan, Akim,
Stepan, please keep Akim in Cc:.
* Stepan Kasal wrote on Tue, Jun 13, 2006 at 12:24:05PM CEST:
> On Tue, Jun 13, 2006 at 12:14:15PM +0200, Akim Demaille wrote:
> > I would like to suggest embedding a probe in Autoconf's test suite to
> > check whether `!' (not as an argument t
Hello Bruno,
* Bruno Haible wrote on Mon, May 22, 2006 at 02:13:52PM CEST:
>
> Inspired by Paul Eggert's new chapter about "Portable C and C++ Programming",
> I went out and collected portability notes and pitfall reminders for over
> 200 among the 1116 POSIX functions. (Attached.)
Is an updated
The m4sugar documentation assumes that m4_wrap behaves in a
LIFO manner, since that is the behavior of GNU m4 1.4.x's m4wrap.
For example, the docs give this example of how not to use m4_wrap,
because the two wrapped outputs get concatenated and rescanned:
m4_define([foo], [Foo])
m4_define([bar],
Hello Ralf,
> Is an updated version of this patch to be expected soonish (as in: this
> week)?
Not this week. It is work in progress. Not a showstopper for autoconf-2.60,
I think.
Bruno
My kneejerk suggestion is to implement m4wrap as POSIX requires, but
to add another primitive (m4parw? :-) that works the way 1.4.4 m4wrap
does. We can then ask people who prefer things the old-fashioned way
to use m4parw.
I'd rather not have the behavior depend on POSIXLY_CORRECT.
POSIXLY_CORREC
* Paul Eggert wrote on Tue, Jun 13, 2006 at 07:08:24PM CEST:
> My kneejerk suggestion is to implement m4wrap as POSIX requires, but
> to add another primitive (m4parw? :-) that works the way 1.4.4 m4wrap
> does. We can then ask people who prefer things the old-fashioned way
> to use m4parw.
Yes.
Hello,
On Tue, Jun 13, 2006 at 09:47:43PM +0200, Ralf Wildenhues wrote:
> FWIW, there are only a handful of uses of m4_wrap in Autoconf >= 2.59.
> All look like they don't care about the order, [...]
I looked at the ocurrences of m4_wrap,and I'm afraid you are not
right.
There are several instai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[dropping bug-m4, adding autoconf-patches]
According to Stepan Kasal on 6/13/2006 2:46 PM:
>
> The biggest problem is this:
>
> m4_init contains:
> m4_divert_push([KILL])
> m4_wrap([m4_divert_pop([KILL])[]])
>
> AS_INIT contains:
>
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> * doc/install.texi (Compilers and Options): Weaken the
> suggestion to use GNU make for VPATH builds.
Thanks, I installed that.
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/m
Hi;
I'd like to have a comma in my help string as follows:
AS_HELP_STRING([--with-wx=opt1,opt2], [specify 2 options separated by comma])
However the comma in '[--with-wx=opt1,opt2]' appears to be interpreted as the
comma between the arguments rather than a character in the 1st string. I get
a
On Tue, Jun 13, 2006 at 08:17:01PM -0500, [EMAIL PROTECTED] wrote:
> Hi;
>
> I'd like to have a comma in my help string as follows:
>
> AS_HELP_STRING([--with-wx=opt1,opt2], [specify 2 options separated by comma])
>
> However the comma in '[--with-wx=opt1,opt2]' appears to be interpreted as the
15 matches
Mail list logo
