Hey,
i've written a macro with 2 parameters.
Suppose that the macro name is FOO, if I use it like that in the
configure.ac file:
FOO([var1]
["yes"]
)
the value of the 2nd parameter in the macro is not yes, but yes followed
by a new line
to remove that error, i just use
FOO([var1], ["y
Vincent Torri writes:
> Hey,
>
> i've written a macro with 2 parameters. Suppose that the macro name is
> FOO, if I use it like that in the configure.ac file:
>
> FOO([var1]
> ["yes"]
> )
Did you mean to write comma after [var1]? Without it there is only one
argument.
> the value of the 2nd
On Sun, 15 Feb 2009, Andreas Schwab wrote:
Vincent Torri writes:
Hey,
i've written a macro with 2 parameters. Suppose that the macro name is
FOO, if I use it like that in the configure.ac file:
FOO([var1]
["yes"]
)
Did you mean to write comma after [var1]? Without it there is only on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Vincent Torri on 2/15/2009 2:45 AM:
>> See node Macro Arguments in the m4 documentation: only leading unquoted
>> whitespace is skipped when collecting macro arguments. All other
>> whitespace will become part of the argument.
>
> ok, th
Dear listmembers,
currently I am attempting to make an old package (namely xcdroast) build and
compile with zero warnings.
Now, this package is using gettext 0.11.5 what causes 2 warnings to pop up
(they're harmless, but I'd like to know how to get rid of them):
config.status: WARNING: po/Makef
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Dieter Jurzitza on 2/15/2009 8:42 AM:
> Now, this package is using gettext 0.11.5 what causes 2 warnings to pop up
> (they're harmless, but I'd like to know how to get rid of them):
>
> config.status: WARNING: po/Makefile.in.in seems to
Steffen Dettmer wrote:
I'm not sure how it looks in your context, but I think usually
autoconf expects to be able to create a binary which usually
requires at least some libc.
Or are you compiling a libc itself?
No, not libc.
How should the knowledge base (I assume it would be some
deliver
Eric Blake wrote:
According to Ivan Levashew on 2/12/2009 11:59 AM:
Generally, I'd like build system and compiler to be as humble as
possible. Don't run tests on my platform, don't look for libraries and
headers in my /usr directory. If something is not specified by means of
command line or env
Dear listmembers,
dear Eric,
I tried your recommendation but doing this the apparently "harmless" warning
turned to an error.
Following your advice I put the define into configure.in, what made the
warnings vanish, however, if I do not forcibly enter the string
datarootdir = @datarootdir@
into
