All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Steele Scott <toojays@toojays.net>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: urcu commit a767fd requires autoconf >= 2.64.
Date: Wed, 13 Jun 2012 22:41:57 +0930	[thread overview]
Message-ID: <4FD8919D.9060607__10059.5898148187$1339595021$gmane$org@toojays.net> (raw)
In-Reply-To: <20120613081001.GA30123@Krystal>

On 13/06/12 17:40, Mathieu Desnoyers wrote:
> * John Steele Scott (toojays@toojays.net) wrote:
>> http://lists.lttng.org/pipermail/lttng-dev/2012-May/017927.html
>>
>> I tried to build the latest urcu (git master e51500) on a Centos 6.2 box, and got:
>>
>> jscott@dxi0-62:~/src/userspace-rcu$ make -j4
>> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /users/jscott/src/userspace-rcu/config/missing --run aclocal-1.11 -I config
>> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /users/jscott/src/userspace-rcu/config/missing --run autoconf
>>  cd . && /bin/sh /users/jscott/src/userspace-rcu/config/missing --run automake-1.11 --foreign
>> configure:4010: error: possibly undefined macro: m4_ifnblank
>>       If this token and others are legitimate, please use m4_pattern_allow.
>>       See the Autoconf documentation.
>> make: *** [configure] Error 1
>> make: *** Waiting for unfinished jobs....
>>
>> Some digging showed that the macro m4_ifnblank requires autoconf 2.64. Centos 6.2 has autoconf 2.63. :(
>>
>> I just worked around it by reverting commit a767fd locally, then I can build fine.
> Thanks for pointing this out! Can you try the following patch and let me
> know if it fixes your issue ?
>
>

Mathieu,

Thanks for your quick response. Unfortunately, with that patch, ./configure fails like:

checking for thread local storage (TLS) class... __thread
./configure: line 4029: syntax error near unexpected token `fi'
./configure: line 4029: `fi'

The section of configure which it's complaining about looks like:

 if test "$ac_cv_tls" != "none"; then

     cat >>confdefs.h <<_ACEOF                                                                                                                                                                                    
#define TLS $ac_cv_tls                                                                                                                                                                                            
_ACEOF                                                                                                                                                                                                            

     cat >>confdefs.h <<_ACEOF                                                                                                                                                                                    
#define CONFIG_RCU_TLS $ac_cv_tls                                                                                                                                                                                 
_ACEOF                                                                                                                                                                                                            

 else

 fi

It seems it doesn't like the empty else..fi clause. If I put a command in there ("true", "echo", whatever), configure completes and I can build successfully.

cheers,

John

  parent reply	other threads:[~2012-06-13 13:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <jr9e2h$phq$1@dough.gmane.org>
2012-06-13  8:10 ` urcu commit a767fd requires autoconf >= 2.64 Mathieu Desnoyers
     [not found] ` <20120613081001.GA30123@Krystal>
2012-06-13 13:11   ` John Steele Scott [this message]
     [not found]   ` <4FD8919D.9060607@toojays.net>
2012-06-13 19:31     ` Mathieu Desnoyers
     [not found]     ` <20120613193142.GA20907@Krystal>
2012-06-13 23:17       ` John Steele Scott
     [not found]       ` <4FD91F91.6080204@toojays.net>
2012-06-14  4:55         ` Mathieu Desnoyers
2012-06-13  7:04 John Steele Scott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='4FD8919D.9060607__10059.5898148187$1339595021$gmane$org@toojays.net' \
    --to=toojays@toojays.net \
    --cc=lttng-dev@lists.lttng.org \
    --cc=mathieu.desnoyers@efficios.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.