I am seeing trivial test failures just because
% rm -f
usage: rm [-f|-i] [-dPRrvW] file ...
e.g.,
> /stresstest.at:251: eval '$LIBTOOL --mode=link $CC $CFLAGS $LDFLAGS -o "$rel"s
ub2/liba.la "$rel"sub/a.lo' $linkargs
> stderr:
> usage: rm [-f|-i] [-dPRrvW] file ...
> stdout:
> libtool: link: rm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paolo Bonzini on 12/14/2007 7:03 AM:
>> What is the m4_provide_if? I didn't find it in the manual of autoconf
>> and m4.
>
> It's in m4sugar.
>
>> Anyways, does this guarantee me that the user did INVOKE the give
>> macros, not merely t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[Adding bug-autoconf, replies can drop libtool]
According to Paolo Bonzini on 12/14/2007 5:24 AM:
>
> You can use m4_provide_if like this:
>
> m4_define([m4_provided], [
> m4_provide_if([AC_PROG_LIBTOOL], [], [
> m4_provide_if([LT_INIT], [],
>
m4_define([m4_provided], [
m4_provide_if([AC_PROG_LIBTOOL], [], [
m4_provide_if([LT_INIT], [],
[m4_warn([syntax], [Libtool required by $1])])])])])
...
m4_provided([MY_MACRO_NAME])
I didn't count the number of closing brackets.
What is the m4_provide_if? I didn't find it in
On Dec 14, 2007, at 1:24 PM, Paolo Bonzini wrote:
The reason why I'm asking this is that I wrote some macros that
rely on Libtool's magic handling of -R and even though it's
clearly stated in the doc/comments/README that Libtool is
mandatory, people keep running in troubles because they did
The reason why I'm asking this is that I wrote some macros that rely on
Libtool's magic handling of -R and even though it's clearly stated in
the doc/comments/README that Libtool is mandatory, people keep running
in troubles because they didn't use Libtool, so I'd like to trigger an
error, so
Hello,
is it possible to detect that AC_PROG_LIBTOOL has been invoked,
either at runtime by looking at a shell variable that Libtool defines
or preferably at autoreconf-time by looking at one of the m4 macros
it defines? I'd like something that works on reasonably old versions
of Libtool
