Re: guile.m4 for autogen

Re: guile.m4 for autogen

[Bruce Korb]

Hi Harlan,

On 08/18/12 14:41, Harlan Stenn wrote:
> Have you tried using pkg-config in autogen's configure to find the guile
> CFLAGS and loader stuff?

I'd prefer to use guile.m4, even though it uses guile-config.  It insists.
Unfortunately, it does not work.  For me.

> configure.ac:140: the top level
> configure:14130: error: possibly undefined macro: AC_LIB_LINKFLAGS_FROM_LIBS
>       If this token and others are legitimate, please use m4_pattern_allow.
>       See the Autoconf documentation.
> bootstrap failure:  trapped exit signal
> mk-all: line 197:  5702 Killed

Here's the configure script fragment with the reference:

>   { $as_echo "$as_me:${as_lineno-$LINENO}: checking libguile link flags" >&5
> $as_echo_n "checking libguile link flags... " >&6; }
>   GUILE_LDFLAGS="`$GUILE_CONFIG link`"
>   { $as_echo "$as_me:${as_lineno-$LINENO}: result: $GUILE_LDFLAGS" >&5
> $as_echo "$GUILE_LDFLAGS" >&6; }
>
>         AC_LIB_LINKFLAGS_FROM_LIBS(GUILE_LIBS, $GUILE_LDFLAGS, )
>   GUILE_LIBS="$GUILE_LDFLAGS $GUILE_LIBS"
>   AC_LIB_LINKFLAGS_FROM_LIBS(GUILE_LTLIBS, $GUILE_LDFLAGS, yes)
>   GUILE_LTLIBS="$GUILE_LDFLAGS $GUILE_LTLIBS"

Since this guile.m4 comes from Guile 2.0.4, it is recent enough that any
fully supported AC_* macro should not have been removed from autoconf 2.69.
If I delete the GUILE_FLAGS invocation, then all is fine.

*sigh*.

Re: guile.m4 for autogen

[Ludovic Courtès]

Hi Bruce,

Bruce Korb <bruce.korb@gmail.com> skribis:

> Hi Harlan,
>
> On 08/18/12 14:41, Harlan Stenn wrote:
>> Have you tried using pkg-config in autogen's configure to find the guile
>> CFLAGS and loader stuff?
>
> I'd prefer to use guile.m4, even though it uses guile-config.  It insists.
> Unfortunately, it does not work.  For me.
>
>> configure.ac:140: the top level
>> configure:14130: error: possibly undefined macro: AC_LIB_LINKFLAGS_FROM_LIBS
>>       If this token and others are legitimate, please use m4_pattern_allow.
>>       See the Autoconf documentation.
>> bootstrap failure:  trapped exit signal
>> mk-all: line 197:  5702 Killed

As the comment says:

  dnl AC_LIB_LINKFLAGS_FROM_LIBS is defined in gnulib/m4/lib-link.m4 and needs
  dnl the file gnulib/build-aux/config.rpath.

This means that these two files have to be imported in your project for
this to work.

I hadn’t noticed that, and I reckon that this is unfortunate.

The change dates back to Feb. 2011, by Bruno, so we’d have to check the
rationale.

Thanks,
Ludo’.

Re: guile.m4 for autogen

[Bruce Korb]

Hi Ludovic,

On 08/24/12 06:36, Ludovic Courtès wrote:
>> I'd prefer to use guile.m4, even though it uses guile-config.  It insists.
>> Unfortunately, it does not work.  For me.
>>
>>> configure.ac:140: the top level
>>> configure:14130: error: possibly undefined macro: AC_LIB_LINKFLAGS_FROM_LIBS
>>>        If this token and others are legitimate, please use m4_pattern_allow.
>>>        See the Autoconf documentation.
>>> bootstrap failure:  trapped exit signal
>>> mk-all: line 197:  5702 Killed
>
> As the comment says:
>
>    dnl AC_LIB_LINKFLAGS_FROM_LIBS is defined in gnulib/m4/lib-link.m4 and needs
>    dnl the file gnulib/build-aux/config.rpath.
>
> This means that these two files have to be imported in your project for
> this to work.
>
> I hadn’t noticed that, and I reckon that this is unfortunate.
>
> The change dates back to Feb. 2011, by Bruno, so we’d have to check the
> rationale.

Thank you for the explanation.

I am a big fan of comprehensible error messages and, as you'd guess,
I don't think that "possibly undefined macro: AC_LIB_LINKFLAGS_FROM_LIBS"
qualifies.  Adding an AC_REQUIRE() would likely trigger something more
meaningful.  Having to trace down a comment in an m4 file is not
very friendly.

However, now that I know the issue, obviously I'll add these files to
the list of things I grab from gnulib.  Thank you again.

Regards, Bruce

Re: guile.m4 for autogen

[Harlan Stenn]

Bruce,

I just tracked down one of the problems:

stenn@deacon> grep ag_cv_test_guile_version *
config.log:ag_cv_test_guile_version='Backtrace: In ice-9/boot-9.scm:
149: 8 [catch #t #<catch-closure 1f1180> ...] 157: 7 [#<procedure 2458c0
()>] In unknown file: ?: 6 [catch-closure] In ice-9/boot-9.scm: 63: 5
[call-with-prompt prompt0 ...] In ice-9/eval.scm: 407: 4 [eval # #] 368:
3 [eval # #] 392: 2 [eval # #] In ice-9/popen.scm: 142: 1 [open-pipe*
"r" "/usr/local/gnu/bin/pkg-config" "--modversion" "guile-2.0"] In
unknown file: ?: 0 [execlp "/usr/local/gnu/bin/pkg-config"
"/usr/local/gnu/bin/pkg-config" ...] ERROR: In procedure execlp: ERROR:
In procedure execlp: No such file or directory error:
("/usr/local/gnu/bin/pkg-config" "--modversion" "guile-2.0") exited with
non-zero error code 1'
stenn@deacon> 

The effect of this is that GUILE_VERSION is empty, so the compile of
autogen aborts.

H