-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Rasmus Lerdorf on 11/28/2009 12:07 PM:
> ok, the docs only say that it has to come before AC_ARG_ENABLE/AC_ARG_WITH
>
> http://www.gnu.org/software/hello/manual/autoconf/Help-.html
>
> and it worked fine in 2.64/2.65 before the AC_INIT,
Eric Blake wrote:
> According to Rasmus Lerdorf on 11/28/2009 11:34 AM:
>> I may have spoken too soon. Someone is now reporting that with 2.62 he
>> is getting:
>
>> configure.in:12: error: m4_defn: undefined macro: _m4_divert_diversion
>> autom4te: /usr/bin/m4 failed with exit status: 1
>
>> 12
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Rasmus Lerdorf on 11/28/2009 11:34 AM:
> I may have spoken too soon. Someone is now reporting that with 2.62 he
> is getting:
>
> configure.in:12: error: m4_defn: undefined macro: _m4_divert_diversion
> autom4te: /usr/bin/m4 failed with
I may have spoken too soon. Someone is now reporting that with 2.62 he
is getting:
configure.in:12: error: m4_defn: undefined macro: _m4_divert_diversion
autom4te: /usr/bin/m4 failed with exit status: 1
where the top of configure.in contains:
...
6: sinclude(Zend/acinclude.m4)
...
11: AC_PRERE
Eric Blake wrote:
> It appears that you are asking for a way to make all --help output appear
> in the same order in which you generate it, and to be able to intersperse
> text strings of your choosing in between strings generated by AC_ARG_WITH
> and AC_ARG_ENABLE.
>
> First, it looks like you ne
On Sat, 28 Nov 2009, Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thomas Dickey on 11/28/2009 8:40 AM:
well, in my view, not bothering to research a detail to provide an
accurate reply falls short of professional behavior.
You get the level of support that you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thomas Dickey on 11/28/2009 8:40 AM:
> well, in my view, not bothering to research a detail to provide an
> accurate reply falls short of professional behavior.
You get the level of support that you pay for. I need a more compelling
reas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Rasmus Lerdorf on 11/28/2009 8:23 AM:
>> But again, what's wrong with the
>> documented interfaces, or what is a specific example of a particular
>> string that outputs in a different location in the --help output than
>> where you want?
>
On Sat, 28 Nov 2009, Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thomas Dickey on 11/28/2009 8:26 AM:
For more recent changes, one would assume you knew offhand the history.
autoconf, and I have no interest in trying to make it work). But, on the
that comm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thomas Dickey on 11/28/2009 8:26 AM:
> For more recent changes, one would assume you knew offhand the history.
>
>> autoconf, and I have no interest in trying to make it work). But, on the
>
> that comment doesn't sound as if you looked
On Sat, 28 Nov 2009, Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Rasmus Lerdorf on 11/28/2009 6:42 AM:
Basically the diversions are there to organize the phases of the checks.
From
http://svn.php.net/viewvc/php/php-src/branches/PHP_5_3/configure.in?view=markup
Eric Blake wrote:> configure --help output is a special case where
diversion magic is
> necessary. Using diversion BODY is too late. But what's wrong with using
> the documented AC_ARG_ENABLE and AC_ARG_WITH, which properly manage the
> diversions on your behalf? Under the hood, they are using
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Rasmus Lerdorf on 11/28/2009 6:42 AM:
> Basically the diversions are there to organize the phases of the checks.
> From
> http://svn.php.net/viewvc/php/php-src/branches/PHP_5_3/configure.in?view=markup
>
> ## Diversion 1 is the autoconf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Rasmus Lerdorf on 11/28/2009 6:42 AM:
> Basically the diversions are there to organize the phases of the checks.
> From
> http://svn.php.net/viewvc/php/php-src/branches/PHP_5_3/configure.in?view=markup
>
> ## Diversion 1 is the autoconf
Eric Blake wrote:
> What exactly are you trying to accomplish? Without knowing your end goal,
> I can't properly suggest a better alternative (and note that the better
> alternative might mean using a different interface altogether). It may be
> better off to use the documented interface of m4_di
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Vincent Torri on 11/27/2009 3:26 PM:
> AC_DEFUN([EVAS_CHECK_IMAGE_LOADER],
> [
>
> m4_pushdef([UP], m4_toupper([[$1]]))
> m4_pushdef([DOWN], m4_tolower([[$1]]))
See my other mail - the quoting of m4_toupper changed, so losing the extra
l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Vincent Torri on 11/28/2009 2:22 AM:
> AC_DEFUN([ECORE_CHECK_MODULE],
> [
> m4_pushdef([UP], m4_toupper([[$1]]))dnl
> m4_pushdef([DOWN], m4_tolower([[$1]]))dnl
Lose the extra quotes. Per the NEWS, m4_toupper and m4_tolower now
properly q
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Rasmus Lerdorf on 11/28/2009 12:35 AM:
> Having plenty of problems getting our old 2.13-based autoconf setup
> working under the new diversions in 2.6
There is no version 2.6, but there is 2.65.
What exactly are you trying to accomplish?
Hey
another simpler example of m4 macro that fails with autoconf 2.65.
Error:
configure.ac:791: error: AC_SUBST: `ecore_[job]_cflags' is not a valid shell
variable name
m4/ecore_check_module.m4:2: ECORE_CHECK_MODULE is expanded from...
Call:
ECORE_CHECK_MODULE([Job], [${want_ecore_job}])
M
19 matches
Mail list logo
