AS_ECHO calls finding their way into calls

Hello,

I'm relatively new to autoconf, and I'm having trouble getting the  
configure file to generate properly on another person's computer. It  
appears that when he uses the AC_ERLANG_CHECK_LIB macro, the configure  
file that's generated has an AC_ECHO still embedded in one of the  
strings to be called. To recreate the problem, we made a skeleton  
configure.ac containing only:

AC_INIT

AC_ERLANG_CHECK_LIB(erl_interface)


When my friend runs autoconf on the file, the relevant section (at  
least, I think this is where the problem lies) reads:

{ $as_echo "$as_me:$LINENO: checking for Erlang/OTP 'erl_interface'  
library subdirectory" >&5
$as_echo_n "checking for Erlang/OTP 'erl_interface' library  
subdirectory... " >&6; }
if test "${erlang_cv_lib_dir_erl_interface+set}" = set; then
   $as_echo_n "(cached) " >&6
else
   ac_ext=erl
ac_compile='$ERLC $ERLCFLAGS -b beam conftest.$ac_ext >&5'
ac_link='$ERLC $ERLCFLAGS -b beam conftest.$ac_ext >&5 ; echo "#!/bin/
sh" > conftest$ac_exeext ; AS_ECHO(["\"$ERL\" -run conftest start -run  
init stop -noshell"]) >> conftest$ac_exeext ; chmod +x conftest
$ac_exeext'
      if test "$cross_compiling" = yes; then
   { { $as_echo "$as_me:$LINENO: error: cannot run test program while  
cross compiling
See \`config.log' for more details." >&5
$as_echo "$as_me: error: cannot run test program while cross compiling
See \`config.log' for more details." >&2;}
    { (exit 1); exit 1; }; }
else

And when I run it, it reads:

{ echo "$as_me:$LINENO: checking for Erlang/OTP 'erl_interface'  
library subdirectory" >&5
echo $ECHO_N "checking for Erlang/OTP 'erl_interface' library  
subdirectory... $ECHO_C" >&6; }
if test "${erlang_cv_lib_dir_erl_interface+set}" = set; then
   echo $ECHO_N "(cached) $ECHO_C" >&6
else
   ac_ext=erl
ac_compile='$ERLC $ERLCFLAGS -b beam conftest.$ac_ext >&5'
ac_link='$ERLC $ERLCFLAGS -b beam conftest.$ac_ext >&5 ; echo "#!/bin/
sh" > conftest$ac_exeext ; echo "\"$ERL\" -run conftest start -run  
init stop -noshell" >> conftest$ac_exeext ; chmod +x conftest$ac_exeext'
      if test "$cross_compiling" = yes; then
   { { echo "$as_me:$LINENO: error: cannot run test program while  
cross compiling
See \`config.log' for more details." >&5
echo "$as_me: error: cannot run test program while cross compiling
See \`config.log' for more details." >&2;}
    { (exit 1); exit 1; }; }
else

Now, I did note that his has $as_echo wherever mine had just echo, and  
I don't know why that is, and don't know why google couldn't provide  
any useful links on the matter. The real problem appears to be that  
his "ac_link" variable has AS_ECHO in it instead of echo, which seems  
like it would cause problems to me. This is where he gets an error  
when running ./configure:

./configure: eval: line 1: syntax error near unexpected token `["\"$ERL
\" -run conftest start -run init stop -noshell"]'
./configure: eval: line 1: `$ERLC $ERLCFLAGS -b beam conftest.$ac_ext  
 >&5 ; echo "#!/bin/sh" > conftest$ac_exeext ; AS_ECHO(["\"$ERL\" -run  
conftest start -run init stop -noshell"]) >> conftest$ac_exeext ;  
chmod +x conftest$ac_exeext'


For the record, I am using autoconf 2.60 and M4 version 1.4.5, and he  
is using autoconf 2.62 and M4 version 1.4.11. My platform is Mac OS X  
10.5 running fink versions of these tools and he is using Mac OS X  
10.4 running the darwinports version, if that makes any difference.

Do any of you know what might be happening here, and what my next  
troubleshooting steps should be?

Thanks.


_______________________________________________
Autoconf mailing list
Autoconf@...
http://lists.gnu.org/mailman/listinfo/autoconf