[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using AM_CONDITIONAL in m4 macros

From: Philipp Thomas
Subject: Re: Using AM_CONDITIONAL in m4 macros
Date: Fri, 18 Jan 2013 19:45:05 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

* Nick Bowler (address@hidden) [20130118 17:17]:

> If the package author(s) provided a script to bootstrap the build
> system, then you should use that script.  Someone made the effort to
> write that script, and they presumably did not do so for no reason.

I have no idea why they originally wrote that script. Fact is it failed to
update the libtool configury correctly so that builing failed because of
libtool version mismatches. I had (wrongly) assumed that running autoreconf 
instead would get me quicker to a building package.

> You say that the provided script works, so that implies that a plain
> autoreconf is not the correct way to bootstrap this package.

That wasn't quite correct as I wrote above.

> If you think this is a bug or limitation in autoreconf, could you
> provide a small example package which demonstrates the problem?

ATM I have no time for dol an example package but the scenario I encounterd
goes something like this:

In file swig.m4:


   if test ! -z "$has_swig"; then
        SWIG_LIB=`$SWIG -swiglib`
        AM_CONDITIONAL(HAS_SWIG,[test 1])
        AM_CONDITIONAL(HAS_SWIG,[test 0])

]) calls MLX_PROG_SWIG and contains




And autoreconf complains that there is no AM_CONDITIONAL for HAS_SWIG unless
I directly m4_include swig.m4. Is that a suffient description?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]