Hello Vincent, Eric,
* Vincent Torri wrote on Tue, Aug 21, 2007 at 08:42:25AM CEST:
> On Wed, 15 Aug 2007, Ralf Wildenhues wrote:
>>
>> The patch changes a comment in the configure script:
>> # Check whether --enable-DOWN was given.
>> to
>> # Check whether --enable-bdf was given.
>
> indeed
*
On Wed, 15 Aug 2007, Ralf Wildenhues wrote:
Did you try these commands:
grep UP configure
grep DOWN configure
The patch changes a comment in the configure script:
# Check whether --enable-DOWN was given.
to
# Check whether --enable-bdf was given.
indeed
thank you
Vincent Torri
__
On Wednesday 15 August 2007 06:28, Ralf Wildenhues wrote:
> > Finally, I've compile autoconf (cvs). Remark that the documentation
> > fails on mingw. If you want the error, I can paste it somewhere.
>
> I think it's merely due to the old texinfo version that comes with
> MinGW.
That seems likely.
* Vincent Torri wrote on Sat, Aug 11, 2007 at 08:29:10PM CEST:
> On Fri, 10 Aug 2007, Ralf Wildenhues wrote:
>> * Vincent Torri wrote on Fri, Aug 10, 2007 at 07:51:00AM CEST:
>>> On Thu, 9 Aug 2007, Eric Blake wrote:
>>>
>
> Finally, I've compile autoconf (cvs). Remark that the documentation fails
On Fri, 10 Aug 2007, Ralf Wildenhues wrote:
Hello Vincent,
* Vincent Torri wrote on Fri, Aug 10, 2007 at 07:51:00AM CEST:
On Thu, 9 Aug 2007, Eric Blake wrote:
AM_CONDITIONAL([BUILD_DRIVER_]UP, [...])
calls AM_CONDITIONAL with a string consisting of UP already expanded (ok
if UP is alphan
On Saturday 11 August 2007 08:59, Vincent Torri wrote:
[Re: http://pastebin.ca/653279]
> I forget to say that I installed m4 1.4.10 ...
I've seen this before. You can't use a native (MinGW) build of m4 with
autoconf, under MSYS. The problem appears to be the result of CRLF
line endings, which
On Sat, 11 Aug 2007, Vincent Torri wrote:
I use MinGW (5.1.3, candidate) with latest release of autoconf and automake.
I can't build autoconf. See here: http://pastebin.ca/653279
I forget to say that I installed m4 1.4.10 and I used autoconf from cvs
checked out 15 minutes ago.
regards
Hey,
On Fri, 10 Aug 2007, Ralf Wildenhues wrote:
There seems to be at least one harmless unexpanded instance left in a
comment, hopefully fixed by the (untested) patch below. OK to apply?
I use MinGW (5.1.3, candidate) with latest release of autoconf and
automake.
I can't build autoconf.
Hello Vincent,
* Vincent Torri wrote on Fri, Aug 10, 2007 at 07:51:00AM CEST:
> On Thu, 9 Aug 2007, Eric Blake wrote:
>
>> AM_CONDITIONAL([BUILD_DRIVER_]UP, [...])
>> calls AM_CONDITIONAL with a string consisting of UP already expanded (ok
>> if UP is alphanumeric, but with the potential for m4 s
On Thu, 9 Aug 2007, Eric Blake wrote:
Needless to say, I only typed a quick answer, rather than trying to test
it. There are two arguments to AM_CONDITIONAL, so both should be quoted.
Then you have a choice:
AM_CONDITIONAL([BUILD_DRIVER_[]UP], [...])
calls AM_CONDITIONAL with a string for t
On Thu, 9 Aug 2007, Eric Blake wrote:
AM_CONDITIONAL(BUILD_DRIVER_[]UP, test "x${use_]DOWN[}" = "xyes")
Follow the quoting rule of thumb - if you don't want things expanded
immediately, then use one level of [] per () to protect the argument
collection scan, thereafter, use nested quotes to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Benoit SIGOURE on 8/9/2007 9:20 PM:
>>>
>>> AM_CONDITIONAL(BUILD_DRIVER_[]UP, test "x${use_]DOWN[}" = "xyes")
>>
>>
>> AM_CONDITIONAL([BUILD_DRIVER_[]UP, test "x${use_[]DOWN}" = "xyes"])
>
> Hum, shouldn't this be:
> AM_CONDITIONAL([BUILD
On Aug 10, 2007, at 4:57 AM, Eric Blake wrote:
According to Vincent Torri on 8/9/2007 12:11 PM:
I have another problem, which is similar. The problem is the
result of
AM_CONDITIONAL. Here is my macro:
AM_CONDITIONAL(BUILD_DRIVER_[]UP, test "x${use_]DOWN[}" = "xyes")
Follow the quoting ru
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Vincent Torri on 8/9/2007 12:11 PM:
>
> I have another problem, which is similar. The problem is the result of
> AM_CONDITIONAL. Here is my macro:
>
> AM_CONDITIONAL(BUILD_DRIVER_[]UP, test "x${use_]DOWN[}" = "xyes")
Follow the quoting
I have another problem, which is similar. The problem is the result of
AM_CONDITIONAL. Here is my macro:
AC_DEFUN([AS_CHECK_DRIVER], [
pushdef([UP], translit([$1], [a-z], [A-Z]))dnl
pushdef([DOWN], translit([$1], [A-Z], [a-z]))dnl
AC_ARG_ENABLE([DOWN[]],
AC_HELP_STRING(
[--disable
On Wed, 8 Aug 2007, Andreas Schwab wrote:
if test "x${use_]DOWN[_driver}" = "xyes"; then
The outer pairs of quotes are removed before the AC_DEFUN macro is
called, thus the argument does not contain the word DOWN any more, but
rather use_DOWN_driver. You need to fix the quoting that they su
On Aug 8, 2007, at 7:03 PM, Vincent Torri wrote:
if test "x${use_pcf_driver}" = "xyes"; then
AC_MSG_NOTICE([Creating pcf driver...])
rm -f src/lib/drv_pcf.c
echo "/* CAUTION! NEVER EDIT THIS FILE */" > src/
lib/drv_pcf.c
sed 's/bdf/pcf/g' src/lib/drv_bdf.c | sed 's/BDF
Vincent Torri <[EMAIL PROTECTED]> writes:
> AC_DEFUN([AS_CREATE_DRIVER], [
>
> pushdef([UP], translit([$1], [a-z], [A-Z]))dnl
> pushdef([DOWN], translit([$1], [A-Z], [a-z]))dnl
>
> pushdef([SRCUP], translit([$2], [a-z], [A-Z]))dnl
> pushdef([SRCDOWN], translit([$2], [A-Z], [a-z]))dnl
>
> if test "
18 matches
Mail list logo
